The “Lost Art” of Business Requirements—Defining the “What,” Not the “How”

In the previous article, our illustrative analysis found manual follow-up failures affecting clients who represent 15% of revenue. We have evidence of the need for change. Now, we finally get to talk about the solution, right?

Not yet. Before you look at a single CRM demo, you have to master a skill that has become a bit of a lost art in the corporate world: Defining business requirements.

Most people skip straight to functional requirements. They make a list of features they want the software to have:

“It needs to have a mobile app.”

“It needs to send automated emails.”

“It needs a dashboard for the manager.”

These are “Hows.” They describe a tool, but they don’t describe a business outcome. A business requirement focuses on the “What.” It describes the state the business must reach to be successful.

Turning pain into requirements

Remember our 48 client complaints? Let’s turn those into requirements.

The Pain: Clients are being forgotten because there is no follow-up accountability.

The business requirement: Every client follow-up must have an accountable owner, an agreed deadline, and a defined response when overdue.

A measurable acceptance criterion could be that all overdue follow-ups receive an accountable review within one working day. Agree the timeframe with the business and validate it against the actual need.

Automated reminders or escalations are possible solution features. A shared work queue or an improved manual process might also meet the requirement. Compare the options before choosing the technology.

See the difference? We have defined an outcome and a way to assess it without specifying the tool. In this illustrative example, that requirement addresses follow-up failures affecting clients who represent 15% of revenue.

Requirements as a test of vendor claims

When a software salesperson sits down to show you their CRM, they are going to show you the “flashy” stuff—the AI predictors, the beautiful charts, the social media integrations.

Without documented business requirements, you’ll get distracted by the bells and whistles. You might buy the “Ferrari” of CRMs when what your business actually needs is a “Reliable Truck” that handles your specific commission calculations.

Your requirements list acts as your success criteria. It allows you to say to a vendor: “Don’t show me the AI. Show me how your approach supports clear ownership, agreed deadlines, and a documented response to overdue follow-ups.”

The “traceability” secret

The real magic happens when you can “trace” your requirements back to your work breakdown pyramid.

The problem: High-value clients are experiencing follow-up failures, putting those relationships at risk.

The Goal: Zero churn due to poor follow-up.

The requirement: Every agreed follow-up has an owner, a deadline, and a documented response when overdue.

The solution options: A team review process, a shared task list, or automated reminders—assessed against the same requirement.

When you can link your spending directly to your goals, you move from “project management” to strategic execution.

This brings us to the “Grand Finale” of the analysis process. You’ve mapped the mess, counted the cost, and defined what success looks like. Now, it’s time to move from a list of needs to a definitive choice.

Solution analysis compares ways to meet the requirements. “The Hash” is my name for the facilitated discussion that helps people weigh those options together.