Introduction

Building Clarity Through Structure

A comprehensive framework for organizational accountability at WKT

This document serves as the working foundation for our accountability chart engagement with Sofia Aziz. It traces a journey from personal reflection through strategic design to detailed implementation.

Purpose: To create a sustainable organizational structure that honors the different kinds of work we do, reduces friction, and enables each part of WKT to optimize for what it does best.

Workshop Status

Foundation

✓ Complete

Strategic reflection captured

Blueprint

✓ Complete

Four-engine model defined

Publishing

⚡ Workshopping

In discussion, not approved

Institutional

⏳ Upcoming

To be developed

Enterprise

⏳ Upcoming

To be developed

Labs

⏳ Upcoming

To be developed

How to Use This Document

For Different Audiences

  • For Sofia: Read sequentially from Reflection → Blueprint → Publishing to understand the conceptual foundation before facilitating discussions on the remaining engines
  • For Leadership Team: Use as reference during workshops to ground decisions in the original strategic insights
  • For Glenn (Integrator): Reference decision rules and boundary definitions when arbitrating cross-engine issues
  • For Future Hiring: Engine-specific sections provide leadership profiles and role clarity

The Journey Ahead

We're building this deliberately, one engine at a time. Each section will be developed through collaborative discussion with Sofia, ensuring the structure reflects both strategic intent and operational reality.

Part One

A Reflection on Leadership and Clarity

December 2025 — Chris LaBossiere

"We may no longer be running a single kind of business — even if we still talk about it as one."

Why This Document Exists

Over the past year, running the business has felt heavier than it should. We have capable people, real customers, and products that matter. Yet, the day-to-day experience of leading has become more taxing and diffuse.

The problem isn't effort or execution — it's classification. We've been treating fundamentally different kinds of work as if they could be governed by a single operating logic.

The Question That Changed Everything

"What kind of work is this, really?"

This question revealed four distinct patterns in how decisions behaved:

The Four Contexts

Context One

Competing Where Customers Have Choice

Governs how we compete in open markets with alternatives, price fluidity, and customer optionality.

Optimizes for: Speed, efficiency, commercial judgment, portfolio management

"Should we compete here — and if so, how do we win efficiently?"
Context Two

Running Trusted Programs

Governs work where we hold delegated authority in regulated or high-stakes environments.

Optimizes for: Consistency, defensibility, relationship stewardship, compliance

"Can we run this safely, consistently, and in a way that holds up over time?"
Context Three

Building Future Capabilities

Governs pre-commercial work before proof, demand, or organizational comfort exists.

Optimizes for: Future leverage, exploration, learning cycles, optionality creation

"Would owning this capability meaningfully change our position?"
Context Four

Stabilizing the Enterprise

Governs systems that ensure the business functions consistently under pressure.

Optimizes for: Reliability, risk reduction, variance minimization, dependability

"Can the business rely on this without escalation?"

Why Tension Is Not the Enemy

Each context optimizes for something different. These priorities are not meant to align perfectly. The error isn't tension itself — it's seeing tension as a problem to eliminate rather than a reality to govern.

Productive Tension Destructive Tension
Visible, named, bounded — shows clear disagreements about trade-offs Ambiguous, personal, escalates unnecessarily — drains energy
Resolved by applying the right rules to the right work No one knows whose authority applies or when to escalate

The Integrator's Role: Classification

The Integrator's job is not to harmonize every disagreement, but to classify by asking:

  • What kind of work is this?
  • Which context governs it?
  • Are we applying the right rules?

Answering these questions resolves many conflicts. Others escalate — but for the right reasons.

What This Means for Structure

Accountability follows context, not titles. Each of the four contexts requires:

  1. A single accountable leader
  2. Clear authority within that context
  3. Explicit boundaries around that authority

The Visionary focuses on direction, narrative, and long-term positioning. The Integrator ensures the contexts interact cleanly, enforces boundaries, and arbitrates tradeoffs that span contexts.

The Test of Whether This Is Working

