Business Masteries: Executive Summary for Leaders

1. Engage System™ – Lead Beyond the Project Boundary

What this means: Successful outcomes depend on engaging and influencing the broader System: your organization, partners, IT, customers, and industry context. "A System is any group of interacting, interrelated, or interdependent parts that form a complex and unified whole that has a specific purpose." — Daniel Kim

Key leadership actions:

1. Insist on System-level thinking

• Ask: How does this initiative interact with our strategy, structure, culture, and other initiatives?
• Require stakeholders to identify external constraints, dependencies, and risks, not just internal project tasks.

2. Strengthen business–IT relationships

• Set the expectation that business and IT are joint owners of outcomes, not opposing camps.
• Model behaviors you want: transparency, trust, plain language, and shared accountability.
• Reward cross-functional collaboration, not silo performance.

3. Require disciplined risk, issue, and decision (RID) management

• Make it non-negotiable that every project has clear RID processes.
• Demand early surfacing of bad news and create a no-blame culture so teams feel safe raising reality.
• Ask for periodic, simple health checks focused on: What’s at risk? What’s changed? What decisions are stuck?

4. Mandate effective transitions and handoffs

• Require explicit plans for critical transitions: requirements ➔ design, design ➔ build, build ➔ test, test ➔ operations.
• Ask for clarity on mission, objectives, roles, and dates for each major transition.

5. Enforce clear, candid communication

• Insist on status reports that emphasize exceptions, risks, and decisions — not long lists of green tasks.
• Challenge vague assurances. Ask: What evidence supports this status? What would we see if things were off track?

2. Develop Insight™ – Learn Before You Commit

What this means: Most failures are sociological and organizational, not technical. You can reduce risk by learning from your own and others’ histories before approving or scaling a project.

Key leadership actions:

1. Demand historical insight and external benchmarks

Before greenlighting major initiatives, require:

• Lessons learned from similar internal projects.
• External benchmarks (industry case studies, peers, analysts) on failure modes and leading practices.
• Ask for evidence: Who has solved a similar problem, and what did we learn from them?

2. Right-size the project and approach

• Encourage smaller, staged initiatives over mega-projects.
• Match approach (structured vs. agile) to:
  • Complexity and criticality.
  • Level of uncertainty (facts vs. assumptions).
  • Team competency and culture.
• Use discovery/feasibility projects when assumptions are high and facts are low.

3. Recognize and manage classic failure patterns

Watch for:

• Vague roles and accountability.
• Factless plans and optimistic schedules.
• Large, convoluted scopes.
• Weak sponsorship and unclear outcomes.
• Persistent communication problems and avoidance of reality.

Intervene early when you see these patterns; don’t wait for red status.

4. Design for learning and iteration

Ask teams to:

• Use prototypes and early testing to clarify requirements.
• Move design and testing slices earlier.
• Conduct Before Action Dialogues (what could go wrong, what we’ll do about it) and After Action Dialogues (what worked, what didn’t, what we’ll change).

Consider Historical Laws and Principles

3. Embrace Mission™ – Clarify, Focus, and Protect the Why

What this means: Behavior without a clear purpose creates chaos. Mission is about people, outcomes, and capabilities, not just project checklists.

Key leadership actions:

1. Anchor everything in clear business outcomes

Require every project to answer:

• Why does this capability exist?
• How does it link to our strategy and financials (P&L, balance sheet, cash flow)?
• What specific outcomes and measures define success?
• Use frameworks like SPRONTO™ (Strategy, Process, Relationships, Organization, Network, Technology, Operations) to ensure you’re considering all dimensions.

2. Apply 80/20 thinking relentlessly

• Focus on the vital few capabilities and requirements that enable the business case.
• Challenge scope creep by deferring nonessential features to later releases.
• Ask in every scope discussion: Is this vital to outcomes or just nice-to-have?

3. Ensure rigorous scoping and requirements

• Do not approve "we’ll figure it out in design" plans.
• Require:
  • Tested, traceable requirements linked to the business case.
  • Early test and deployment planning.
• Make it clear that late changes to requirements will be treated as reinvestment decisions with visible cost and schedule impacts.

4. Demand robust business cases and value tracking

• Insist on a business case that includes:
  • Benefits (quantitative and qualitative).
  • Total cost of ownership (project + ongoing operations).
