Organizations are cognitive systems, not just social ones. They have default modes for perceiving reality, storing memory, allocating attention, and making decisions. Most organizations perform far below their potential because these cognitive functions are designed accidentally, if at all.
In most organizations today, responsibility fragments across silos: leadership sets direction, a program office coordinates execution, IT provides tools, HR manages talent. But the architecture that determines what the organization can notice, how quickly it can learn from what it notices, and whether it can coordinate action based on what it learns—that falls through the gap.
We close that gap.
We start by making your governance and cross-functional workflows legible. From there, we fit them to your actual needs and make them durable in the systems your team already uses. Engagements range from fixing a single, broken workflow to rebuilding how the whole organization coordinates. Typical projects include:
- Asana architecture and rollout
- CRM/martech integration
- OKR design
- Cross-functional process design
- Performance management systems
- AI governance and tooling
- Knowledge management across systems
- Executive reporting and dashboards
The principles below guide how we approach this work. The unifying theme is coherence across tools, teams, representational layers, and information types.
Core principles
- Build for observability, not monitoring. A major software trend over the past decade is the shift from static monitoring to observability—ensuring work is traceable as it happens, so new questions can be answered later, not just the ones anticipated in advance. That same shift is embedded, often unrecognized, in platforms like Asana, Slack, and Salesforce. Consistent data structure across these systems is paramount, because it determines what can later be learned: which Slack thread, status update, Google Drive folder, or executive decision is canonical, and how conversations and results accumulate over time. When work is observable, executive oversight improves without micromanagement, and redundant status reporting disappears. The work itself becomes the system of record.
- Design organizations that rebalance themselves. Most organizations only negotiate the trade-offs between efficiency, resilience, stability, and agility when something forces them to—an offsite, a restructure, a crisis. With richer data models and AI across the toolchain, these trade-offs can be rebalanced continuously, as conditions change, rather than only when someone calls a pause. Strategic posture becomes an ongoing capability, instead of an effortful regrouping exercise.
- Process over tools. AI tools change by the month. We help organizations move from tool-centric to flow-centric thinking, so the underlying processes stay intact as tools quickly proliferate and evolve.
- Make goals real. Most goal systems fail gradually because they live on a different representational plane than the work itself: the OKR that becomes theater or gets serially overwritten; the strategic plan that sits in a drawer. The underlying problem relates to knowledge representation. Goals and tasks should be different views of the same structure, in a single data model—not two conflicting realities that teams reconcile in their minds day by day, or at the end of each quarter.
- Asana as cognitive infrastructure. There are many work management tools, but past a certain level of complexity, there is no real replacement for Asana. An Asana rollout is never just a tooling project—it makes ownership, dependencies, and avoidance visible, and exposes cultural debt with ruthless clarity. We often serve as an acting Chief Asana Officer: designing and implementing Asana for performance management, revenue functions, and executive oversight; making sure the system holds; and then transferring ownership to internal teams as capacity allows.
- Task alignment before team alignment. People coordinate primarily around shared work, not shared values. Yet organizations invest heavily in “teambuilding” and “culture” while leaving actual collaboration workflows undesigned. Cross-functional coordination usually hinges on a handful of specific handoffs: story banking between program teams and comms, CRM hygiene between marketing and sales, release coordination between product and marketing. Designing clear workflows for these handoffs produces more reliable alignment than asking adjacent teams to understand each other better, or meet more often.
- Isolate signal. The volume of content in every internal and external channel now exceeds what any human can read. We design reporting and sampling systems that let leaders skim intelligently—surfacing leading indicators, and escalating what actually requires judgment.
- Emotional intelligence as a discipline. Emotions are not obstacles—they’re high-density data streams. Our coaching and advisory work helps leaders appreciate finer-grained emotional perception—not to manage feelings instrumentally, but to let them circulate as actionable and valuable intelligence.