Discovery Playbook:

Discover Your Operating System

A structured way to discover the core elements of your operating system—cycles, rituals, artifacts, language, structures, and decision patterns—and identify opportunities for improvement.

Introduction

Your guide to discovering how your organization really works

GOAL: By following the steps in this playbook, you will have a clear, concrete picture of how your organization actually works today, including its cycles, rituals, artifacts, language, structures, systems, and decision patterns. You will have collected the raw inputs needed to design, configure, and instrument your operating system in the tool of your choice (ideally Dotwork, but not required).

The goal of this playbook is to equip customers, future customers, and partners with a structured way to discover the core elements of their operating system and identify opportunities for improvement.

Dotwork is uniquely suited to bring these insights to life in a tool, but these practices stand on their own. We share them freely because we believe that how you work, and the systems you use to support that work, should be treated as a product. Your operating system has customers. It has objectives. It deserves intentional design.

You do not need to go deep on every activity in this playbook. You only need to go deep enough to illuminate what is getting in the way right now. Dotwork is not a three-month “implementation” that you finish once. It is a platform for continuous improvement and continuous adaptation. You start where you are, make things a little more legible, and then evolve as your organization evolves.

You're Creating an Internal Platform!

If we are to leave one message in your head, it is this: you are creating an internal platform, not buying and installing a vendor product. What does that actually mean?

  1. You have a North Star. The goal is better decision making and more engaged team members.
  2. You have inputs. Reduced friction, better data quality, improved collaboration, clearer insights, early detection of risks, and healthier conversations.
  3. You have users. Your platform is a multi-sided product. Leaders need a high-level view; managers and teams want context to make good decisions.
  4. You want to encourage helpful behaviors, not zombie processes.
  5. Tools alone will not solve your problems, but they can help reduce friction, encourage habits, surface the right information, and gently nudge the organization toward healthier routines.

How Tools Like Dotwork Help

InterventionDescriptionHow Tools Like Dotwork Help
EducationBuild understanding, deliver relevant informationProvides structured visibility, embedded context, and access to strategic info in real-time
TrainingDevelop skills through guided practiceSupports templates, walkthroughs, and embedded workflows that reinforce applied learning
EnablementRemove barriers or add support mechanismsReduces coordination friction, surfaces blockers, enables behavior via nudges and scaffolds
PersuasionInfluence attitudes through communicationNudges, progress indicators, team stories, and visible value pathways shape beliefs
ModelingDemonstrate desired behavior through exampleMakes good behaviors, rituals, and patterns across teams visible — see what works
Environmental RestructuringChange context to enable behaviorShapes flow of work: rituals, dashboards, check-ins, working agreements — structures new defaults

Download this playbook as a PDF