Why V2 is a lie

In the plethora of projects I have had the privilege to work on, I’ve set hundreds (maybe thousands) of business requirements. These are things you need, things you’d like and friendly suggestions. In the process of determining the scope of the project, The Project Manager will “pare down” the business requirements to just enough to get the product out the door.

In an effort to give the business owner an exiguous amount of hope, the project manager will say, “we’ll include that in the v2 requirements”. Don’t believe them.


But it’s not the PMs fault. It’s the way it goes. The business needs to move on to the next customer facing feature or big idea, and cannot afford to keep looking back.

These are the trials and tribulations of an Information Architect.