Choose Learn it when…
the problem is bounded, an internal owner can apply the method, and building in-house capability is the main goal.
Three equal routes
Choose how to build the capability.
Start with the business constraint, then choose the route that fits the decision work, internal capacity, adoption risk, and amount of implementation support needed.
A route decision guide
The routes are not quality or price tiers.
Choose Build it with us when…
the work needs diagnosis, decisions across roles, and facilitated design grounded in the real process.
Choose Have us build it when…
the workflow can be defined, a process owner exists, and configuration, documentation, testing, and handoff are the main needs.
One business can use different routes for different capabilities. A team might learn a weekly review rhythm, co-design its sales handoff, and use implementation support for a bounded intake system.
A way to build
Learn it
Use practical guidance to build and maintain the capability inside your own team.
Who it fits
- An owner or team member has time and authority to apply the work.
- The problem is bounded enough to learn through a guide, workshop, clinic, or working example.
- Keeping the knowledge in-house matters more than speed of implementation.
Who it may not fit
- Nobody has capacity to apply the material after the session.
- The workflow spans several roles and needs facilitated decisions.
- The change carries risk that requires specialist or regulated advice.
Example artifacts
- Diagnostic worksheet
- Step-by-step guide or template
- Practice exercise and review questions
- Owner-defined application plan
What Run Better NW contributes
Frames the problem, teaches a practical method, supplies usable tools, demonstrates the work, and helps review application.
What the owner and team contribute
Chooses the real problem, brings the people who own it, adapts the tool, performs the work, and maintains the result.
Common reasons this route fails
- The session is treated as inspiration rather than scheduled work.
- The attendee lacks authority to change the process.
- A template is copied without adapting it to the real workflow.
When another route may fit: Choose Build it with us when the team needs facilitated design, or Have us build it when a bounded workflow needs configuration and rollout support.
Diagnose the capability firstNo monitored public contact is active yet.
A way to build
Build it with us
Work alongside Run Better NW to diagnose, design, test, and introduce the capability.
Who it fits
- The owner wants expert structure but needs the system grounded in the team's actual work.
- Several roles must agree on handoffs, ownership, or exceptions.
- Adoption matters as much as the process or tool design.
Who it may not fit
- The owner cannot provide access to the people who perform the work.
- The decision has already been made and only production capacity is needed.
- The issue is solely professional advice outside Run Better NW's scope.
Example artifacts
- Current-state and constraint map
- Co-designed workflow and ownership rules
- Prototype or configured working model
- Test notes, adoption actions, and decision log
What Run Better NW contributes
Maps the current work, facilitates decisions, drafts the process and supporting system, structures tests, and helps the team review adoption.
What the owner and team contribute
Supplies factual context, makes business decisions, involves affected people, approves changes, tests the work, and owns ongoing use.
Common reasons this route fails
- Working sessions exclude the people who know the exceptions.
- Decisions are postponed while tools are configured.
- The owner delegates sponsorship but not authority.
When another route may fit: Choose Learn it when the internal team can apply a clear method alone, or Have us build it when the design is bounded and implementation help is the main need.
Diagnose the capability firstNo monitored public contact is active yet.
A way to build
Have us build it
Have a defined workflow and supporting system designed, configured, documented, tested, and handed over with your participation.
Who it fits
- The business can define a bounded workflow and responsible owner.
- The team can participate in discovery, testing, training, and approval.
- A working implementation and handoff are more useful than advice alone.
Who it may not fit
- The desired outcome is still too broad or disputed to define.
- No one will own the system after handoff.
- The work requires unsupported software, regulated judgment, or continuous managed operation.
Example artifacts
- Approved workflow and system configuration
- Roles, controls, and exception paths
- Operating documentation and training materials
- Test record, handoff checklist, and maintenance owner
What Run Better NW contributes
Structures discovery, designs and configures the agreed workflow, documents controls and exceptions, supports testing and training, and prepares the handoff.
What the owner and team contribute
Approves scope and decisions, provides access and accurate facts, assigns a process owner, participates in testing, and accepts responsibility after handoff.
Common reasons this route fails
- The business expects configuration to resolve an undecided process.
- Testing uses ideal examples and misses real exceptions.
- Handoff occurs without a named owner or maintenance rhythm.
When another route may fit: Choose Build it with us when discovery and shared decision-making are the main work, or Learn it when the team mainly needs a method and tools.
Diagnose the capability firstNo monitored public contact is active yet.
What happens after reading or contacting?
Reading a route guide creates no service, program, booking, or commercial relationship. When a monitored contact path is active, a conversation can clarify the problem and possible fit. Any later paid or program relationship would require separate scope, terms, approvals, and agreement.