CHAPTER 15
Staff Projects
Read It
"You must complete a Staff project before being promoted to Staff" isn't a universal truth, but it often appears as a hidden requirement only at the final review. Some people advance through long-term stable influence, others by changing companies. Yet a project that is ambiguous, contested among stakeholders, and highly visible in both success and failure compresses all the capabilities Staff work requires into one arena. It isn't a certificate—it's a form of integrated training that's hard to replace.
Open full image ↗Draw It
What defines a Staff project isn't scale, but the overlap of three complexities: the problem has no clear answer, stakeholders' goals conflict, and the outcome can't hide in a local scope. Crossing these three dimensions separates a "big project" from a "Staff project," and explains why technical difficulty alone isn't enough.
Rethink It
Before accepting a project, instead of asking only about budget, headcount, and tech stack, ask: Who defines success differently? Who will see the failure? When conflicts arise, do I have enough authority to keep moving? If none of these questions apply, it may just be a large delivery. If all three exist at once, you're facing a genuine exercise in senior influence.
Take It With You
The value of a Staff project isn't that it fits into a promotion packet; it's that it forces you to keep making judgments under ambiguity, conflict, and visible pressure.