Insight: Apple's 'DRI' Org Structure
Apple's functional organizational structure, which relies on "Directly Responsible Individuals" (DRIs), is being praised for its effectiveness in large-scale projects. The model is cited for aligning incentives and reducing bureaucracy by assigning clear ownership for every component of a project.
- The DRI concept was institutionalized by Steve Jobs after his return to Apple in 1997, when he reorganized the company into a functional structure with a single P&L. This was done to eliminate the infighting between business units that he believed was stifling innovation. - Within Apple's culture, the DRI's name is placed next to each action item on a meeting agenda, making it transparent who is accountable for every task. This practice extends from major initiatives down to individual bug reports, ensuring there is never ambiguity about ownership. - A common misconception is that the DRI must perform all the work; however, a key part of the role is effective project management and delegation. The DRI is the go-to person for updates and decisions, but their primary function is to drive the project forward, not necessarily to execute every component themselves. - For executive communication, a widely used framework is BLUF (Bottom Line Up Front), which advocates for starting with the main point or request in the first line of any message or presentation. This respects leaders' limited time and avoids them having to dig through background details to understand the key takeaway. - When structuring a persuasive argument for a leadership review, the PREP framework (Point, Reason, Example, Point) is highly effective. This involves stating your main argument, explaining the reasoning, providing a concrete example or data, and then restating the main point to reinforce it. - When presenting engineering work to senior leadership, frame the update around business impact rather than technical metrics. For example, instead of focusing on code commits, report on how engineering predictability has improved on-time delivery from 67% to 85% in the last quarter. - A critical step before presenting to executives is to align with stakeholders beforehand, a practice sometimes called *nemawashi*. Circulating a structured document detailing your proposal to peers and stakeholders can help gather feedback and reduce the chance of surprises during the actual meeting. - To simplify complex technical topics for a non-technical executive audience, use analogies to bridge concepts, such as explaining a pressure valve as a "traffic light for pressure flow." It is also crucial to ensure every slide or graphic answers the implicit question in an executive's mind: "So what?".
