Operating Logic
This is the why behind Atlas: a visual operating architecture for making the agency system visible, editable, and easier to align.
It is not about storing information. It is about making the system visible.
Atlas centralizes the elements that shape the agency: people, initiatives, meetings, resources, decisions, roadmap, and the relationships between them. It does not replace Notion, Slack, Google Drive, Canva, or other tools. It helps show how those pieces connect, what affects what, and what is needed to build with clarity.
Atlas is not a line. It is an iterative visibility system.
Discovery, Understanding, Building, and Evolution feed each other continuously. A meeting can reveal a resource gap; a resource gap can change the roadmap; a roadmap change can create new questions; new questions can return the team to discovery. This is how the system stays alive instead of becoming a static document.
iterative TS
what exists
what connects
what becomes work
what changes
What do we have?
Resources, tools, subscriptions, databases, documents, platforms, assets, and existing materials.
Who is involved?
People, roles, stewards, contributors, areas, and communication paths.
What are we building?
Initiatives, products, experiences, workflows, content systems, and internal tools.
Where are we going?
The roadmap: visible flow, priorities, dependencies, milestones, and what each step unlocks.
What changed?
Roadmap evolution: visible adjustment points, why they changed, and what they impact.
What do we still need to know?
Open questions, missing access, unclear ownership, unknown costs, and assumptions to validate.
How to explain it
How to read Atlas
Quick reading of the whole system.
How the major parts relate.
What tools exist, what is missing, and what affects what.
The road: priorities, dependencies, and what each step unlocks.
Where the roadmap changed and why.
What needs validation before the next decision.
System Dashboard
A quick reading of the whole operating system. Use this first to see what is present, what is missing, and what needs clarification.
The Knowing Agency
Client prototype workspace built from the MPA Flow Atlas model.
MPA Flow Atlas
Reusable visual operating architecture. This workspace can evolve without losing data as long as the Foundation schema remains stable.
How to read this
If a number is low, it does not mean a problem. It means that area is not visible yet. The goal is to turn conversations into observable architecture.
Recommended onboarding flow: Dashboard → Discovery → Resources → Ecosystem Map → Roadmap.
Starter roadmap logic
Start with discovery and infrastructure before production. If the team already has tools, use them. If not, propose a small toolkit with cost, purpose, and priority.
Prototype maturity: working internal tool, cloud persistence enabled, collaboration model next.
Ecosystem Map
The visual anatomy of the system. It shows the relationships between people, initiatives, resources, and roadmap items. Use it to ask: what affects what?
Live Map
For the conversation itself. Add quick nodes, move them, connect them, and validate understanding in real time.
Discovery
Everything that enters the system: ideas, areas, gaps, risks, existing workflows, needs, and opportunities.
Add discovery item
Discovery list
People / Org
Who is in the system, what they own, where they support, and what knowledge they hold.
Add person / role
Org visibility
Resources
Tools, platforms, subscriptions, repositories, templates, APIs, databases, docs, and infrastructure. This view makes visible what exists, what is unknown, what needs access, and what may require budget.
Add resource
Resource Map
How to read: move resources near the initiative or capability they support. A line means “this resource affects / enables / is needed by this part of the system.” Use this to make tool decisions visible.
Resource matrix
Same resources as cards for quick scanning. The map is for visibility; the matrix is for details.
Meeting Intelligence
Paste Notion summaries or transcript fragments. Extract decisions, open questions, next steps, affected areas, and resource needs.
Add meeting
Meeting log
Initiatives
What is alive, paused, legacy, emerging, or ready to become roadmap work.
Add initiative
Current initiatives
Roadmap
A visible road, not a task dump. It shows sequence, priority, dependencies, owners, and what each stage makes possible.
Add roadmap item
Road view
How to read: follow the road from left to right. Darker/warmer cards are higher priority. Each card shows what must be true, what it depends on, and what it unlocks.
Horizon lanes
Same roadmap grouped by working horizon.
Editable roadmap list
Evolution
Visible points of adjustment: what changed, why it changed, who proposed it, and what it impacts.
Add adjustment point
Evolution map
How to read: each adjustment shows how the roadmap changed. This keeps the why visible.
Direction Log
Decisions, clarifications, and strategic direction. This protects the why behind the work.
Add direction
Direction log
Open Questions
Questions that need validation. Keep hypotheses separate from facts.