In a highly collaborative and fast-paced environment, assign explicit ownership for every feature, no matter how small. The goal isn't to assign blame for failures but to empower individuals with the agency to make decisions, build consensus, and see their work through to completion.
To accelerate your career, focus on developing 'agency'. This means moving beyond assigned tasks to proactively solve unspoken, systemic problems. Instead of chasing high-visibility projects, look for the unaddressed issues that keep leaders up at night. Solving these demonstrates true ownership and strategic value.
Effective delegation of decision-making authority is impossible without first ensuring leaders are deeply aligned on organizational objectives. When individuals are empowered to make choices but pull in different directions, the result is a quagmire, not progress. Alignment must precede autonomy.
To avoid stifling teams with bureaucracy, leaders should provide slightly less structure than seems necessary. This approach, described as "give ground grudgingly," forces teams to think actively and prevents the feeling of "walking in the muck" that comes from excessive process. It's a sign of a healthy system when people feel they need a bit more structure, not less.
In partnerships, tasks are often shared, leading to no clear ownership and constant follow-up. The "Fair Play" card system forces explicit assignment of both physical tasks (e.g., garbage) and invisible mental tasks (e.g., planning appointments), creating true ownership and freeing up mental bandwidth.
When a project stagnates, it's often because "everyone's accountable, which means no one's accountable." To combat this diffusion of responsibility, assign one "single-threaded owner" who is publicly responsible for reporting progress and triaging issues. This clarity, combined with assigning individual names to action items, fosters true ownership.
To avoid chaos in AI exploration, assign roles. Designate one person as the "pilot" to actively drive new tools for a set period. Others act as "passengers"—they are engaged and informed but follow the pilot's lead. This focuses team energy and prevents conflicting efforts.
Using the classic "ham and eggs" fable, projects fail when filled with "chickens" who are merely involved versus "pigs" who are fully committed. To ensure accountability, organizations must assign single-threaded leaders ("pigs") who own an outcome end-to-end, rather than committees of contributors.
Forcing innovations to "scale" via top-down mandates often fails by robbing local teams of ownership. A better approach is to let good ideas "spread." If a solution is truly valuable, other teams will naturally adopt it. This pull-based model ensures change sticks and evolves.
To encourage participation from everyone, leaders should focus on the 'why' behind an idea (intention) and ask curious questions rather than judging the final output. This levels the playing field by rewarding effort and thoughtfulness over innate talent, making it safe for people to share imperfect ideas.
Instead of faking expertise, openly admitting ignorance about technical details builds trust and empowers specialists. This allows you to focus on the 'what' and 'why' of the user experience, giving engineers and designers the autonomy to own the 'how', which fosters a more collaborative and effective environment.