/skills · Applied enablement

Capability,
not dependency.

Applied enablement taught by people who build, fail, and scale products themselves. Not slide-deck workshops — a mindset shift backed by hands-on practice, so your team can own, evolve, and scale what we leave behind.

prodct/units/skills.config
1// unit.config 2unit: "/skills" 3focus="applied enablement" 4for=Leadership · L&D · Product & Team leads 5taught_by=practitioners, not trainers 6formats=1:1 advisory · workshops · 9–18mo programs 7tracks=AI literacy · delivery mindset · tech eval 8outcome=teams that don’t need us next time
// the problem

Workshops end on Friday. Monday, nothing changed.

You've paid for AI training, agile transformations, and innovation workshops. Everyone nodded. The slides were good. And then on Monday the team went back to the same processes, the same decisions, and the same vendors — because nobody changed how they work.

Knowledge transfer only sticks when it's applied to real work under guidance, with feedback loops long enough to form habits. That's what /skills is — not a course, but an embedded practice that teaches your people to do the thing while they do it, until they don't need us.

// formats

Three ways to work with us.

Match the format to the ambition. All three use the same underlying approach — practitioners teaching while work happens.

01 · ADVISORY 1-on-1 advisory for leaders.
monthly cadence3–12 months

A senior sparring partner for a CTO, CPO, or product lead. We work on your actual roadmap, actual hires, actual vendor decisions — not hypotheticals.

// for: C-suite, heads of product & tech
02 · WORKSHOPS Hands-on workshops, built on your cases.
2–5 days8–20 people

No generic curriculum. We study your real projects, then teach the team by re-running them — with us in the room to coach the decisions.

// for: product, tech, data & marketing teams
03 · PROGRAM 9–18 month coaching programs.
embeddedmeasurable

We pair with your team on real delivery for a full product cycle — kickoff to KPI. By month 12 they're shipping without us. That's the point.

// for: org transformation, new capabilities
// program arc

Five stages. Each one hands off more.

The whole arc is designed to transfer ownership. We're most present at the start, least present at the end — by design.

01BaselineHonest diagnosis: where the team is, where the gaps are, what good looks like.
02Co-buildWe pair on real work. Pair-programming, pair-designing, pair-deciding.
03CoachThey lead. We review. Feedback tightens as confidence builds.
04ObserveThey ship. We watch. Quiet office hours, escalation only if needed.
05HandoffRunbooks, hiring rubrics, onwards roadmap. We're unnecessary.
// tracks

What we actually teach.

01AI literacy for leadership — what LLMs are, what they aren't, where they belong in your stack.
02Applied AI enablement — teams using GPT / Claude / agents inside their real workflows, safely.
03Delivery-driven mindset — how to scope, estimate, and ship in weeks instead of quarters.
04Technology evaluation frameworks — how to pick vendors, platforms, and architectures without consultants selling the answer.
05Product discovery — interviewing customers, framing bets, killing ideas fast, writing honest business cases.
06Engineering leadership — hiring, reviewing, setting the bar for technical decisions and code quality.
// how we teach

Four principles we never break.

Every format, every track, every coaching session runs against these.

Taught by practitioners.

Our coaches are still building, shipping, and failing on real work. Nobody on /skills has "left the field" — because the second you do, the advice rots.

Applied to your real cases.

We don't rent a hotel conference room and teach generic slides. We study your roadmap, your codebase, your team — and teach against it. The homework is your next sprint.

Designed to end.

The best outcome is that you don't need us next year. Every engagement has a planned handoff. If we're still indispensable at month 18, we failed.

Measured in behavior, not satisfaction.

We don't care if the workshop got 5 stars. We care whether the team ships differently six months later. That's the only metric that matters.

// when clients call us

Typical situations.

01"We've done AI workshops. Nothing shipped. We need it to actually land."→ applied AI
02"Our CTO is new. She needs a sparring partner who's done this before."→ advisory
03"We want to stop depending on agencies — but our team has never shipped product."→ 12mo program
04"We keep buying the wrong platforms. We need to evaluate them ourselves."→ tech eval
05"We want an in-house product culture, not another framework rollout."→ embed
// why prodct /skills

We're the consultancy trying to make itself redundant.

Most training firms sell you more training. We sell you less — because the quieter our calendar gets with you, the better we did our job. The success metric isn't a renewed contract; it's a team that walks into year two confident they don't need us anymore.

We can afford this because the other three units keep us sharp. /skills isn't a training brochure written by people who left the field a decade ago — it's a side of the business taught by the same people who, next week, are shipping an e-commerce migration or an AI agent in production.

// /skills

Want your team to own it next time? Let's scope it.

EN DE