Sonesis/AI Capability Development

These lessons are designed to learn with Sonesis/AI’s help. It can help you understand the material, answer questions, explain a difficult distinction in another way, give you examples, and help you connect the ideas to the work you are actually doing.

These lessons represent most of those aspects of the Sonesis system not commonly found. You can do these lessons in any order. You can start with the video, the slides and transcript, or the detailed reading—or simply tell Sonesis/AI what you are trying to accomplish and let it help you decide where to begin.

The goal is not for Sonesis/AI to give you more information. It is to help you develop capability. It can question your reasoning, create practice situations, check your understanding, help fill gaps, and then work with you as you apply the ideas in a real situation. You can come back with what happened, examine the evidence together, and decide what to try next. As your understanding and judgment grow, the amount of assistance should decrease.

These 24 short learning units provide a working path through the core ideas behind Sonesis and Sonesis/AI. Each unit focuses on a capability people can develop and use in real work. The sequence is tentative and can evolve as the material is used, reviewed, and improved.

1. Human Capability in the Age of AI

Why capability—not AI tool operation or content consumption—is the central objective.

AI makes information, drafts, code, analysis, and options increasingly abundant. That shifts the differentiator away from simply knowing how to operate an AI tool and toward what a person can recognize, understand, decide, improve, and learn. This session introduces the overall Sonesis/AI learning model: AI should not merely help people produce more; it should help them develop better judgment, stronger system understanding, and greater adaptive capability. The goal is increasing human agency—using AI to extend what people can accomplish while developing the capability to work intelligently in situations that continue to change.

2. Training vs. Capability Development

Interaction → Learning → Application → Evidence → Adaptation → Transfer → Capability.

Training can create understanding, but understanding alone does not demonstrate capability. The real test comes when someone must recognize a situation, apply what they learned in context, observe what happens, adapt, and transfer the reasoning to a different situation. This session introduces the full capability-development path and highlights where conventional training often weakens: application, evidence, and adaptation. It also shows why learning should continue after the formal session ends, using real work and feedback to turn knowledge into something the learner can use independently.

3. Learning with AI Without Creating Dependence

How AI can explain, question, challenge, assess, and reduce assistance as capability grows.

AI can make high-quality help available at the moment of need, but the way that help is provided matters. If the AI always notices, frames, decides, and reflects for the learner, it may improve short-term output without strengthening the person. This session distinguishes answer mode from capability-development mode and shows how AI can use a broader repertoire: explanation, questioning, examples, practice, challenge, prediction, assessment, and reflection. The governing principle is increasing capability with decreasing assistance, so the person becomes more able to recognize, reason, and act without needing the same level of support.

4. Perception, Framing, and Reactivity in Change

Recognizing how prior experience, perceived risk, attachment, and framing shape interaction.

People do not respond only to the words being spoken; they respond to the meaning those words have for them. Prior experience, role, identity, status, perceived risk, and what the current system has taught them all influence how a proposal is interpreted. This session helps learners notice reactivity without prematurely labeling it resistance, keep multiple explanations open, and examine their own framing before pushing harder. It introduces practical ways to reduce unnecessary threat, restore choice, create curiosity, and use inquiry and evidence to improve the quality of change conversations.

5. Complex Work: Complexity, Uncertainty, and What They Do Not Mean

Distinguish uncertainty from helplessness; identify what can still be known and acted on.

Complex work can be hard to predict without being unknowable. Many important relationships—queues, dependencies, batch size, unclear objectives, delayed feedback—remain understandable even when the whole system produces surprising outcomes. This session shifts attention away from simply labeling work complex and toward managing uncertainty: what is known, assumed, suspected, and unknown; which uncertainty matters to the next decision; and what action can create value or evidence without excessive irreversible risk. The objective is grounded agency under uncertainty, not false certainty and not helplessness.

6. Flow, Work in Process, and the Economics of Delay

Recognize overloaded systems, queues, dependencies, and why more activity can reduce delivery.

More activity does not necessarily mean more value is being delivered. When too much work is started, queues grow, feedback slows, dependencies become harder to coordinate, and completion can decline even while everyone appears busy. This session develops the ability to see Work in Process, delay, handoffs, utilization, and feedback as interacting system conditions rather than isolated process metrics. Learners examine how smaller batches, reduced WIP, better sequencing, and earlier completion can improve both flow and learning, and why the economics of delay should influence how work is organized.

7. Constraints, Dependencies, and Scarce Capability

See how local workload, specialization, and coordination constraints shape system performance.

Some of the most important limits on performance are not visible in a team backlog. Scarce expertise, shared services, approval points, external dependencies, specialized knowledge, and coordination demands can constrain the entire value-creation system. This session helps learners identify where capability is genuinely scarce, distinguish local busyness from system constraint, and understand how adding work near a constraint can make overall performance worse. The emphasis is on designing around real dependencies and scarce capability rather than assuming that every problem should be solved by making every team independently cross-functional.

8. Learning Through Prediction and Evidence

