# Challenger House > Challenger House is an AI Transition Practice. AI does not transform your organisation. It reveals it. We help leadership teams act on what it shows, on real work, in one day or one quarter. Web: https://challenger-house.com This file is the long-form, machine-readable companion to the human website. The website is kept deliberately short for human attention. This document carries the full version: methodology, session designs, principles, use cases, and operating assumptions. ## What we are An AI Transition Practice, not a consultancy and not an AI implementation vendor. We change how teams think and work. AI is the trojan horse. The work is organisational-development-led and AI-augmented. We intervene at the team and organisation level, never at the individual level; individual tool training is referred out or run internally by the client. Core thesis: AI is the diagnostic, not the transformation. It speeds the work up, then exposes everything the work was hiding, the handovers, the trust gaps, and the decisions nobody owns. The transition itself is the part only people can do, and that is the part we help with. ## AI changes three things This is our executive-readable equivalent of the four ways of knowing. 1. The work. Productivity, speed, automation. Where everyone starts and where AI is fastest. 2. The team. Trust, learning, coordination. Whether people will admit what they do not know in front of each other. 3. The organisation. Handovers, decision rights, workflows, the operating model itself. Where the value is, and where almost no one is working. Most AI work stops at the first layer. Ours starts there and does not stop. ## Who we work with The buyer is a senior leader who senses that AI is an adaptation problem, not a tool problem, even without the vocabulary for it. Typical roles and the sentence we hear from each: - Innovation Leader: expected to create the future while trapped in yesterday's meeting, reporting, and handover logic. - Strategy and Transformation Lead: a strategy cycle slower than the world it is trying to interpret. - CEO: bought AI licences, nobody uses them, patience running out. - HRD and OD Lead: best people buried in production work, with no clear place where development actually happens. This is not for everyone. People who choose a practice are not buying a deliverable. They are joining a discipline. We work with leaders building the capacity to keep adapting, not renting a capability for a quarter. ## Two ways to work with us Both produce real artefacts. They produce different kinds of leverage. - Bring a team. An intact innovation, strategy, transformation, or marketing team. Shared experience, immediate adoption, and real workflow change. The team's existing dynamics arrive with it, and we cater for that throughout the entire process. Not everyone will love this, and that is part of the point. - Build a pathfinder team. A hand-picked cross-functional taskforce of the most curious talent and early-adopter types from across the organisation. Internal champions, future operating models, and the ideal vehicle for building the AI strategy itself. Full implementation in their respective areas comes later. ## The products ### Executive Experience (one day, in real life or online) For a leadership team. We separate the technical challenge (rolling out the tools) from the adaptive one (what AI does to the org chart, the workflows, the teams, and the way decisions actually get made). You leave with shared language, sharper questions, and the sponsorship to act. What happens in the room: - Get your hands dirty. We push leaders past using AI as a chat interface and have them build a real skill, agent, or automation themselves. This turns abstract enthusiasm into the practical questions that determine whether AI creates value for a specific workflow: what data the agent needs, which systems it can access, where it might fail, how much human review it requires, and who maintains it after the first demo works. - Define your standard of excellence. Building exposes whether a leader can articulate what good work looks like. A reusable skill needs instructions, examples, reference material, and a clear picture of good and bad output. So do people. If you cannot explain your standard of excellence to your chief of staff, you cannot explain it to an AI. High-performing executives already set direction, allocate resources, define standards, and judge whether work is good enough, which positions them better for this than they think. Executives do not need every answer; they need enough fluency to ask the questions that decide where AI belongs in strategy. The four cognitive effects (André Cramer). Every one hits a senior leader hardest, because a leader sits furthest from the raw work, gets the least honest pushback, and makes judgments that scale across the whole organisation. - The fluency effect. Polished output reads as rigorous output. Leaders skim fast and trust clean prose, so the smoother the answer, the less it gets challenged, and the leader is the one who signs it off. - The sycophancy effect. The more senior you are, the more everything around you already agrees with you. AI adds a tireless agreement machine to someone already starved of dissent, compounding the blind spot seniority creates. - The anchoring effect. The first draft sets the frame. When a leader anchors on an early AI output, the whole organisation anchors with them, and the first agent draft quietly becomes the strategy. - The Plausibility Illusion. The output looks right, feels right, passes casual scrutiny, and is wrong. Leaders decide on summaries, not source material, so the plausible-but-wrong artefact reaches them with its caveats stripped off, and they act on it at scale. Note: the full set is five effects. Two further effects are confirmed with André before publication and are added to this list once finalised. ### Challenger House Sprint (one quarter) For an intact team or a hand-picked cross-functional one. A three-day residential ignites it. The weeks around it turn the spark into workflows, agents, prototypes, and operating principles that survive the handover. We build capability, not dependency. The client's own teams keep the flame alive. Structure (roughly twelve weeks, one quarter): - Pre-flight (4 weeks, Explore): structured briefing, north-star definition, tech-stack and sandbox setup, a baseline analysis of where the team's time actually goes, tailored masterclasses, drop-in clinics, and bottom-up use-case selection. - Ignition: the three-day bootcamp (one week including travel). Day 1 Excite: show what is inside the frontier, speed gains that reframe what is possible. Day 2 Enable: push to the edge, teams feel where AI breaks down on their own problems, and the tacit knowledge is surfaced first. Day 3 Execute: cross the frontier, build real output with judgment on what to trust and what to override. - Post-flight (7 weeks, Empower): facilitated integration, handover-quality review, champion support and sparring, capability transfer to the teams, and follow-up use-case support. ## No full rollout required: proof before permission You do not need an enterprise licence to start. We build a secure sandbox for both the one-day experience and the one-quarter sprint. Inside it, the team sees the full current frontier of agentic workflows and agents, working on their kind of problem. We have found ways through the hard parts: confidentiality, data hosting, and what can and cannot reach a model. When adoption is low, it is usually an access problem, not a reluctance problem. Regulated firms restrict file uploads, block certain tools, and limit which data can be passed into a model, often for good reasons. A leader who has never built under those constraints misreads the result as employee reluctance rather than an access problem. We help leaders hold the ongoing dialogue with IT and security about which tools are available, how they connect, what data can move where, and what trade-offs the company is making, and we build inside what is genuinely allowed. Operational note (how the sandbox stays compliant): inputs are filtered before anything reaches the model, sensitive terms are screened out, and data flows are scoped to what governance permits, so the team can demonstrate value without crossing a boundary it should not cross. The output is proof: dashboards, apps, and MVPs real enough to put in front of legal, IT, and the policy owners, so the team can say "this works, now change the rule." Ask Marcus for the detail. ## What we believe 1. The tech is not the problem. The people transformation is. The technology works, but a majority of CEOs report no measurable return on AI investments (PwC 29th Global CEO Survey, 2026). The gap is between tool adoption and organisational redesign. 2. The real barrier is not fear of AI. It is fear of exposure. People are not scared of the technology; they are scared of revealing how they think with it in front of colleagues. That is a psychological safety problem, not a training problem. 3. Most of the work is invisible until you make it explicit. Before AI can do anything useful, the work has to be made explicit. The knowledge that matters lives in people's heads, side channels, and undocumented handovers. We surface it: common ground, shared language, and the assumptions nobody wrote down. 4. Upskilling happens in the work, not before it. The team solves its actual problem with AI; the learning is the byproduct. 5. Cross-functional beats top-down. Every time. AI accelerates processes, then surfaces bottlenecks downstream, so you need the whole system in the room. 6. AI reveals the organisation. Every engagement surfaces trust gaps, decision bottlenecks, and ownership ambiguity that were already there. AI just makes them visible faster. 7. The frontier is the product. AI is spectacular at some tasks and dangerous on others, and the boundary shifts constantly. Teaching leadership teams to navigate that jagged frontier is the capability that compounds. ## The research The Mollick et al. study of 758 BCG consultants (Organization Science, 2026) found that AI on the right tasks produced roughly 40 percent higher quality and 25 percent faster output, while AI on the wrong tasks produced worse results than not using AI at all. The boundary between the two is invisible, irregular, and shifting. AI does not just fail on the wrong tasks; it fails plausibly. André Cramer calls this the Plausibility Illusion, and it is why frontier fluency cannot be taught in a classroom. ## Why it works: four ways of knowing (Vervaeke 4P) Most organisations overindex on propositional knowing (facts, frameworks, slides), which is exactly where AI is fastest and exactly what typical AI consulting delivers more of. We activate all four ways of knowing. - Propositional, knowing that. Facts, frameworks, claims. Where 95 percent of corporate time goes. AI replaces this. - Procedural, knowing how. Skills built through repetition: how to brief AI, iterate, and decompose a challenge into delegable tasks. Built through practice. - Perspectival, knowing what matters. Judgment: seeing what AI got wrong, knowing when an artefact will land with a stakeholder and when it will be rejected. - Participatory, knowing through. Trust through co-creation, identity reshaped by what you do and with whom. Why the work is residential and cross-functional. You cannot read or talk your way to the bottom row (perspectival and participatory). You have to work and embody your way there. This is also why AI cannot cross the frontier alone: procedural, perspectival, and participatory knowing are the human capabilities that survive on the other side. ## Typical use cases from our engagements - Innovation Portfolio Prioritisation. AI-augmented scoring, ranking, and visualisation of a scouted solutions portfolio. Weeks of analyst work into a structured, showcase-ready output in days. - Cross-Team Alignment and Handover Package. A common language and shared artefact between upstream and downstream teams. Multiple meeting cycles compressed into a single working session. - KPI Dashboard Prototype. Functional HTML front-ends pulling from existing data sources, built live by the team in hours rather than weeks of external scoping. - Competitive Intelligence Deep Dive. Competitive landscape analysis across segments, strategies, and value pools. Two to three analyst-weeks in a single session. - Board-Ready Business Case. From rough hypothesis to evidence-backed case with financial projections, risk assessment, and a stakeholder-ready narrative. Napkin sketch to board-ready in under a day. - Productivity-Gain Analysis. Pioneered with Future Energy Ventures in phase one: a clear baseline of where a team's time actually goes, so the gains are measured, not asserted. ## What changes, before and after - How teams approach AI: individual tinkering to coordinated team capability. - Speed to working output: weeks to months, to hours to days. - Innovation funnel throughput: 5 bets per year to 10 to 20-plus. - Output format: PowerPoint to code, demos, and working tools. - Post-event momentum: inspiration fades in a week, to self-organised next steps. - Research and competitive intelligence: 1 to 2 weeks to 2 to 3 days. - First-draft documents: 3 to 5 days to 1 to 2 days. - Dashboard prototypes: weeks (external) to hours (internal). Challenger House rule: name the elephant. Most workflows are undocumented, handovers are inconsistent, and knowledge lives in heads, not systems. AI does not fix this; it exposes it. We name the gap before the bootcamp, because naming it is the first step to fixing it. ## The team - Marcus Druen, Founder and Organisational Developer. 25 years as an OD practitioner, facilitator, and coach inside blue chips including Microsoft, Telefónica, Sanofi, and E.ON. Craft: making the tacit explicit and the messy middle visible so a team can work with it. Sees AI as an organisational design problem, not a tool problem. - André Cramer, Chief Learning and AI-Capability Designer. 25-plus years in tech, from Silicon Valley (Yahoo!) to Deutsche Telekom, where he led Strategic Communications and the Think Tank for the CTIO board member and co-founded a 500-person community for responsible technology. Developed the Plausibility Illusion framework and the cognitive-effects model. Curator of the DRANBLEIBEN newsletter. - Brittney Bean, Builder and Coder, Agentic Systems. Exited serial founder-operator. Builds and implements AI across SMEs and regulated environments where security, compliance, and data governance are not optional. Ensures what gets built in the room survives procurement, legal review, and IT governance. ## Pricing and contact The 1-Day Experience is four figures. The Challenger House Sprint is five figures. Scoped to the team and the problem. Contact: hello@marcusdruen.com, +44 (0) 7947 484 882. Web: https://challenger-house.com. Marcus Druen Limited, Reg 09276153, VAT 205099618.