Introducing the RS AI Learning Lab

A learner-directed home for practical AI learning, safe experimentation, and shared growth.

Audience: Internal team and contributors
Status: Working internal draft
Public counterpart: Public-version placeholder

The RS AI Learning Lab is a place for people to learn about AI without needing to become AI specialists.

Tracks offer maps. Modules offer useful places to stop, learn, practice, and build. Learners choose the route that fits their goals, questions, experience, abilities, and available time.

Some people will arrive wanting to understand what generative AI is. Others will bring a problem they need to solve, a skill they want to develop, or a concern they need help evaluating. Some may want to complete an entire learning track. Others may need only one module and a useful conversation.

There is no single entrance and no required path through the Lab. A module may name prerequisites when they are genuinely needed; otherwise, suggested paths remain suggestions.

Why the Learning Lab Exists

AI is entering ordinary work, learning, creativity, family life, small businesses, and community life.

Yet much of today’s AI education still begins with product demonstrations, collections of clever prompts, or predictions about what the technology may eventually become. Those things can be useful, but they are not enough.

People also need durable concepts that continue to make sense when products change. They need practical judgment, safe places to experiment, and people they can ask for help. They need opportunities to see where AI is useful, where it is unreliable, and where human experience still matters most.

The RS AI Learning Lab exists to make that learning grounded, useful, and accessible.

Curiosity is welcome here.

Skepticism is welcome too.

A learner does not need to believe that AI will change everything. They do not need to become enthusiastic about every new product. They only need enough curiosity to ask better questions and enough skepticism to examine the answers.

What the Learning Lab Is

The Learning Lab is a learner-directed, modular learning environment.

It brings together tracks, modules, presentations, videos, activities, references, guides, demonstrations, community support, and opportunities for practice. It is intended to help people move from explanation into experience.

The Lab is not being designed as a finished textbook placed on a shelf. It is a working learning environment that will evolve through use.

Learners will help shape that evolution.

Their questions will reveal missing explanations. Their experiences will show where activities are unclear, inaccessible, unrealistic, or incomplete. Their projects may inspire new examples, new modules, new formats, and entirely new learning paths.

Some learners may eventually become contributors, reviewers, facilitators, mentors, or creators themselves.

Feedback is therefore not simply a way to improve existing content. It is one of the ways the Learning Lab discovers what it should become next.

The Lab is not:

• A single required course
• A vendor certification program
• A sales funnel for one AI company or product
• A promise that every learner must become technical
• A content library that ends with reading or watching
• A substitute for human responsibility or qualified professional judgment

That final boundary requires some nuance.

Learning materials can help people ask better questions, understand tradeoffs, prepare for professional conversations, and recognize when additional expertise is needed. They cannot replace legal, medical, financial, engineering, security, or other specialized judgment when the consequences demand it.

Learners will not always need to go somewhere else for that help.

Renaissance Solutions includes experienced technical professionals and may be able to provide consulting, assessment, facilitation, or implementation support when a learner or organization needs more than a learning module. When a need falls outside our expertise, authority, or professional scope, we will say so and help identify the appropriate kind of assistance.

The Learning Lab and RS consulting services are connected resources, but they are not the same thing. A learner may use the Lab without becoming a consulting client, and someone may seek professional support without completing a learning track.

The goal is to give people honest options.

Who the Learning Lab Is For

The Learning Lab is intended for people who are completely new to generative AI as well as people who have been using it for some time and suspect they may have missed important foundations.

Its audiences may include:

• Community learners
• Workers and small-business owners
• Students and lifelong learners
• Families and older adults
• Creators and educators
• Mentors and facilitators
• People preparing for external certifications
• Future contributors
• People who are curious but not yet ready to participate directly

Participation should not depend on being able to sit at a keyboard and type quickly.

Learners may type, speak, watch, listen, discuss, work with a partner, use printed examples, use assistive technology, or begin by observing.

Where AI products support voice interaction, learners may practice speaking naturally with them. Modules may also introduce accessibility features such as speech-to-text, text-to-speech, screen readers, magnification, keyboard navigation, captions, transcripts, alternative input devices, and other participation aids.

Accessibility is not a specialty layer that gets added after the main experience is built. It is part of how the Lab defines participation.

We will not always get it right on the first attempt. That is one reason accessibility reviewers, learner testers, disabled learners, caregivers, and contributors with lived experience are essential to the Lab’s development.

The goal is not merely to say that everyone is welcome.

The goal is to remove as many unnecessary barriers as we reasonably can.

How Tracks Work

Tracks organize related modules around a larger area of learning.

Each track has a Track Guide that explains:

• Who the track is for
• What the track covers
• The major concepts learners will encounter
• Suggested starting points
• Suggested paths through the material
• Related tracks
• Available learning formats
• Tool or access considerations
• An optional capstone, when one is available

Track Guides are maps, not fences.

A learner may follow a suggested route from beginning to end. Another learner may choose only the modules that address an immediate need. Someone with experience may enter near the middle, while another person may spend more time building foundations.

