Business Relationship Management at SMPH
Why the BRM Role Exists
At the UW School of Medicine and Public Health, technology decisions directly impact research productivity, clinical operations, faculty advancement, and financial stewardship.
The BRM role exists to ensure:
-
Technology investments align to documented business objectives.
-
Departments make informed, data-driven technology decisions.
-
IIT resources are directed toward high-impact outcomes.
-
Misaligned, reactive, or redundant investments are prevented.
BRMs are strategic partners accountable for alignment between business intent and IT capability. If a department invests in technology and does not realize expected value, the BRM shares accountability for the alignment failure.
The BRM Value Proposition
The BRM role is anchored in three core pillars:
1. Strategic Alignment
Translate business partner strategy into prioritized, funded, and executable IIT initiatives.
-
-
Connect Business Partner (department) goals to IIT service capabilities.
-
Ensure technology requests are tied to measurable outcomes.
-
Influence portfolio sequencing and prioritization decisions.
-
Surface trade-offs across competing demands.
-
Result: Technology investments directly support academic, clinical, and research priorities.
2. Demand Shaping
Prevent misaligned investments before they occur.
-
Engage early — before vendor selection or procurement.
-
-
Clarify business problems before solution discussions.
-
-
Challenge assumptions and surface alternatives.
-
Leverage existing IIT services where appropriate.
Result: Reduced duplication, stronger ROI, fewer reactive IT requests.
3. Advocacy & Executive Interface
Represent business partner needs within IIT and IIT realities within departments.
-
Ensure leadership understands constraints, capacity, and risk.
-
-
Communicate clearly on priority conflicts and trade-offs.
-
-
-
Facilitate cross-department alignment when interests compete.
-
-
-
Drive decision clarity when leadership is ambiguous.
-
Result: Informed decisions, executive confidence, reduced friction. 
What a BRM Actually Does
BRMs operate at the portfolio and decision-support level — not at the execution level.
A high-performing BRM:
-
Meets regularly with business partner leadership.
-
Reviews portfolio health and investment alignment.
-
Surfaces risks before escalation.
-
Shapes demand before procurement begins.
-
Facilitates definition of success metrics for initiatives.
-
Develops or co-develops business cases and ROI analysis.
-
Identifies cross-department collaboration opportunities.
-
Challenges unclear problem statements.
-
Escalates strategically when priorities conflict.
Role Boundaries (Intentional by Design)
To safeguard strategic capacity, a Business Relationship Manager (BRM) remains informed and actively engaged across the IT portfolio without assuming responsibility for operational or technical execution. The following table provides further clarification regarding the role of the BRM.
|
Out of Scope Area |
BRM Relationship Role |
|---|---|
|
Technical Support & Maintenance |
Do not troubleshoot; escalate systemic issues and ensure awareness of patterns impacting the department. |
|
Project Management |
Do not manage timelines, resources, or budgets; stay engaged on “what” and “why”; |
|
Code & Development |
Do not build systems; ensure business objectives are clear before development begins. |
|
Business Partner Operations |
Do not own business processes; influence alignment and improvement discussions. |
|
Data Analytics & BI Production |
Do not generate reports; help define business intelligence requirements. |
|
Staff Management |
Do not have direct reports and or personnel management authority within departments; work with managers and supervisors to align resources and communicate business needs. |
When BRMs drift into execution ownership, the school loses strategic capacity.
The role is intentionally designed to operate at the alignment and decision level.
BRM Relationship Maturity Model
Relationship maturity varies by department and evolves over time.
Level 1 – Reactive (Ad-Hoc)
Interaction Pattern: Engaged only during crises or urgent requests.
Value Delivered: Stability and issue awareness.
Primary Activity: Information relay and problem escalation.
Signal:
-
BRM engaged after vendor selection or crisis.
Level 2 – Transactional (Order Taker)
Interaction Pattern: Department requests specific tools; BRM facilitates routing.
Value Delivered: Fulfillment and coordination.
Primary Activity: Liaison and intake management.
Signal:
-
Engagement begins after solution already selected.
Level 3 – Trusted Advisor
Interaction Pattern: Department consults BRM before making technology decisions.
Value Delivered: Optimization and risk avoidance.
Primary Activity: Consultative recommendation and opportunity identification.
Signal:
-
BRM invited into planning discussions.
-
Department asks: “What are our options?”
Level 4 – Strategic Partner
Interaction Pattern: BRM participates in annual planning and leadership discussions.
Value Delivered: Innovation, growth, portfolio alignment.
Primary Activity: Co-develop business cases, quantify ROI, shape investment sequencing.
Signal:
-
BRM engaged before budget decisions.
-
BRM influences priority trade-offs.
-
Technology roadmap integrated into business partner strategy.
The goal of the BRM function is to operate at Level 4 across SMPH.
How We Measure BRM Effectiveness
The BRM role is evaluated on outcomes, not activity volume.
Key indicators include:
-
Percentage of technology investments tied to documented business objectives.
-
Early engagement rate (BRM involved before vendor selection).
-
Reduction in reactive or redundant IT requests.
-
CAO and leadership satisfaction.
-
Clear definition of success metrics for major initiatives.
-
Portfolio transparency across departments.
BRMs are accountable for alignment quality — not ticket counts.
How to Engage a BRM
Engage your BRM when:
-
You are considering purchasing software or engaging a vendor.
-
You are planning a major operational or strategic initiative with technology impact.
-
You need clarity on IT capabilities or constraints.
-
You are preparing for budgeting discussions involving technology.
-
You want to improve a business process that may involve IT.
The earlier the engagement, the stronger the outcome.
The Standard We Hold Ourselves To
BRMs at SMPH:
-
Own business outcome alignment.
-
Listen before prescribing.
-
Challenge assumptions respectfully.
-
Translate strategy into actionable initiatives.
-
Protect both Business Partner (business partner) and IIT capacity.
-
Operate with executive presence and clarity.
BRMs are strategic partners accountable for alignment between business intent and IT capability. If a department invests in technology and does not realize expected value, the BRM shares accountability for the alignment failure.