Family enterprises face a unique leadership challenge right now: digital technology is accelerating at unprecedented speed, while some of the most consequential and complex decisions require broad alignment across generations, owners, and operational leaders.
Enterprise Resource Planning (ERP) are the software systems that drive information flow through a business. New ERP implementations are major investments, demanding projects, and perfect software systems do not exists. Hence, ERP selection may be one of the most complex and expensive decisions a family enterprise makes. It touches nearly every function, reshapes how information flows, and locks in long-term capabilities.
The risk is real in both directions:
Move too slowly and you fall behind competitors who modernize faster.
Move too fast without alignment and you pay for it in rework, politics, adoption failure, and expensive course corrections.
The goal isn’t speed at all costs. The goal is decision velocity with strategic coherence, making timely decisions that align today’s needs with tomorrow’s reality.
That’s where a clean alignment cascade supported by the RACI decision model creates clarity, confidence, and efficient decision-making control.
Avoiding Decision Pitfalls: The alignment cascade
In a family enterprise, alignment has layers. When one layer is fuzzy, the layers below improvise and that’s where decision-making slows down.
Family alignment: Clarity on identity and purpose: legacy, values, and what “success” means beyond money.
Owner alignment: Clarity on the ownership agenda (return expectations, liquidity needs, time horizon, reinvestment appetite, and risk tolerance).
Governance alignment: Governance is the stewardship layer. It establishes the enterprise guardrails that keep decisions coherent over time:
Risk posture: acceptable vs. unacceptable risks
Return priorities: growth vs. dividends vs. reinvestment balance
Long-term strategic direction: 3–10 year view
Culture and enterprise health: values in practice, leadership behavior, talent
Control environment expectations: financial integrity, compliance, cybersecurity posture
Capital allocation principles: how big bets are evaluated and justified
Operational management alignment: Translation into execution: priorities, plans, resources, process ownership, accountability, and cross-functional coordination.
Employee alignment: Role clarity, stable priorities, and confidence that leadership decisions will stick.
Why generational decision alignment is hard: different generations often carry different risk memories, time horizons, and definitions of “responsible leadership.” Alignment doesn’t remove disagreement, it prevents disagreement from freezing progress and leads to productive conversations.
RACI Clarified
RACI is a simple framework that helps stakeholders create shared clarity for who does what, when, and why in a decision or process:
R = Responsible: the person(s) driving the work and producing deliverables
A = Accountable: the single owner of the final decision and outcome.
C = Consulted: people whose input materially improves the decision before it’s made
I = Informed: people who need to know the decision and rationale after it’s made
RACI creates speed without chaos because it does three things:
Creates clarity: No more “I thought you owned that.” No more “we’re waiting on everyone.”
Builds confidence: Teams move when they trust the pathway and believe decisions won’t get reversed later.
Enables efficient decision-making control: Leaders maintain appropriate oversight through the “A” role, while execution moves through the “R” role without bottlenecking at the top.
Two rules that make RACI work:
Only one “A.” If more than one A, we get decision-by committee and no accountability.
Limit “C.” Too many consulted voices leads to friction and slow motion.
ERP selection: the perfect test case (and why single-point accountability matters)
ERP selection is complex because it isn’t one decision—it’s a multi-stage commitment that stretches from early requirements through long-term adoption. Most ERP failures don’t happen because the team “picked the wrong software.” They happen because accountability is fragmented:
One group writes the RFP
Another group selects the software
Another group “runs the implementation”
Internal teams struggle with competing interests, needs, and priorities
And nobody truly owns the end-to-end outcome
When accountability breaks across phases, the project becomes vulnerable to decision drag, cross-functional conflict, scope creep, and adoption failure. This is especially true in a family enterprise where alignment across generations and functions can be hard-won and easy to lose.
The key principle: one Accountable owner from RFP → selection → implementation
For ERP projects, the RACI needs one A (Accountable) who carries ownership from:
Request for Proposal (RFP) development
ERP + implementation partner selection
Implementation execution and adoption
This person keeps the project moving at the exact moments it’s most likely to stall: tradeoffs, resistance, capacity constraints, political pressure, and “we’ll do it later” decisions.
What “Accountable” really means in ERP
The Accountable owner must have enough influence and authority to navigate:
Decision obstacles: tradeoffs between cost, speed, customization, and future capability
Change obstacles: process redesign, role shifts, training requirements, legacy behaviors, organizational culture, structure, and uncommitted leadership
Adoption obstacles: habits, workarounds, skepticism, productivity dips
The authority needed to navigate these obstacles can come from role/position and/or subject matter expertise. The real test is simple: When the project hits resistance, can this person make progress without the organization waiting for a rescue?
Example: RACI for ERP selection built for end-to-end accountability
Non-negotiable structure
One Accountable leader (A) owns the ERP effort end-to-end.
Multiple people can be Responsible (R) for work-streams.
The Consulted group stays purposeful (input that materially improves the decision).
The Informed group gets consistent updates and rationale to reduce rumor, re-litigation, and reversals.
| ERP Lifecycle Step | Responsible (R) | Accountable (A) (same person throughout) | Consulted (C) | Informed (I) |
|---|---|---|---|---|
| Define outcomes & success metrics that meet today & future needs | IT Lead + Process Owners | ERP Program Owner (A) | CFO, Sales Lead, HR/Change Lead | CEO/President, Board/Owners |
| Build requirements + develop RFP | Process Owners + IT Lead | ERP Program Owner (A) | Security, Finance, frontline SMEs | Department teams |
| Vendor shortlist + demo design | IT Lead + PM | ERP Program Owner (A) | Process Owners, Security, CFO | CEO/President |
| Evaluate vendors + scorecards | IT Lead + PM | ERP Program Owner (A) | Process Owners, external advisor | CEO/President, Board (as needed) |
| Select ERP + implementation partner | CFO + IT Lead + PM | ERP Program Owner (A) | Governance/Board (guardrails), Legal | Owners, leadership team |
| Implementation planning (timeline, resourcing, change plan) | PM + Workstream Leads | ERP Program Owner (A) | Department heads, HR/Change | Org-wide |
| Implementation execution + adoption | Workstream Leads + HR/Change Lead | ERP Program Owner (A) | Department leaders, training lead | All employees |
| Go-live readiness + stabilization (hypercare) | PM + IT + Workstreams | ERP Program Owner (A) | Finance, Ops, Security | Org-wide |
Note: The “ERP Program Owner” can be a COO, CTO, CFO, or Organizational Development leader or another leader with sufficient authority and influence to direct the action of others across the whole organization. What matters is the person in the role has the authority, credibility, emotional intelligence, and influence to navigate cross-functional friction and keep decisions moving.
A quick test for choosing the right “A”
A strong ERP Accountable owner can answer “yes” to these:
Authority: I can allocate resources and enforce decisions across functions.
Credibility: Teams trust my judgment enough to change how they work.
Stamina: I’ll stay committed through the messy middle, not just the kickoff.
Tradeoff power: When priorities conflict, I can resolve it quickly.
Outcome ownership: I own business outcomes and adoption, not just “go-live.”
AND, this person's peers confirm the accuracy of the potential ERP Accountable owner's self-assessment. If not, the “A” becomes symbolic, and the project drifts, budgets explode, and failure becomes a more likely outcome.
A practical starting point (30 minutes)
Choose one high-stakes decision this quarter (ERP selection, key hire, capex, pricing change) and do this:
Write the outcome for the decision in one sentence.
Name the A: one person.
Name the R: who are the people that drive weekly progress.
Choose 3–6 C’s: only those who materially improve the decision.
Define the I list: identify who gets the decision and rationale behind it
Add a deadline and escalation rule: Define what happens if alignment stalls.
This is how family enterprises increase decision velocity without sacrificing stewardship.
Closing thought: Digital change won’t slow down. Family enterprises that thrive in this era will be the ones that build a leadership system capable of moving quickly and wisely by aligning across generations while keeping governance guardrails intact. RACI is a simple framework, but in a family enterprise context it becomes a powerful accelerator of clarity, confidence, and control for decisions that stick and drive impact.
For more information or support: Drop us a note.