Overview

WKT Accountability Framework

A living document tracing WKT's organizational evolution from strategic insight through structural design to detailed implementation.

Workshop Progress — Sofia Aziz Engagement

Foundation

✓ Complete

Blueprint

✓ Complete

Publishing

✓ Complete

Institutional

⏳ In Progress

Enterprise

⏳ In Progress

Labs

⏳ In Progress

Purpose & Structure

This master document serves as the foundation for Sofia Aziz's EOS accountability chart engagement. It traces three stages of organizational evolution:

Stage Document Section What It Provides Status
Why A Reflection on Leadership and Clarity Conceptual framework — four contexts, structural tension ✓ Complete
What Organizational Blueprint Four engines, decision rules, leadership profiles ✓ Complete
How Detailed Engine Structures Accountability charts, roles, implementation plans ⏳ 1 of 4 complete

How to Use This Document

  • For Sofia: Read sections sequentially to understand the conceptual foundation before building the remaining engines
  • For Leadership: Reference as the single source of truth for organizational structure and decision authority
  • For Hiring: Use engine-specific sections for role definitions and leadership profiles
  • As Living Document: Will be updated as Institutional, Enterprise, and Labs structures are completed
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 Matters

Over the past year, running WKT 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 our decisions behaved, independent of teams or titles. Each pattern represented a unique way of creating value, managing risk, and exercising judgment.

The Four Contexts

Context 1

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 2

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 3

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 4

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. Organizations don't eliminate these forces — they govern their interaction.

Productive Tension Destructive Tension
Visible, named, and bounded — shows clear disagreements about trade-offs, resolved by applying the right rules to the right work Ambiguous, personal, escalates unnecessarily — 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 and long-term positioning. The Integrator ensures contexts interact cleanly, enforces boundaries, and arbitrates tradeoffs that span contexts.

Part Two

Organizational Blueprint

Four Engines, Four Realities — February 2026

The four contexts become four operational engines. WKT is the company brand across all four.
Division Context Purpose
WKT Publishing Sell Commercialize and distribute WKT's own published training content
WKT Institutional Operate Manage trusted training programs for government and association partners
WKT Enterprise Support Shared services that keep the enterprise running
WKT Labs Invent Build future capabilities and new SKUs before commercialization

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

Sell Context

  • Retail storefronts
  • SCORM / B2B
  • Channel partners

INSTITUTIONAL

Operate Context

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

ENTERPRISE

Support Context

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

LABS

Invent Context

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

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 box creates the exact friction we identified in the Reflection.

Decision Rules

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

WKT Publishing

Detailed Structure — The "Sell" Context

From the Reflection: "Sell governs how the company competes in open markets — environments with customer choice, alternatives, and price fluidity. Should we compete here — and if so, how do we win efficiently?"

Current State: The Problem

$12.16M
2025 Revenue
2.24
Blended ROAS
$1.19M
Ad Spend (2025)
$170K
Danatec Overspend

What's Broken

  • No allocation discipline: SKUs spending 50-243% of revenue on ads
  • No testing framework: Campaigns running without structured experimentation
  • Structural inefficiencies: 80% Search Lost Impression Share, junk conversion signals
  • Owned channels dormant: 250K RAPID database records generating ~0% of revenue
  • One person doing three jobs: Trying to be strategist, executor, and systems builder simultaneously

Root cause: We asked one person to manage $1.2M+ ad spend across 8 SKUs without the strategic framework, execution discipline, or automation infrastructure to succeed.

Proposed Accountability Chart

GM, WKT PUBLISHING

Portfolio Leadership

P&L ownership • Capital allocation • SKU investment decisions • Revenue accountability

GROWTH MARKETING

Head of Growth Marketing

  • SKU/lane strategy (8 brands)
  • Testing roadmap & messaging
  • Channel mix optimization
  • Launches (CIRO, LLQP)

REVENUE

B2B & Channel Sales

  • Inside Sales — SCORM (2)
  • Channel Partner Mgr (1)
  • AI-assisted qualification

↳ PAID MEDIA

Performance Marketing Mgr

  • Daily ad management
  • Campaign optimization
  • Budget pacing (<5% variance)

↳ SYSTEMS & AI

Marketing Ops & AI

  • Dashboards & analytics
  • RAPID activation
  • AI execution layer

MARKETING SERVICES

Marketing Manager

95% Publishing, supports Institutional

  • Campaign creative & brand work
  • Content & Production team
  • Front-End Dev & Web

The Solution: Three Functions, Not One

The current role is actually three distinct functions:

  • Strategy & Portfolio Management → Head of Growth (commercial judgment)
  • Paid Media Execution → Performance Manager (in-platform mastery)
  • Systems & Automation → Marketing Ops (data, AI, infrastructure)

Full implementation details, AI layer, budget comparisons, and timeline available in working documents.

Part Four — Engine 2 of 4

WKT Institutional

The "Operate" Context — In Progress with Sofia Aziz

🚧 Workshop in Progress

This section will be developed during Sofia's accountability chart engagement.

Expected completion: Q2 2026

Preview: Institutional Structure

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

  • GM, WKT Institutional (leadership profile: trust stewardship)
  • Partner Success (relationship management for RSBC, go2HR, AHEIA)
  • Business Development (government RFP, long-cycle sales)
  • Program Operations (compliance, SLA monitoring)
Part Five — Engine 3 of 4

WKT Enterprise

The "Support" Context — In Progress with Sofia Aziz

🚧 Workshop in Progress

This section will be developed during Sofia's accountability chart engagement.

Expected completion: Q2 2026

Preview: Enterprise Structure

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

  • COO/Integrator
  • Finance & Accounting
  • HR & People
  • Platform/Product Team (RapidLMS, ALF, infrastructure)
Part Six — Engine 4 of 4

WKT Labs

The "Invent" Context — In Progress with Sofia Aziz

🚧 Workshop in Progress

This section will be developed during Sofia's accountability chart engagement.

Expected completion: Q2 2026

Preview: Labs Structure

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

  • Head of R&D / CTO (reports to Visionary, not Integrator)
  • Developers (project-based)
  • AI/Data Specialist (ontologies, adaptive models)
  • Product Designer (UX for new capabilities)

Living Document Status

This master document will be updated as Sofia Aziz leads the accountability chart workshop for the remaining three engines.

Last Updated: March 4, 2026 | Next Update: As each engine structure is completed with Sofia