{"id":50,"date":"2026-04-12T21:23:45","date_gmt":"2026-04-12T21:23:45","guid":{"rendered":"https:\/\/practicalmbse.com\/?p=50"},"modified":"2026-04-16T22:30:07","modified_gmt":"2026-04-16T22:30:07","slug":"requirements-why-you-your-project-manager-should-care","status":"publish","type":"post","link":"https:\/\/practicalmbse.com\/?p=50","title":{"rendered":"Requirements – Why You & Your Project Manager Should Care"},"content":{"rendered":"
\n

Requirements aren’t paperwork – they’re engineering.<\/mark><\/strong>
If you’ve ever wondered why writing them feels painful, slow, or like it stopping “real work” from happening, this is the article for you.<\/p>\n\n\n\n

Here’s the blunt truth:<\/mark> Getting requirement right early is the different between a project that lands cleanly and one that burns time, money, and reputation later.<\/em><\/p>\n<\/div>\n\n\n\n

<\/p>\n\n\n\n

Have you ever been writing requirements and thought “I can’t be arsed for this – we know what we are building why are we writing all this down<\/em>?”

Or have you heard your PM say something like “We just need it delivered so we can get paid<\/em>“

You’re not alone and I get it.

This is what some people don’t understand: requirements aren’t paperwork!<\/mark><\/strong> They’re the shared language between engineering intent<\/mark><\/strong> and project reality<\/mark><\/strong>. They’re the thing that stops your project from quietly setting itself on fire six months down the line.
<\/p>\n\n\n\n

<\/div>\n\n\n\n

Why Requirements Actually Matter<\/h3>\n\n\n\n

Requirements drive everything – design, cost, schedule, customer satisfaction, and ultimately whether the thing you’re building is legal, safe and sellable.

Miss requirements early?
You will<\/em> pay for them later.

Miss major functional or legislative requirements? You get unhappy customers, blown budgets, and a reputation that follows you around like a bad smell.

Let’s make it real.<\/p>\n\n\n\n

<\/div>\n\n\n\n

A Quick Example (That Happens More Often Than Anyone Admits)<\/h3>\n\n\n\n

You’re designing a vehicle. Tight timescales. Pressure from the business to hit payment milestones. Requirements are rushed. Corners get cut. A few “we’ll sort that later” items slip through.

One of those items? A key legislative requirement.<\/p>\n\n\n\n

You don’t notice until Critical Design Review<\/a>.<\/p>\n\n\n\n

Suddenly the entire electrical architecture is non‑compliant — and illegal to sell.<\/p>\n\n\n\n

Now you’re looking at:<\/p>\n\n\n\n