Obsolescence is a choice. Make it consciously.
A working session for senior leaders who'd rather confront what AI is making obsolete in a room with their own team — than find out from a competitor, a board member, or a customer who already has.
Most leaders are treating AI as an upgrade. It isn't. It's a reset of what the business sells, how it delivers, and who does the work. The leaders who recognize this are making deliberate decisions about what to defend, what to retire, and what to rebuild. The leaders who don't are making those same decisions by default — they just aren't the ones making them.
OBSOLESCENCE is a working session for senior leaders who would rather confront that honestly, in a room, with their own team, than find out from a competitor, a board member, or a customer who already has.
This is a leadership workshop about what AI is forcing leaders to decide. The frameworks are tool-neutral. The facilitation is operator-led. The conversation is the one most leadership teams have been avoiding.
OBSOLESCENCE runs a deliberate arc. Each act has a purpose. Each act ends with something written down. The structure is consistent across every tier — what changes is intensity, not sequence.
These are not session topics. They're the lenses the workshop uses to examine the business. No engagement touches all eight — the facilitator selects the three or four most relevant to the client's actual situation, identified in a pre-engagement working session with the sponsor.
Each lens is applied to the client's actual business, not presented as content. The frameworks are in service of the client's decisions, not the other way around.
This work is often mistaken for an AI briefing, a strategy offsite, or a leadership development event. It's none of those things. The distinction matters because it shapes who should be in the room — and what they should expect when they get there.
OBSOLESCENCE scales to the audience without losing its structure. Executive teams get depth and confidentiality. Leadership groups get working time and structured disagreement. Organizations get cascade and shared language. The framework is consistent; the intensity is not.
Every tier shares the Confront / Choose / Commit spine. What scales is intensity, audience, and artifact depth — not structure.
There's no shortage of events and sessions promising to help leaders navigate AI. Most are built around inspiration, vendor content, or generic frameworks applied to hypothetical companies. OBSOLESCENCE is built around the opposite.
There are five paths leadership teams typically take when AI is forcing the question. Most of them produce reports. This one produces signed commitments. Below is what each path actually delivers, side by side.
|
OBSOLESCENCE Working Session
|
Consultant-led strategy projects
Big 4 and Tier 1 "AI strategy" engagements
|
Vendor-led sessions
AI platform vendors
|
Innovation accelerators or labs
|
Internal executive offsites
|
|
|---|---|---|---|---|---|
| What gets decided by the end | Three things, in writing: one thing retired, one thing rebuilt, one thing confronted again. Specific to the business. | A recommendation. Often a phased roadmap. Decisions deferred to “next steps.” | A capability demo and a procurement conversation dressed as strategy. | Generative ideas and a board of post-it notes. Decisions rarely made in the room. | Whatever the room can agree on. Sometimes a lot, sometimes nothing, depending on who’s there. |
| Who owns what comes out of it | A named CEO or executive sponsor. Required, not optional. The session doesn’t happen without one. | The consulting firm owns the deliverable. Inside the company, ownership often diffuses after the project ends. | No one inside the company. The vendor owns the relationship; the buyer owns the contract. | The innovation team, usually. Often disconnected from where real authority lives. | The CEO or the team collectively. Accountability depends entirely on follow-through. |
| How long it takes | Half a day to two days, depending on tier. Pre-work memos before. A signed document by the end. | Three to six months on average. Sometimes longer. | A half-day to a full day, often free or subsidized. The follow-up is where the time goes. | Two days on site to a multi-week program. | One to three days, typically once or twice a year. |
| Who’s selling something else | No one. No platform partners, no implementation revenue, no follow-on pipeline assumed. | The same firm often sells the implementation that follows. The strategy work is partly a sales conversation. | The vendor is selling the platform. The session is a procurement on-ramp. | The accelerator or lab has its own program economics — partnerships, sponsors, cohort fees. | No one inside. But individual leaders have their own agendas, which is its own problem. |
| What you walk out with in writing | A one-page commitment document, confidential, signed, dated, owned. Plus a decision calendar at higher tiers. | A deck. Often very thick. Frequently impressive. Rarely referenced six months later. | A capabilities brief and a proposal. | A summary report, photos of the whiteboards, a post-program retrospective. | Notes. Sometimes a memo. Sometimes nothing. |
| What pre-work is required | A CEO or sponsor scoping call before the session. Pre-work memos from each participant at the team-intensive tier. | Interviews, document review, data requests — typically weeks of preparation by the consulting team. | A discovery call. The vendor does the work to tailor the pitch. | Application materials. Pre-reads. Sometimes a charter. | Whatever the leadership team prepares for itself. Often very little. |
| Who’s allowed to attend | Senior leaders only. CEO-sponsored. Six to forty people depending on tier. No observers, no guests, no junior staff. | Mixed. Consulting firm interviews broadly; the strategy work itself is leadership-only. | Whoever the vendor wants to influence. Often broader than is useful. | The innovation team, plus invited executives. | Whoever’s on the leadership team. |
| What happens six months later | A document leadership can point to. A retired thing actually retired. A rebuilt thing actually being rebuilt. | A binder on the shelf. Sometimes the recommendations got implemented; often the world moved and the deck didn’t. | A signed contract, or no contract. Either way, the strategy question is still open. | Pilots that may or may not have scaled. A few people who had a good experience. | Depends entirely on whether the CEO held the line. |
If a consultant-led project, a vendor partnership, an accelerator, or an internal offsite is the right match for what you’re trying to do, we’ll tell you that. OBSOLESCENCE is built for leaders who’ve decided the deferral has gone on long enough.
Most leaders leave offsites energized. Leaders leave OBSOLESCENCE with three things written down that they're accountable for. The session produces something — not just a feeling of progress, but a document the team has seen, signed, and agreed to.
Signal & Horizon is accepting a small number of OBSOLESCENCE engagements for 2026 — by design.
If you are navigating a business-model question that AI has already started to answer for you — or a leadership team still treating AI as an upgrade rather than a reset — the conversation starts here. Brief, honest, no sales funnel. We'll tell you in the first exchange whether this is the right fit.