The Myriada Lens: Interpreting Organizational Culture Through Decision Architecture

Culture is often described as 'how things get done around here,' but that definition is too abstract to act on. Decision architecture — the rules, roles, and rhythms that shape how choices are made — offers a concrete lens. When you map the decision points in an organization, you see culture not as a fog but as a system of levers. This guide introduces the Myriada Lens, a practical framework for interpreting organizational culture through decision architecture.

We have seen teams spend months on values workshops only to find that the real friction lives in who approves a budget, how a meeting is run, or what data is considered before a hire. The Myriada Lens flips the focus: instead of asking 'what do we believe,' ask 'how do we decide.' The answers reveal culture with surgical precision.

This guide is for leaders, internal consultants, and team leads who need to diagnose cultural issues without relying on vague surveys. It assumes no prior knowledge of decision intelligence, but it does expect a willingness to look at your organization as a set of repeatable choice patterns.

Who Needs This and What Goes Wrong Without It

Every organization has a decision architecture, whether it is designed or emergent. When it is emergent, culture problems appear as symptoms: slow execution, blame loops, low psychological safety, or innovation bottlenecks. Teams blame 'the culture' but cannot point to a root cause. Without a decision architecture lens, interventions are guesswork — a new mission statement, a team-building offsite, or a reorg that shifts boxes without changing how choices flow.

Consider a typical scenario: a product team struggles to ship features on time. The common diagnosis is 'poor prioritization.' But if you map decisions, you might find that the engineering lead has final say on scope, the product manager owns the roadmap, and the designer is consulted only after specs are locked. The architecture creates sequential bottlenecks and rework. No amount of 'agile training' will fix that; you need to rewire who decides what and when.

Another common failure: a company invests in 'empowerment' but keeps all budget decisions at the executive level. Frontline teams feel trusted in theory but powerless in practice. The decision architecture contradicts the espoused culture, breeding cynicism. Without the Myriada Lens, leaders blame 'resistance to change' rather than the structural mismatch.

The Myriada Lens is designed for three primary audiences:

• Leaders who want to align culture with strategy by redesigning decision rights.
• Internal consultants and HR business partners who need a diagnostic tool that goes beyond engagement surveys.
• Team leads who face recurring friction and want a systematic way to identify the decision points causing it.

Without this lens, you risk treating symptoms. You might run a 'culture transformation' that changes language but not behavior. The Myriada Lens gives you a map of the actual machinery.

Prerequisites and Context Readers Should Settle First

Before applying the Myriada Lens, you need a few foundational pieces in place. First, clarify the scope: are you looking at a single team, a department, or the entire organization? The lens works at any scale, but the granularity changes. For a team, you can map every decision in a two-week sprint. For an organization, you focus on high-stakes decisions like budget allocation, hiring, and strategy.

Second, gather raw materials: recent decision logs, meeting notes, email threads, and any documented processes. You do not need perfect data — you are looking for patterns, not precision. If you have access to a few people who can describe how a typical decision unfolds, that is enough to start.

Third, check your own biases. The Myriada Lens is descriptive, not prescriptive. You are mapping how decisions actually happen, not how you think they should happen. If you are a leader, your own role in the architecture may be uncomfortable to see. Be prepared to find that you are the bottleneck.

Fourth, understand the key dimensions of decision architecture that the lens examines:

• Decision rights: Who has the authority to decide, who must be consulted, and who is informed after the fact?
• Information flow: What data is available to decision-makers, and when?
• Decision timing: Are decisions made on a regular cadence, or ad hoc? Is there a deadline?
• Accountability: Who is responsible for the outcome, and how is that measured?
• Decision process: Is it a formal process (e.g., a governance board) or informal (e.g., hallway conversations)?

Finally, set a boundary: the Myriada Lens is not a substitute for deep cultural work like addressing systemic inequity or trauma. It is a cognitive tool for understanding one layer of culture. If you are dealing with a toxic environment, decision architecture may be a symptom, not the root cause. Use the lens to reveal patterns, but pair it with other interventions when needed.

Core Workflow: Mapping Decision Architecture in Five Steps

The core workflow is a structured observation and analysis process. It works best when done collaboratively with a small group of people who live the decisions daily. Here is the sequential process.

Step 1: Identify a Recurring Decision Type

Start with one type of decision that happens frequently and has visible outcomes. Examples: sprint planning, hiring a new team member, approving a budget request, or choosing a vendor. Avoid one-off decisions like 'should we acquire a company' — they are too rare to reveal cultural patterns. Pick something that occurs at least monthly.

