Flexible curriculum Live practice Real artifacts Mechanisms that scale

Start with the thing that is actually limiting the team.

The best sessions start by naming the real constraint. Sometimes that is leadership cadence. Sometimes it is hiring, product judgment, execution discipline, conflict, or AI behavior. I flex the material around the problem, the audience, and the artifacts the team already uses.

Capability compounds when people practice on real work, with dates, owners, mechanisms, and feedback.

Kindel Leadership Development

You are behind in AI. Catch up.

AI adoption usually fails because teams wait too long to touch real work.

01

Locate the team

Diagnose whether the team is avoiding, curious, committed, compounded, or AI native.

02

Practice safely

Use AI internally where learning is high and the blast radius is low.

03

Prototype on real work

Run weekly demos against real constraints, not one-off theater for leadership.

04

Bring oversight early

Put legal, security, compliance, and risk at the whiteboard before the demo.

05

Hire the wedge

Build the small team that can rewire the org: forward deployed, applied research, platform, and product muscle.

06

Run the 90 days

Pick the fight worth winning, ship the first workflow, measure adoption, and set the flywheel.

Operational, engineering, and product management excellence together.

Strong product development is not just PM craft. It connects customer truth, technical quality, execution, and product decisions that can survive contact with reality.

Customer

Customer truth

Find the pain customers would protest losing a solution for, then make that truth hard for the org to ignore.

Narrative

Written clarity

Use narratives, tenets, and crisp metrics to make product thinking inspectable.

Engineering

Quality and tradeoffs

Build a shared language for architecture, quality, speed, risk, and technical bets.

Operations

Cadence and accountability

Turn product intent into mechanisms, dates, paths to green, and decision records.

Build the operating system for people and execution.

Leaders

Leader of leaders

Design the cadence, mechanisms, and principles that let leaders lead without you in every room.

Managers

People management as a profession

Practice relationships, trust, conflict, commitment, accountability, and results through others.

Builders

Influence without authority

Lead through facts, trust, vision, coalitions, strong questions, and plans people can own.

Org OS

Mechanisms that scale

Install planning, reviews, knowledge, interfaces, taxonomy, principles, and fitness functions.

Hiring excellence is a leadership mechanism.

Better hiring is not luck. It is a path leaders of leaders can teach: plan the work, run an evidence-based operating system, then land the hire through onboarding and ramp. More chapters will land here as the curriculum grows.

01 · Plan

Have a Plan (the 5Ps)

Purpose, Principles, Priorities, People, Plan. Hiring that depends on unnamed headcount is a fake plan. Leaders learn to inspect any plan (including recruiting, offer, and ramp) and see which P is missing before reality does.

02 · Run

The Hiring Operating System

Bias is the default; interviewer confidence is not evidence. Define role outcomes, map evidence to interviewers, collect independent signal, write feedback, and debrief from observations. Capability and behavior both count; yellow flags become investigations.

03 · Land

From Job Description to 30/60/90

Start with 12-month success, replace years-of-experience with repeated demonstration, name tradeoffs, design the loop, close honestly, and onboard before day one. At 90 days, inspect the original packet so the system gets less wrong over time.

Leaders practice defining roles in outcomes, mapping interviewers to signal, debriefing from evidence, and closing the loop with a real 30/60/90. For related writing, see excellent hiring and the Leader of Leaders handbook.

Start in office hours. We will figure out the right session from there.

Book free office hours