This model is working if:

  • Fewer decisions escalate unnecessarily
  • Leaders are confident saying "no" within their domain
  • Tension is discussed openly and resolved faster
  • Leadership energy shifts from reconciliation to progress
Part Two

Organizational Blueprint

Translating Reflection into Structure — February 2026

The four contexts become four operational engines. WKT is the company brand across all four.
Division What It Does Maps to Context
WKT Publishing Commercialize and distribute WKT's own published training content Competing where customers have choice
WKT Institutional Manage trusted training programs for government and association partners Running trusted programs
WKT Labs Build future capabilities and new SKUs before commercialization Building future capabilities
WKT Enterprise Shared services that keep the enterprise running Stabilizing the enterprise

The Accountability Chart

VISIONARY

Chris LaBossiere

Direction, long-term positioning, R&D oversight, Oliu™

INTEGRATOR

Glenn Bosch

Cross-engine arbitration, operating rhythm, EOS accountability

PUBLISHING

GM Publishing

  • Retail storefronts
  • SCORM / B2B
  • Channel partners

INSTITUTIONAL

GM Institutional

  • RSBC, go2HR
  • AHEIA, Alberta DL
  • AGCO programs

LABS

Head of R&D

  • New SKUs
  • ALF next-gen
  • Oliu™ spinout

ENTERPRISE

COO

  • Platform & Product
  • Finance, HR, Legal
  • Infrastructure

Key Structural Insights

1. Lanes, Not Divisions

Publishing opens new "lanes" (vertical markets like Danatec, BCC, RELO) without adding business units. When Labs ships a new SKU, Publishing opens a new lane and applies the same playbook.

2. Each Engine Requires a Different Leader

This is not about talent — it's about fit. The right person in the wrong context creates exactly the friction we identified in the Reflection.

3. Platform Governance

RapidLMS and ALF serve both Publishing and Institutional. Changes require impact assessment on both engines. Neither can unilaterally push platform changes. Labs experiments happen on isolated environments.

Decision Rules

If the decision is about... Who decides
Selling content, marketing, B2B licensing, channel partners Publishing GM
Delivering a managed program under contract Institutional GM
Building future capabilities, new SKUs Labs (Visionary has veto)
Enterprise stability, infrastructure, compliance Enterprise COO
Crosses engine boundaries Integrator arbitrates
Direction, long-term positioning, Oliu™ Visionary

What Comes Next

With Sofia's facilitation, we'll now develop the detailed accountability structure for each of the four engines. This work happens collaboratively, ensuring the structure reflects both strategic intent and operational reality.

Publishing is first — currently in workshopping stage (not approved, in discussion).

Part Three — Engine 1 of 4

WKT Publishing

Detailed Structure — Workshopping Stage

⚡ Workshop Status

The content in this section represents initial thinking and proposals — not approved decisions. This is active discussion material for Sofia's facilitation process.

Publishing maps to the first context from our Reflection: Competing where customers have choice.

Core question: "Should we compete here — and if so, how do we win efficiently?"

Detailed Publishing structure, current problems, proposed team composition, and implementation thinking will be developed through collaborative workshop sessions with Sofia and the leadership team.

Working documents and detailed proposals available for review during workshop sessions.

Part Four — Engine 2 of 4

WKT Institutional

To Be Developed with Sofia

Institutional maps to the second context: Running trusted programs.

Core question: "Can we run this safely, consistently, and in a way that holds up over time?"

Structure will be developed through Sofia's facilitation process following completion of Publishing workshop.

Part Five — Engine 3 of 4

WKT Enterprise

To Be Developed with Sofia

Enterprise maps to the fourth context: Stabilizing the enterprise.

Core question: "Can the business rely on this without escalation?"

Structure will be developed through Sofia's facilitation process.

Part Six — Engine 4 of 4

WKT Labs

To Be Developed with Sofia

Labs maps to the third context: Building future capabilities.

Core question: "Would owning this capability meaningfully change our position?"

Structure will be developed through Sofia's facilitation process.

Living Document

This framework evolves as we workshop each engine with Sofia Aziz. Progress is deliberate and collaborative.

Last Updated: March 5, 2026 | Next Session: TBD with Sofia