• Require periodic updates to the business case and post-implementation benefit tracking.

5. Staff and organize for success

• Use RACI and clear role definitions for sponsors, owners, project managers, and key SMEs.
• Never start a significant project without:
  • An engaged, empowered sponsor.
  • Defined governance (steering committee or equivalent).
• Align skills to business need — don’t staff critical work only with whoever is available.

4. Optimize Decisions™ – Be a Disciplined Buyer and Partner

What this means: Vendor and solution decisions must be based on knowledge, not just on numbers or marketing. The goal is to choose the right partner, not just the right product.

Key leadership actions:

1. Set clear goals for buy vs. build

Favor buying when:

• The capability is not a key differentiator.
• Proven solutions exist.
• Long-term support and innovation matter more than bespoke features.

Reserve a custom build for truly differentiating capabilities where market solutions fall short.

2. Insist on a structured, transparent evaluation process

Require:

• Clear guiding principles and minimum vendor requirements.
• An agreed scoring model (factors, weights, rating scales) before vendor engagement.
• A small, skilled cross-functional evaluation team.
• Make bias mitigation explicit; don’t allow decisions on anecdotes alone.

3. Limit traditional RFPs; favor dialogue-rich approaches

• Use RFPs only when required (e.g., public sector) or for very high-risk decisions.
• Prefer partnering and JITDE™ (Just-in-Time Decision Evaluation):
  • Research and shortlist ~3 viable vendors.
  • Run intensive, interactive sessions with demos, sandbox use, and contract discussions in parallel.

4. Look beyond features to long-term fit

Evaluate vendors on:

• Financial viability and roadmap.
• Services, education, and support.
• Security, architecture, and alignment with your standards.
• Cultural fit and partnership mindset.
• Ask for and follow up with customer references beyond those provided by the vendor.

5. Negotiate with a total-value mindset

• Engage experienced procurement and legal counsel (especially for major ERP/cloud deals).
• Negotiate on three fronts:
  • Vendor performance and SLAs.
  • Solution capabilities and configuration boundaries.
  • Economics (licenses, recurring fees, exit costs, contingencies).
• Insist that commitments critical to success are in writing — assumptions and verbal assurances don’t count.

5. Think Capability™ – Drive Adoption and Long-Term Return

What this means: Projects are only vehicles; the real value comes from capabilities that are adopted, sustained, and extended over time.

Key leadership actions:

1. Judge success on capabilities and outcomes, not go-live dates

Define success as:

• Capabilities in place.
• Adoption by users.
• Measurable business impact.

Expect a post-implementation plan for:

• Job aids and training.
• Support, continuous improvement, and incremental releases.

2. Plan for phased delivery and ongoing extension

Encourage:

• Delivering the vital few requirements first.
• Using real-world usage and feedback to refine and expand.
• Support agile pivoting and improvisation when business or market conditions change.

3. Integrate structured and agile methods

Ask teams to combine:

• The discipline and predictability of structured approaches (trains).
• The speed and adaptability of agile approaches (jet engines).
• Focus on cycles (Decide–Design–Develop–Deploy), channels (business, organization, technical), and controls (project management).

4. Model the behaviors you expect

Demonstrate:

• Willingness to say "no" or "not now" to nonvital scope.
• Openness to bad news and rapid course correction.
• Commitment to learning, reflection, and continuous improvement.

Leader’s Short Checklist

When you next review, sponsor, or approve a major initiative, ask:

1. System & Relationships
   • Have we mapped the broader System and key relationships (business–IT, vendors, other initiatives)?
   • Are roles, governance, and RID processes clear?
2. Insight & History
   • What have we learned from similar internal and external efforts?
   • Are the scope, approach, and size appropriate to our uncertainty and capability?
3. Mission & Outcomes
   • Are outcomes clearly defined, measurable, and linked to strategy and financials?
   • Have we applied 80/20 thinking to requirements and scope?
4. Decisions & Vendors
   • Do we have a transparent, pre-agreed evaluation and scoring approach?
   • Are we choosing a long-term partner, not just a product?
5. Capabilities & Adoption
   • How will we ensure adoption, support, and continuous improvement post go-live?
   • How and when will we measure realized value versus the original business case?

Leaders who consistently apply these actions dramatically increase the odds that technology investments translate into sustained business performance and value.