Ideas

Essays and reflections on digital governance, organizational systems, and the practice of designing technology for complex operational environments.

Decision Architecture in Complex Systems

February 2026

Most organizations struggle not with making decisions, but with structuring decision-making. This essay explores how digital systems can create architecture for organizational decisions without removing human judgment.

Organizations make thousands of decisions every day. Most of these decisions are small, reversible and delegated to individuals or teams who have the right context. But some decisions require coordination, some need approval, some must be documented, and some should follow a structured process.

The challenge is that most organizations have no systematic way to distinguish between these types of decisions. Everything either becomes a formal approval process (creating bottlenecks) or operates informally (creating risk and inconsistency).

Decision architecture is the practice of designing systems that structure how decisions get made without prescribing what decisions should be. It's about creating clarity around: Who can decide what? What information do they need? What must be documented? When does a decision need escalation? How do we learn from decisions over time?

Good decision architecture does three things: First, it makes decision authority explicit. Everyone knows who can decide what, and under what constraints. Second, it creates information pathways. Decision-makers have access to the right context at the right time. Third, it enables learning. Decisions and their outcomes are captured in ways that help the organization improve over time.

Digital systems are particularly good at supporting decision architecture because they can embed these structures into workflows. But the technology is only useful if it reflects how the organization actually operates. Bad decision architecture—whether embedded in digital systems or not—either gets ignored or creates bureaucracy without value.

Digital Governance Beyond Technology

January 2026

Digital transformation often focuses on automation and efficiency. But the most important opportunity is using technology to enable better governance—creating structures for accountability, transparency and learning in complex organizations.

When organizations talk about digital transformation, they usually mean automating processes or analyzing data. These are worthwhile goals, but they miss the most fundamental opportunity: using technology to govern better.

Governance is about how organizations make and enforce decisions, allocate resources, manage risk, and ensure accountability. In most organizations, governance happens through a mix of policies, approval processes, oversight committees, and informal norms. It's often opaque, inconsistent, and difficult to improve because there's no systematic way to see how it's working.

Digital systems can make governance visible and improvable. They can create clear audit trails, make decision-making transparent, surface patterns in exceptions, and enable learning from past decisions. But this requires thinking about technology differently—not as a tool for automation, but as infrastructure for organizational governance.

The best examples of digital governance come from regulated industries where traceability and accountability are non-negotiable. But every organization can benefit from governance systems that create clarity about who decides what, how resources are allocated, and how accountability works.

The key is to start with governance needs rather than technological capabilities. What decisions require transparency? Where is accountability unclear? What patterns in exceptions suggest systemic issues? Once you understand the governance challenges, technology becomes a tool for creating structure rather than an end in itself.

Designing for Organizational Memory

December 2025

Organizations forget. Projects end, people leave, decisions are made without context. This essay examines how digital systems can serve as organizational memory—not just storing information, but preserving context and enabling learning.

Every organization has experienced this: someone leaves, and critical knowledge leaves with them. A decision gets made without understanding why a similar decision failed three years ago. A project team solves a problem that another team already solved. The organization keeps learning the same lessons because it has no memory.

Organizational memory isn't about storing more documents or creating more processes. It's about capturing decisions and their context in ways that future teams can learn from. This requires designing systems that record not just what was decided, but why it was decided, what alternatives were considered, and what happened as a result.

The challenge is making this memory useful. Most knowledge management systems become digital landfills—everything is stored, nothing is findable, and nobody trusts that the information is current. Good organizational memory systems are selective about what they capture, rigorous about keeping information current, and thoughtful about how knowledge gets surfaced when it's needed.

Digital platforms can serve as organizational memory if they're designed for it. This means capturing context during normal workflows rather than asking people to document separately. It means related connecting decisions so patterns emerge. And it means creating search and discovery tools that help people find relevant knowledge when they need it.

The payoff is significant. Organizations with good memory make better decisions, onboard new people faster, and improve continuously rather than repeatedly solving the same problems. But building this memory requires thinking about digital systems as long-term infrastructure for learning rather than short-term tools for efficiency.

Exception Management as Organizational Intelligence

November 2025

Standard processes are important, but exceptional cases reveal how organizations really work. This essay argues for treating exceptions as strategic intelligence rather than operational annoyances.

Every organization has standard processes for routine work. And every organization has exceptions—cases that don't fit the standard process, require judgment, or demand special handling. Most organizations treat exceptions as problems to be minimized. But exceptions are actually sources of organizational intelligence.

Exceptions reveal where processes don't match reality. They surface edge cases that process designers didn't anticipate. They show where judgment is needed and where rules are too rigid. And they often point to opportunities for improvement—if the organization is paying attention.

The problem is that most organizations handle exceptions informally. Someone escalates to a manager, the manager makes a judgment call, the exception gets handled, and everyone moves on. There's no systematic way to learn from exceptions or identify patterns that might indicate systemic issues.

Digital systems can change this by formalizing exception management. Instead of handling exceptions through email and informal escalation, organizations can create structured pathways for exceptions—routing them to appropriate decision-makers, documenting the reasoning, and capturing patterns over time.

This transforms exceptions from operational headaches into strategic intelligence. An organization that systematically tracks exceptions can see: What types of exceptions occur most frequently? Which processes generate the most exceptions? What patterns emerge? Are exceptions increasing over time? This information guides process improvements and policy changes in ways that standard metrics can't.

The key is designing systems that make exception handling visible without making it bureaucratic. Exceptions need judgment, so the system should support decision-makers rather than constrain them. But it should also create visibility and enable learning so the organization continuously improves.

Coordination Costs in Digital Organizations

October 2025

Digital tools promise to reduce coordination costs, but they often increase them by adding new communication channels and creating information overload. This essay explores how to design systems that actually reduce the cost of coordination.

One of the promises of digital transformation is reduced coordination costs. Email, chat, project management tools, and collaboration platforms should make it easier for people to work together. But many organizations find that digital tools increase coordination costs—there are more meetings, more messages, and more time spent managing information rather than doing work.

The problem is that most digital tools optimize for communication rather than coordination. They make it easy to send messages or share updates, but they don't reduce the fundamental challenge of coordination: aligning work across people who have different information, different priorities, and different constraints.

Real coordination requires shared context, clear responsibilities, and visibility into what others are doing. Communication tools can support this, but they don't automatically create it. In fact, they can make things worse by creating more channels for miscommunication and more places where critical information gets lost.

To design systems that reduce coordination costs, start with the work rather than the communication. What decisions need coordination? What information do people need to do their work? What handoffs occur between teams? Once you understand the coordination needs, you can design digital systems that create the right structures.

This often means fewer tools, not more. Instead of adding another communication channel, create visibility into work status. Instead of another approval workflow, clarify decision authority. Instead of another meeting, create asynchronous ways for people to stay aligned. The goal is coordination with minimum communication—systems that keep people aligned without requiring constant interaction.

These essays reflect ongoing thinking about how organizations can use digital systems to govern better, coordinate more effectively, and learn continuously. If you're interested in discussing these ideas or exploring how they might apply to your organization, I'm always glad to have the conversation.