Step 2: Map the Actual Flow

For the chosen decision type, trace the last three instances. For each, answer: who initiated? Who was consulted? Who made the final call? Who was informed? How long did it take? What information was used? Use a simple swimlane diagram or a list of roles and actions. Do not rely on the official process — map what actually happened. You will often find that the real flow differs from the documented one.

Step 3: Identify Decision Gaps and Misalignments

Compare the actual flow to what the team or organization says it wants. Common gaps include: decisions that should be delegated but are escalated; decisions that require input that never arrives; or decisions that are made without the right data. Also look for 'decision shadows' — choices that are made informally and never recorded, which often carry unspoken power.

Step 4: Analyze Cultural Signals

Each gap or misalignment sends a cultural signal. For example, if all budget decisions go to the CEO, the signal is 'we do not trust managers with money,' regardless of what the values poster says. If decisions are made in closed-door meetings, the signal is 'transparency is optional.' List the signals you observe. They are the raw material for cultural interpretation.

Step 5: Design a Targeted Intervention

Choose one decision type and redesign its architecture to send a different cultural signal. For instance, if you want to signal trust, delegate a specific budget threshold to team leads. If you want to signal collaboration, require a cross-functional review before a decision is final. The intervention should be small and measurable — change one decision right, not the whole system at once.

This workflow is iterative. After you change one decision point, observe how the culture shifts. You may need to adjust. The Myriada Lens is not a one-time audit; it is a continuous practice.

Tools, Setup, and Environment Realities

You do not need expensive software to apply the Myriada Lens. A whiteboard, sticky notes, and a facilitator are sufficient for a team-level mapping. For larger organizations, you might use a simple spreadsheet to track decision types, rights, and gaps. Some teams use collaborative tools like Miro or Lucidchart to build decision flow diagrams. The key is to keep the artifact living — update it as decisions evolve.

However, the environment matters. The lens works best in a setting where psychological safety is moderate to high. If people fear retribution for pointing out that a leader makes all decisions, the mapping will be incomplete. You may need to anonymize the data or work with a neutral facilitator. In low-trust environments, start with a small, low-stakes decision type that the team feels safe discussing.

Another reality: decision architecture is not static. It shifts with new leadership, reorganizations, and external pressures. A mapping from six months ago may be outdated. Treat the lens as a snapshot, not a permanent blueprint. Revisit it quarterly for high-change environments.

Time investment varies. A team-level mapping for one decision type can take 90 minutes in a workshop. An organization-wide audit might take several weeks of interviews and analysis. Start small. The goal is not to map everything, but to map something actionable.

Finally, be aware of the 'observer effect.' When you start asking about decision rights, people may become more conscious of their choices, which can alter behavior. That is fine — it means the lens is already having an impact. Just note that your initial mapping may capture a system that is already shifting.

Variations for Different Constraints

The Myriada Lens is flexible. Here are common variations based on organizational constraints.

Startup vs. Enterprise

In a startup, decisions are often fast and informal. The lens reveals where that informality causes confusion — e.g., two founders both think they have final say on product direction. The intervention is often to clarify decision rights with a simple RACI-like matrix. In an enterprise, the challenge is the opposite: too many formal layers. The lens helps identify where decisions are over-escalated or where approval chains create delays. The intervention is to push decision rights downward.

Remote vs. In-Person

Remote teams have a different decision architecture because informal hallway conversations are replaced by scheduled calls and async messages. The lens can reveal that decisions are slower because they wait for synchronous meetings. A variation is to map the 'decision latency' — the time between a decision being needed and being made. Interventions include async decision protocols (e.g., 'decide by Friday unless someone objects') or dedicated decision channels in Slack.

High-Stakes vs. Low-Stakes Decisions

For high-stakes decisions (e.g., budget, hiring), the architecture tends to be conservative and layered. The lens helps identify where risk aversion is built into the process. For low-stakes decisions (e.g., which software tool to use), the architecture may be too heavy. The variation is to create a 'decision tier' system: low-stakes decisions are delegated, medium-stakes require consultation, and high-stakes require formal approval. The Myriada Lens helps you calibrate the tiers.

Cross-Functional vs. Single-Function Teams

Cross-functional teams often struggle with decision rights because each function has its own reporting line. The lens can map the 'decision handoffs' — where a decision moves from one function to another. Common friction points are at the boundaries: e.g., engineering and design disagree on scope. The intervention is to create a shared decision forum (e.g., a weekly triage meeting) with clear escalation rules.

