Products, Not Projects
In “The Politics Of Projects“, Robert Block rightly states: “People want products, not projects“. The ideal project takes zero time, no labor, and no financial investment. The holy grail is to transition from abstract desire to concrete outcome in no time flat :). Nevertheless, for any non-trivial product development effort requiring a diverse team of people to get the job done, some sort of project (or, “coordinated effort” for you #noprojects advocates) is indeed required. Whether self-organized or dictator-directed, there has to be some way of steering, focusing the effort of a team of smart people to achieve the outcomes that a project is expected to produce.
At the simplistic BD00 level of comprehension, a project is one of two binary types: a potential revenue generator or a potential cost reducer.
Startups concentrate solely on projects that raise revenue. At this stage of the game, not a second thought is given to cost-reduction projects – the excitement of creating value reigns. As a startup grows and adds layers of “professional” management to control the complexity that comes with that growth, an insidious shift takes place. The mindset at the top flips from raising revenue to reducing costs and increasing efficiency. In large organizations, every employee has experienced multiple, ubiquitous, top-down “cost reduction initiatives“, the worst of which is the dreaded reduction-in-force initiative. On the other hand, org-wide initiatives to increase revenues are rare.