Tracks help learners see the landscape. They do not require everyone to walk through it in the same order.

How Modules Work

Each module is designed around a specific learning purpose.

Depending on the topic and stage of development, a module may contain:

• A clear purpose
• Observable learning outcomes
• A What’s Inside summary
• A human-led presentation
• A human video explainer
• Demonstrations
• Questions and guided discussion
• Practical activities
• Reflection prompts
• Optional homework
• A take-home artifact
• Prerequisites and related modules
• Tool and access requirements
• Accessibility guidance
• Safety reminders
• Feedback and support links

Not every module will use every element.

A conceptual module may focus on discussion, examples, and reflection. A practical lab may include demonstrations and hands-on activities. A module about risk, privacy, or decision-making may require more review and conversation than tool use.

The promise is simpler:

A module should help a learner understand something, try something, notice something, and decide what to do next.

The goal is not to fill time or produce more content. It is to create a useful change in what the learner can understand, evaluate, discuss, or do.

Ways to Participate

The Learning Lab is being designed for multiple forms of participation.

Current and emerging formats include:

• In-person presentations and workshops
• Live demonstrations and questions
• Human-led YouTube explainers
• Self-guided module pages
• Live online sessions
• Optional homework projects
• Office hours
• Community discussions
• Interactive labs
• Games and simulations
• Optional capstone modules
• Learner and contributor showcases

These formats will not all be available at once.

Each track and module should clearly describe its current learner availability using honest language such as:

• Available
• Drafting
• Pilot
• Planned
• Deferred

A planned video should not be presented as though it already exists. A pilot workshop should not be described as a mature program. A promising idea should be allowed to remain an idea until it has been tested.

The Learning Lab is a growing workshop, not a stage set painted to look finished.

Tools, Accounts, and Cost

Most introductory modules should be usable with free versions of commonly available AI tools.

Some modules may require a low-cost feature, temporary subscription, paid account, API access, local hardware, or cloud computing resources. Advanced modules may involve development tools, automation platforms, specialized software, or infrastructure that is not freely available.

Every module should explain its requirements before the learner begins.

Whenever possible, shared demonstrations, paired participation, printed examples, group activities, and observation options will be used to reduce barriers.

The Lab aims to remain broadly tool-agnostic, especially when teaching durable concepts such as context, verification, privacy, prompting, trust, and human review.

That goal will not always be completely achievable.

Some capabilities exist only within particular products. Interfaces differ. Accessibility support varies. Features appear, change, move, or disappear. Certain modules may need to focus on a specific platform, model, workflow, or technical environment.

When that happens, the Lab should say so clearly rather than pretending that every lesson transfers perfectly across tools.

This is also one reason contributors matter.

No single person or small team can maintain deep, current knowledge of every major AI product. Contributors who use different tools can expand coverage, test activities, identify platform-specific limitations, and help learners understand what transfers and what does not.

Tool independence is a direction, not a purity test.

Learning for Different Goals

People will come to the Learning Lab for different reasons.

A learner may want to:

• Understand AI well enough to participate in conversations about it
• Solve an immediate problem
• Become safer and more informed
• Build practical chatbot skills
• Explore creative uses
• Improve work processes
• Prepare for an external certification
• Build a portfolio
• Complete a capstone
• Join a learning community
• Become a contributor, facilitator, reviewer, or mentor

Completion will therefore mean different things for different learners.

For one person, completion may mean attending a single workshop and leaving with a safer way to use a chatbot. For another, it may mean completing a track and producing a capstone. Someone else may return periodically as tools and responsibilities change.

The Lab should make those choices explicit rather than pretending that every learner needs the same finish line.

Capstones and Portfolios

Every track is intended to eventually include an optional capstone module.

Capstones will give learners a chance to combine concepts, practical skills, judgment, and human review from several modules.

A capstone might involve:

• Evaluating an AI-supported workflow
• Building and testing a small solution
• Creating an educational artifact
• Documenting a responsible-use process
• Comparing multiple tools
• Designing a practical activity for other learners
• Conducting a structured risk or readiness review

Capstones may support portfolios, contributor applications, or forms of completion recognition.

They remain optional.

A learner who needs targeted knowledge should not be required to produce a large final project simply to prove that the learning mattered.

When capstones are created, they should document the learner’s reasoning, choices, testing, review, and reflection. A polished AI-generated output alone does not demonstrate understanding.

The artifact matters.

The human thinking behind it matters more.

Activities, Examples, and the Learner Gallery

Learning activities should emphasize reflection, judgment, adaptation, and transfer.

A successful exercise is not simply one that produces an impressive output. It should help the learner notice why something worked, where it failed, what assumptions shaped the result, and whether the approach would still be appropriate in another setting.

Learners and contributors may create:

• Infographics
• Explainer videos
• Podcasts
• Study guides
• Games
• Simulations
• Demonstrations
• Checklists
• Case studies
• Sample workflows
• Reflection journals
• Comparison exercises

Selected learner work may eventually appear in a moderated gallery.

That gallery will require human gatekeepers.