Make expectations explicit, compare actual with predicted, and adapt the model or action.

Improvement becomes more rigorous when we make our expectations visible before acting. A prediction does not imply certainty; it makes the current explanation testable. This session shows how to connect hypotheses, expected results, observations, and evidence so that a difference between predicted and actual outcomes produces learning. When results differ, the response is not simply to declare success or failure. The learner examines whether the action, implementation, measurement, assumptions, explanatory model, or context should change. This creates a stronger learning loop than simply trying things and calling the result inspect-and-adapt.

9. Stakeholder Value Beyond Users and Customers

Identify all relevant stakeholders and what value, constraints, and consequences matter.

Product and service decisions are often framed primarily around users or customers, but organizational outcomes are affected by a broader set of stakeholders. Regulators, operations, support, employees, partners, finance, security, communities, leadership, and others may all create value, receive value, impose constraints, or experience consequences. This session develops the ability to identify the stakeholders who actually matter to a decision and understand their objectives, concerns, and evidence needs. The goal is not to satisfy everyone equally, but to make important value and consequences visible before work is decomposed into features or backlogs.

10. Stakeholder Alignment Across Products and Product Lines

See how locally rational product decisions can create poor system-level outcomes.

Product managers can each make sensible decisions within their own area and still create conflict, duplication, dependency, or diluted value across the organization. This session focuses on alignment before separate products and backlogs pull work in different directions. Learners examine shared stakeholders, cross-product consequences, conflicting objectives, sequencing dependencies, and common value outcomes. The capability is to recognize when local optimization is creating a system-level problem and to create an alignment object or conversation that lets multiple product leaders reason together before detailed commitments make divergence expensive.

11. Quality Value Requirements (QVRs): Finding a Meaningful Slice

Use QVR reasoning to find a valuable, testable increment rather than simply making work smaller.

Breaking work into smaller pieces is useful only when the smaller piece still creates meaningful value or useful evidence. This session introduces QVR reasoning as a way to find a coherent slice that is valuable enough to matter, small enough to learn from, and concrete enough to guide further work. Learners examine stakeholder value, conditions of satisfaction, evidence, dependencies, and what must be present for the slice to be meaningful. The goal is not decomposition for its own sake; it is to create increments that improve learning, reduce risk, and move the system toward a worthwhile outcome.

12. QVRs as an Organizational Alignment Mechanism

Use a common value slice to align product managers before separate backlogs diverge.

QVRs are not only a way to slice work; they can also provide a common object around which multiple product managers align. Before each product area decomposes its work independently, a shared value slice can clarify what the organization is collectively trying to realize, which stakeholders matter, and what evidence would indicate progress. This session develops the ability to use QVRs as an organizational coordination mechanism, helping product leaders expose conflicts and dependencies earlier. The result is less reliance on reconciling already-divergent backlogs after local decisions have hardened.

13. Objective Stories: Clarifying What Must Be Accomplished

Move from feature/story language toward objectives, conditions, and useful evidence while retaining existing terminology when helpful.

User stories and similar artifacts can be useful, but teams often move too quickly from a request into a solution-shaped statement. Objective Stories shift attention toward what must be accomplished, under what conditions, for whom, and how useful evidence will show whether the objective has been met. This session helps learners recover the reasoning underneath story language without requiring an organization to abandon its existing terminology. The capability is to make objectives and conditions explicit enough that teams have room to discover better solutions rather than treating the first proposed implementation as the requirement.

14. Learning Requirements Earlier With Less Rework

Connect objectives, examples, feedback, and evidence to reduce late discovery and avoid premature decomposition.

Requirements problems are often learning problems. Important distinctions are discovered too late because objectives, examples, constraints, stakeholder concerns, and evidence were not explored early enough. This session shows how to improve learning before large commitments are made, without pretending that complete requirements can be known up front. Learners connect objectives to concrete examples, clarify uncertainty, identify what must be learned, and delay premature decomposition when it would freeze weak assumptions into detailed work. The aim is earlier discovery of what matters and less rework caused by misunderstood purpose or context.

15. Diagnose Before You Prescribe

Start from purpose, context, constraints, forces, and evidence before selecting practices.

Improvement efforts often begin with a preferred solution: a framework, practice, tool, team structure, or transformation model. This session reverses that order. Learners begin with the worthwhile objective, the current condition, stakeholder needs, constraints, system forces, history, and available evidence. Only then do they consider practices that might help. The capability is not merely asking more questions; it is forming a useful explanatory model before prescribing action. This reduces the risk of applying a generally good practice to a situation whose underlying dynamics require something different.

16. Patterns: Reusable Solutions in Context

Understand patterns as recurring problem/force/solution relationships rather than recipes.

A pattern is more than a reusable solution. It captures a recurring problem, the forces that make the problem difficult, the context in which a response applies, the tradeoffs involved, and the resulting consequences. This session develops the ability to use patterns as reasoning aids rather than as instructions to copy. Learners examine why a solution worked, what conditions supported it, what forces it balanced, and where it may fail. This creates reusable organizational knowledge that can guide adaptation while avoiding the rigidity that occurs when practices are separated from the problems and forces they were intended to address.