Each variation requires adjusting the scope and the intervention. The core workflow remains the same, but the emphasis shifts based on the constraint you are addressing.

Pitfalls, Debugging, and What to Check When It Fails

Even with a solid mapping, things can go wrong. Here are common pitfalls and how to debug them.

Pitfall 1: Mapping the Official Process, Not the Real One

Teams often describe what should happen, not what does. To avoid this, ask for specific examples: 'Tell me about the last time you needed approval for a new hire. Who did you talk to? What happened?' If the story contradicts the process map, trust the story. Debug by cross-checking with three different people involved in the same decision type.

Pitfall 2: Overwhelming Scope

If you try to map every decision at once, you will drown in detail. The lens works best when focused on one decision type at a time. If the mapping feels too complex, narrow the scope. Pick a decision that is causing visible pain and map only that. You can expand later.

Pitfall 3: Ignoring Informal Power

Decision architecture is not just about roles; it is also about who has influence. A junior person may have de facto decision power because they control the data. Or a senior person may be bypassed because they are hard to reach. The lens must capture informal influence. Add a column for 'actual influencer' alongside 'formal decision-maker.' If the two diverge, that is a cultural signal worth exploring.

Pitfall 4: Designing Interventions Without Buy-In

Changing decision rights is political. If you redesign a process without involving the people who currently hold power, they will resist. Before implementing an intervention, share the mapping with stakeholders and ask: 'Does this match your experience? What would you change?' Co-design the intervention with those affected. The lens is a diagnostic tool, not a prescription from on high.

Pitfall 5: Expecting Immediate Culture Change

Culture shifts slowly. Changing a decision right does not instantly change behavior. People need time to unlearn old habits. After an intervention, check in after a month: is the new architecture being used? If not, is it because of resistance, lack of training, or a flaw in the design? Adjust accordingly. The Myriada Lens is a cycle, not a one-shot fix.

Frequently Asked Questions and Common Mistakes in Prose

We often hear from teams who try the Myriada Lens and run into the same questions. Here are the most common ones, addressed in plain language.

How many decisions should I map? Start with one. Pick a decision that is causing frustration or delay. Map it thoroughly. Once you see value, add a second. Quality over quantity. Mapping ten decisions superficially is less useful than mapping one decision with depth.

What if the mapping reveals that I am the problem? That is uncomfortable but valuable. The lens is not about blame; it is about design. If you hold too many decision rights, consider delegating. If you are not providing enough information, change that. The lens gives you a lever to pull. Acknowledge the discomfort and use it as data.

Can I use this lens without a facilitator? Yes, but it is harder. A neutral facilitator helps surface blind spots. If you go solo, be extra careful about confirmation bias. Ask a colleague to review your mapping. Better yet, do the mapping as a team exercise where everyone contributes their perspective.

Is this lens only for business organizations? No. It works for nonprofits, government agencies, and even volunteer groups. Any group that makes repeated decisions can benefit. The same principles apply: map the actual flow, identify gaps, and redesign to send a different cultural signal.

What if the decision architecture is fine but the culture is still bad? That is possible. Decision architecture is one layer of culture, not the whole picture. If the architecture is healthy but the culture is toxic, look at other factors: leadership behavior, reward systems, or unresolved conflict. The Myriada Lens is a starting point, not a complete solution.

A common mistake is to treat the lens as a one-time project. Culture is dynamic, and decision architecture evolves. Schedule a quarterly 'decision audit' to check if the architecture still serves the culture you want. Another mistake is to focus only on formal decisions. Informal decisions — like who gets invited to a meeting — carry powerful cultural signals. Include them in your mapping.

What to Do Next: Specific Next Moves

You have the lens. Now apply it. Here are concrete next steps to take within the next week.

1. Pick one decision type that your team or organization makes regularly. Choose one that feels frustrating or slow. Write it down.
2. Map the actual flow for the last three instances. Use a simple list or diagram. Do not rely on memory alone; talk to two other people involved.
3. Identify one gap between the actual flow and what you want. Example: 'We want decisions to be fast, but every budget request needs three approvals.'
4. Design one small intervention to address that gap. Example: 'Delegate approval for requests under $5,000 to the team lead.'
5. Implement it for one month. Then check: did the cultural signal change? Are people feeling more trusted? Is speed improving? If not, adjust.

After that, expand to a second decision type. Share the lens with a colleague so you have a sparring partner. Over time, you will build a library of decision maps that reveal the true culture of your organization. The Myriada Lens is not a one-time fix; it is a practice. Start small, iterate, and let the architecture speak.