How DCMA Put Business Relationship Management to Work | Case Study

When demand has nowhere to go

Commercial technology cycles keep getting shorter. Beck argues that the Department’s real problem isn’t access to innovation. Its internal processes often can’t absorb new capabilities fast enough, and weak demand governance is usually the reason.

At DCMA, demand never went away. It fragmented instead. With no reliable forum to review their requests, mission partners turned to personal networks and workarounds, or stopped asking. Constraints such as security, policy and workforce limits showed up late in the process, so everything felt slow. The result was a growing trust gap between the mission and the IT organization that served it.

Beck makes the point that DCMA isn’t unusual. Government oversight reviews have flagged the same pattern across the Department: governance boards that lose their cadence, intake that exists only on paper, and decisions that never get made.

Professionals, not liaisons

DCMA’s turnaround started with a choice about staffing. Its IT Strategy and Planning leadership didn’t hand coordination duties to existing staff or create informal liaison roles. They staffed the BRM function with certified practitioners who held or were working toward the BRMP and CBRM credentials.

Those BRMs soon found the root problem: nobody owned the work of getting requests ready for a decision. Instead of building a parallel structure, they stepped in to reconstitute the agency’s capability boards. They didn’t have decision authority. Their job was to make sure every request reaching a board was clear, complete and tied to strategy.

Beck sums up the difference this way. A liaison tells governance what stakeholders want. A certified BRM tells governance what the organization needs, then follows the request all the way through to delivery and value.

What you’ll find in the full case study

The story above is only the setup. The case study covers what happened next and what other organizations can learn from it, including:

• The results, with data. It explains how intake and board performance changed once certified BRMs took over, including a decision-timeliness standard that one capability board had missed for two years.
• What “resolved” really means. It shows why good governance is measured by decision quality and speed, not by approval rates.
• Why BRM, and not something else. It takes on a hard question: business analysts, PMOs and ITIL all address parts of the problem, so what gap does BRM close that they don’t?
• A blueprint for other DoD components. It lays out the conditions, enablers and risks that decide whether the model works in organizations like DISA, DLA and Service-level IT shops.
• An honest look at the limits. It discusses where the evidence stops and the next steps Beck recommends.

Read the full paper

If you’re trying to make the case for BRM in your own organization, in government or not, this case study gives you a real-world example to point to. It is grounded in practice and candid about what it takes.