17. Scientific Reasoning for Improvement

Distinguish hypothesis, prediction, observation, evidence, inference, assumption, and uncertainty.

Organizations often use scientific language without maintaining the distinctions that make scientific reasoning useful. This session develops a practical vocabulary for improvement: what is observed, what is inferred, what is assumed, what hypothesis is being considered, what prediction follows from it, and what evidence would support or challenge the explanation. Learners also examine uncertainty and credible alternatives rather than rushing to certainty. The capability is to make reasoning inspectable enough that teams can learn from disagreement and results, instead of protecting a favored explanation after the evidence changes.

18. OODA, Retrospection, and Adaptive Improvement

Use observation and learning loops to adapt intelligently rather than ritualizing inspect-and-adapt.

Observation, orientation, decision, action, and retrospection can create powerful learning loops when each step changes what the system understands and does next. They become weak when reduced to recurring ceremonies whose output does not materially influence action. This session examines OODA, retrospection, and related adaptive practices as mechanisms for improving perception and decision-making. Learners focus on what should be observed, how existing frames influence orientation, how decisions connect to predictions, and how evidence from action changes the next cycle. The objective is adaptive capability, not ritual compliance.

19. Designing Value Creation Structures Around the Work

Treat structure as a design problem shaped by value, dependencies, capability, coordination, and context.

There is no universally correct organizational structure. Product teams, service groups, platforms, shared capabilities, specialists, research functions, regulatory groups, and other structures can all be appropriate depending on the work. This session helps learners design value-creation structures from the governing dynamics rather than from a preferred topology. Stakeholder value, dependencies, scarce capability, coordination cost, learning needs, flow, and context become design variables. The capability is to ask what structure best supports the work now and how that structure should evolve as the work, constraints, or capabilities change.

20. Beyond Cross-Functional Teams as a Default

Treat cross-functionality as one design variable rather than an unquestioned destination.

Cross-functional teams solve important problems, especially excessive handoffs and fragmented ownership, but they are not the answer to every organizational design problem. Some capabilities are too scarce, specialized, expensive, regulatory, or context-dependent to duplicate inside every team. This session helps learners distinguish when cross-functionality reduces delay and coordination cost from when it creates underutilization, diluted expertise, or new dependencies. The goal is not to reject cross-functional teams but to treat them as one possible design response among others, selected because they fit the work rather than because they are considered inherently mature.

21. Coaching for Capability

Shift from giving answers toward helping people recognize, reason, apply, learn from evidence, and transfer.

Coaching becomes more powerful when the objective is not simply to solve the immediate problem but to change what the other person can do next time. This session develops the ability to choose among explanation, questioning, challenge, modeling, practice, prediction, reflection, and direct advice based on the capability need. Learners also examine attachment, perceptual dynamics, and the danger of turning questions into disguised persuasion. The aim is increasing capability with decreasing assistance, while still recognizing situations where a direct answer or expert recommendation is the most responsible response.

22. The Sonesis Improvement Kata

Use a repeatable improvement conversation to connect objectives, current conditions, predictions, evidence, adaptation, and capability.

The Sonesis Improvement Kata provides a repeatable structure for moving from intention to learning. It connects a worthwhile objective with the current condition, obstacles or governing dynamics, a useful next action, an explicit prediction, evidence, and adaptation. Unlike a fixed problem-solving recipe, the kata is intended to improve both the situation and the person’s capability to reason about similar situations. This session introduces the conversational pattern and shows how Sonesis/AI can support it between human interactions while keeping responsibility for purpose, judgment, and action with the person.

23. The Sonesis Improvement Kata — Advanced

Work with ambiguity, perceptual dynamics, transfer, deeper diagnosis, and decreasing assistance.

Advanced use of the Sonesis Improvement Kata requires more than following the conversational sequence. The coach or learner must work with ambiguity, incomplete explanations, competing objectives, emotional or perceptual dynamics, and situations where the next useful distinction is not obvious. This session focuses on deeper diagnosis, maintaining multiple hypotheses, choosing when to challenge or explain, transferring learning across contexts, and deliberately reducing assistance as capability develops. The aim is flexible use of the kata as a reasoning discipline rather than mechanical adherence to a script.

24. From Individual Learning to Organizational Learning

Capture and review reusable knowledge, patterns, evidence, and reasoning so one engagement or team can improve the next.

Capability development becomes much more valuable when learning survives beyond the individual or team that generated it. This session examines how session analyses, decisions, examples, questions, evidence, patterns, disagreements, predictions, and application results can become reusable organizational knowledge. The emphasis is not on storing everything, but on preserving reasoning that can improve future diagnosis and action. Sonesis/AI can help retrieve and apply this knowledge in context, while human review maintains quality and provenance. The result is a system in which one engagement, incident, experiment, or team can improve what the next one is able to see and do.