Blogs / Design Pulse: Reading the Health of a Design Organization
Design Pulse: Reading the Health of a Design Organization

Design, Extractives · 5 Min Read

Design Pulse: Reading the Health of a Design Organization

How recurring observation helps design leaders connect capabilities, organizational attention, and changing needs.

When activity stops telling you enough

At Meta, quick shifts in priorities brought constant context switching and noticeable burnout to my team. We were working, but activity alone could not tell me whether our effort was building the capabilities the organization needed. Some commitments continued as priorities moved elsewhere. Other needs became more pressing without a corresponding change in capacity.

The leadership problem was not simply how to get more work done. It was how to understand what our work was sustaining, what it was helping us become capable of doing, and where the relationship between the two had started to break down.

I developed Design Pulse to examine that relationship regularly and guide capability development, resource allocation, and decisions about which commitments to reconsider.

A design organization can be busy, productive, and apparently functional while gradually losing alignment with what its organization needs.

What Design Pulse makes visible

Design Pulse is an evolving practitioner framework for understanding the health of a design organization in context. It examines capabilities across five organizational layers through three complementary categories: “We focused,” “We continued,” and “We identified.”

Here, health is not a single score. It concerns how capabilities, attention, and organizational needs relate to one another.

A strong capability may receive little attention because other demands have become urgent. A familiar practice may keep consuming resources after its purpose has weakened. A capability gap may remain unresolved even while the team is deliberately investing in it.

The approach connects team observations with leadership judgment. Team contributions help reveal what is happening; leadership interprets those observations alongside changing priorities and constraints. Intentionality concerns where leaders and teams deliberately direct effort. Attention concerns what actual activities reveal about priorities, maintenance, and overlooked commitments. Attunement means recognizing when changing conditions require priorities or practices to be reconsidered.

These ideas work together: what we intend to support may differ from what our activity reveals, and changing conditions may alter what deserves a response. The purpose is not to chase every organizational shift, but to recognize when a shift calls for a different decision.

Design Pulse is neither a productivity tracker nor a team-health survey. It helps leaders decide what to develop, maintain, reconsider, or deliberately leave uncovered.

Three complementary categories

We focused

“We focused” records active investment: time, resources, or deliberate effort directed toward developing capability. This might include strengthening research, building leadership skills, improving quality systems, or changing collaboration with engineering. The question is not merely whether work happened, but what capability the investment was intended to support.

We continued

“We continued” records capabilities and practices maintained at their current level. Routine one-on-ones, team norms, and operating rhythms can provide essential continuity. Maintenance is not automatically a lesser contribution than development. Keeping something useful working can make other investments possible.

But a practice can persist because it remains valuable, or because nobody has reconsidered it. Continuation deserves examination, not automatic approval or dismissal.

We identified

“We identified” records emerging concerns: capability gaps, misalignments, constraints, or demands on resources that warrant attention. Identifying a condition does not mean it can immediately be resolved or that an individual has failed. It makes the condition available for interpretation.

These are complementary observations, not exclusive boxes. A team may focus on developing research capability while identifying unresolved research-capacity constraints and continuing practices that already support useful research. Together, the categories show what we are investing in, sustaining, and recognizing as needing attention.

Five organizational layers

A difficulty experienced by an individual designer may originate in team infrastructure, product delivery, or company priorities. Examining only the layer where it appears can lead to the wrong response.

Personal: leadership development

The Personal layer examines how individual development contributes to broader organizational capability. Leadership training, feedback, and cross-team relationships matter in relation to the responsibilities people are taking on. Does development prepare them for their actual challenges, rather than simply adding skills?

Team: collective infrastructure

The Team layer examines whether people can work as a cohesive unit. Skills, hiring, career paths, norms, and bandwidth shape collective capacity. Strong individual performance does not necessarily resolve a shared capability gap or a culture rewarding personal wins over collective value.

Product: conditions for delivery

The Product layer examines how design operations and cross-functional arrangements enable product work. Quality systems, collaboration, operating rhythms, and capacity across disciplines affect delivery. If designers cannot ship because engineering capacity is constrained, design effort alone cannot explain the issue.

Strategy: the connection between direction and execution

The Strategy layer examines whether visions and plans influence decisions and produce meaningful action. A strategy can remain visible without being useful. Does strategic work change priorities and practice, or have visions become too detached from execution?

Company: design’s organizational position

The Company layer examines design’s relationship with business direction, planning, and organizational expectations. Unlike Product’s concern with delivery or Strategy’s translation of direction into action, it asks whether design’s role, commitments, and contribution remain connected to what the wider organization is trying to achieve.

These are not five separate checklists. A delivery constraint may require a resource decision beyond the team. Changing company direction may alter capability needs without making people who hold existing expertise less valuable.

From observation to leadership decision

Tracking our design roadmap helped me see how intended work changed as priorities shifted. Looking back at those commitments, we realized that roughly one-fifth of our effort had gone toward maintenance and work that was no longer strategically prioritized, more than we had anticipated. The important finding was the difference between intended priorities and where effort was actually going.

The observation was that planned work kept changing. The pattern was that maintenance and other commitments occupied more capacity than we had recognized. Interpretation required distinguishing necessary continuity from work that no longer justified its demands.

During layoffs, with fewer people and shifting goals, Design Pulse helped guide decisions to drop non-essentials.

We moved from “do everything with less” toward accepting certain gaps.

This was not only a Product-layer question about delivery. It connected Team capacity with Strategy and Company priorities. Asking designers to work harder would not, by itself, resolve that relationship.

The sequence matters: observe, recognize a pattern, interpret its significance, make a leadership decision, and continue examining what follows. Subsequent observations help leaders reconsider whether a decision still fits the conditions.

Weekly observation and quarterly interpretation

Design Pulse combined team contributions with interpretation, prioritization, and decision-making by design leadership.

Weekly observation kept it close to actual work. Across the five layers, the team contributed observations about what received investment, what continued, and what concerns had emerged. This created an ongoing record rather than relying on later recollection.

Quarterly interpretation provided a longer view. Leadership could examine whether persistent concerns indicated structural constraints, sustained investments still served a purpose, or continued work had become difficult to justify.

Weekly observations make changing conditions visible; quarterly interpretation distinguishes passing difficulties from recurring patterns and connects them to priorities and resources. Team observations bring knowledge of the work; leadership remains responsible for interpreting competing needs and making trade-offs explicit.

What implementation taught me

Maintenance deserves recognition before it deserves reduction. Routine work can protect quality, relationships, and continuity. Treating all maintenance as waste would undermine capabilities the organization still needs.

Identifying a gap must not become a way to assign individual blame. A constraint may reflect staffing, cross-functional dependencies, changing priorities, or commitments that no longer fit together. Naming the condition creates the possibility of a better decision; it does not explain the condition by itself.

Current organizational needs cannot be the only horizon. If every shift redirects development, a team may become responsive in the short term while losing capacity to meet future demands. Leaders have to judge what should change and what is worth sustaining through uncertainty.

Design Pulse does not remove these tensions. It gives them a recurring place in leadership practice and makes deliberate non-coverage possible.

Acknowledging a gap, understanding the trade-off, and choosing not to address it yet can be more responsible than maintaining the fiction that everything remains achievable.

The aim is not to keep every capability equally developed or every commitment intact. It is to understand which capabilities need investment, which deserve continuity, and which commitments must change. Organizational health depends on understanding the relationship between what a team can do, what it gives its attention to, and what its circumstances require.