14. Build together, learn together *A good idea needs somewhere to go and people who will help it grow.* Industry perspective > “Refine the change, based on what was learned from the test.” * (#quotation-context) Institute for Healthcare Improvement Model for Improvement: Testing Changes · Act step (https://www.ihi.org/library/model-for-improvement/testing-changes) · Accessed 2026-10-10 The Act step of Plan-Do-Study-Act: learn from a small test, then decide what to change or test next. Listen for the useful detail A volunteer discovers that a different opening question helps someone feel more comfortable during a call. A family member notices a missing explanation. A frontline team finds a simpler way to prepare for a visit. Each observation may contain something worth exploring. The first step is to make it possible to share the idea in ordinary language. What happened? What was difficult? What seemed to help? Who might benefit? A person should not need to arrive with a finished product proposal before the organization will listen. The genus innovation workflow can help turn that description into a structured draft. AI assistance can organize the challenge, intended value, and proposed approach so the team has something concrete to discuss. The originating person should be able to check whether the draft still reflects what they meant. Image description: An observation becomes a clear need, a working draft, human review, a small test, and shared learning. Learning returns to the next revision. AI can help clarify and prepare, while people decide readiness. Figure 14. Give a useful idea a path into practice · Connection map Connection map for collaborative improvement. Progress depends on listening, a useful test, and the review the work needs; this is not a fixed delivery schedule. 1. Start with a challenge or need and explain the value of a possible change. 2. Prepare something people can see and try, then review scope and responsibilities before testing. 3. Learn with the people using it. Share useful lessons with permission and carry them into the next revision. Move from an observation to something people can try A small prototype can make a conversation more useful. People can react to wording, a sequence, or a working example instead of trying to imagine a specification. They may change the idea substantially, and that can be the most valuable part of the work. AI-assisted design and development can shorten the time needed to prepare some drafts. The ambition is to keep conversations active while ideas become visible. A focused improvement may move toward a usable version in days; complex changes take longer, particularly when clinical, privacy, integration, or operational review is required. The useful measure is whether the process helps the team learn and produce something it can responsibly support. Speed matters when it keeps a real need in view. It should not hide unresolved questions about who will use the tool, what it changes, or who maintains it. Learn from a small, purposeful test The Model for Improvement (https://www.ihi.org/library/model-for-improvement) asks teams to define an aim, decide how they will recognize improvement, and identify changes worth testing. Its Plan-Do-Study-Act approach (https://www.ihi.org/library/model-for-improvement/testing-changes) supports learning through small tests and revision. For the volunteer’s idea, a first test might be a reviewed conversation guide used in a defined setting. The team could ask whether people felt more comfortable, whether volunteers found the wording natural, and when the approach did not fit. The test should respect the organization’s consent, supervision, and information-handling requirements. A lesson becomes more useful when it includes context. “This phrase worked” is incomplete. Explain the situation, the intended purpose, what was observed, and the limits of the observation. Other teams can then decide whether it is relevant to their circumstances. Capturing wins A win may be a better question, a clearer explanation, a useful resource, less duplicated work, or a handoff that reaches someone able to help. Give that observation a route into learning: 1. Describe the situation and intended purpose. 2. Record what someone tried and what was observed. 3. Preserve the context, uncertainty, and anything that did not help. 4. Review what may be shared, with whom, and under which permissions. 5. Try the idea in an appropriate setting with an agreed reviewer. 6. Return to contributors with the decision and what was learned. AI can organize permitted information; the contributor checks its meaning and responsible people decide what to try and share. Capture limits as well as benefits. A useful win connects a person’s experience with improved quality, less effort, or more dependable service. Verify any financial effect separately. Use the learning-loop definitions (genus-book-review.html#companion-learning-loops-and-capturing-wins) to return reviewed decisions to contributors. Retain, change, stop, or do not proceed can all close a loop. The aim is learning that strengthens care and the organization, not a growing count of positive stories. Share learning without taking more than was offered A contribution can be shared voluntarily and reviewed before wider use. That does not require automatic call recording or unrestricted reuse of personal information. Teams can often describe an approach without identifying the people involved. Agree what the contributor is comfortable sharing and what the organization may publish. Remove unnecessary personal details and review the result. Where a story or example still identifies someone, the relevant permissions and review remain necessary. The aim is to carry useful learning forward while respecting the relationship from which it came. The carePhysics connection From Local Experience to Shared Learning (https://genusconnect.org/carephysics/book/chapter-14) provides the main connection. Scoring — Learn What Helps (https://genusconnect.org/carephysics/book/chapter-10) encourages a careful look at what measures can and cannot tell us. Combine observations, experience, and practical measures. A tool may be used often because it is helpful, because it is required, or because another route is difficult. Ask people what the activity means. Keep the person’s purpose visible as the team decides what to retain, change, or remove. genusLabs and the next opportunities genusLabs describes a direction in which people can propose and help create tools, games, and features for varied communities. The opportunity is to connect a useful idea with the people and context where it can help. Review, testing, and support belong before ecosystem release. Some ideas may grow into products of their own. Others may remain small improvements that make a particular community’s day easier. Both can have value. This direction does not mean unrestricted public publishing is currently available. Bring your knowledge Begin with one need, one audience, and one outcome worth working toward. Bring the people closest to the need into the conversation. Use a draft to make the idea visible, agree how it will be reviewed, and decide what would help you learn from a first test. Then return to the people who contributed. Show what changed, explain what is still uncertain, and invite the next observation. Building together is an ongoing relationship: listening, trying, learning, and making room for someone else’s understanding. Explore further — An idea worth bringing forward Describe the challenge, who experiences it, and what better would look like. Add an example and any constraints the team should understand. Say what you have already tried and what you do not yet know. That is enough to begin a useful conversation. The partner worksheet in the companion turns these questions into a practical starting brief. About the quotations * External quotations illustrate relevant ideas and directions in care and technology. Their inclusion does not imply affiliation with, sponsorship of, or endorsement of genus by the quoted individuals or organizations.