Before work is shared, reviewers may need to consider consent, privacy, intellectual property, accessibility, factual accuracy, sensitive information, and the rights of other people represented in the artifact.

Participation in the gallery will always be optional.

The Lab will not measure learning by how much content a person generates or how frequently they post.

Volume is not understanding.

Safety, Responsibility, and Trust

Global Learning Lab boundaries apply across every track and module.

Learners will be taught to protect sensitive information, recognize the limits of AI-generated outputs, and use appropriate verification when accuracy matters.

Important outputs may require review by a knowledgeable person, authoritative source, qualified professional, or accountable decision-maker.

Consequential decisions remain human-owned.

The more serious the possible impact, the less appropriate it is to treat an AI response as the final word.

The Lab will also work to make trust visible.

Where practical:

• Sources should be identified
• Reviewers should be named or their role described
• Tool-specific facts should be dated
• Product limitations should be stated
• Corrections should be published
• Uncertainty should be acknowledged
• Learners should be told where to seek additional help

Professional and authoritative support should not be reduced to a vague sentence telling people to “consult an expert.”

Learners should be given specific routes.

Depending on the situation, those routes may include RS consulting, licensed professionals, public agencies, product support, accessibility services, educators, community organizations, or other appropriate resources.

Trust grows when people can see where the edges are.

Learning With a Community

Learning rarely happens through content alone.

People learn by asking questions, watching others work, comparing approaches, explaining ideas, testing assumptions, and returning after the first attempt goes sideways.

The Learning Lab is intended to support that social layer through:

• Weekly office hours
• Facilitator support
• Community questions
• Peer learning
• Learner testing
• Shared examples
• Contributor opportunities
• Feedback loops
• Moderated discussion spaces

A Discord community or another shared platform may eventually become part of the Lab.

It should not be launched simply because community platforms are easy to create.

Moderation capacity, privacy practices, accessibility, escalation processes, participation expectations, and community boundaries need to develop before broad public launch.

Community support is part of the destination.

It must also be built responsibly.

Built by Contributors

The Learning Lab begins with Mike as its initial steward, but it is being designed for shared authorship, review, production, testing, facilitation, and maintenance.

No single person can represent every learner, understand every tool, test every accessibility need, review every technical claim, or maintain every area of knowledge.

Contributors may serve as:

• Writers
• Learning designers
• Facilitators
• Reviewers
• Activity developers
• Video producers
• Podcast producers
• Accessibility reviewers
• Community stewards
• Tool specialists
• Subject-matter contributors
• Learner testers
• Mentors

Roles, credit, review expectations, decision authority, and compensation should be made explicit.

Contribution should not become a polite name for invisible labor.

The RS AI Learning Lab is being built by a growing group of learners, practitioners, facilitators, reviewers, and creators. Shared stewardship is not merely a way to produce more material. It is part of the design.

Learners should be able to influence the Lab without first becoming formal contributors. Contributors should be able to challenge assumptions, expand tool coverage, surface accessibility barriers, and help the Lab reach people its original designers may not have understood well enough.

The Lab should become broader because more people helped shape it.

Where the Lab Is Today

The Learning Lab is still being built.

Tracks and modules exist at different stages.

Some are early ideas. Some are outlines or source packets. Some are nearing runnable form. Some have already developed through conversations, workshops, articles, demonstrations, or practical experiments.

Presentations and human video explainers are beginning to develop together. External credential alignment is being researched. Formal learner evidence is still limited. Feedback, testing, accessibility review, and revision systems are still being established.

The current site is an internal working home, not the final public learning experience.

That is not something to hide.

Learners and contributors should be able to distinguish between a stable module, an active pilot, and an idea that is still looking for its legs.

Transparency about the Lab’s maturity is part of building trust.

Where the Lab Is Headed

The immediate goal is not to launch everything.

It is to create a useful initial set of modules that people can actually run, test, learn from, and improve.

Over time, the Learning Lab may grow to include:

• A practical collection of runnable modules
• In-person and human-video versions
• More self-guided pathways
• Optional capstones
• Portfolio support
• Credential-aligned pathways where appropriate
• Office hours
• Moderated community support
• Interactive exercises
• Games and simulations
• A human-reviewed learner gallery
• A larger contributor and facilitator network
• Broader coverage of AI tools and platforms
• Continuous improvement driven by learner evidence

The direction is ambitious.

The promises should remain grounded.

The Lab will grow through modules that work, contributors who care, learners who respond honestly, and a willingness to revise what does not hold up in practice.

An Invitation

Start with the question that brought you here.

Choose a module. Follow a suggested path. Attend a session. Watch an explainer. Bring a problem to office hours. Observe before participating. Work with a partner. Help test an activity. Tell us what remains confusing. Show us where the experience creates unnecessary barriers.

You do not need to know where the path ends before taking the first useful step.

The RS AI Learning Lab is designed to grow through use, reflection, contribution, and shared care.

The map is being drawn.

Learners will help decide where it leads.

---

Source: docs/introducing-rs-ai-learning-lab.md