Polaris Shift Journal

Ideas for a moving North Star.

Long-form arguments, concepts, and research notes about how AI changes what organizations should optimize for. The goal is not to summarize technology. It is to understand strategic consequence.

FOUNDING EDITIONSTRATEGY · AI · CUSTOMER · ORGANIZATION
White paper 01 · October 2026

When to Move Your North Star

A framework for strategic reorientation in the age of AI, with research context, fictional decision rehearsals, and a practical North Star review.

Read the white paper →
Decision Histories · 01 · Published October 29, 2026

Adobe: when progress makes the dashboard look worse.

A sourced reading of the 2012–2013 subscription transition. Examine what leaders could know at the time, consider the choices, and separate changing a business model from changing the North Star.

Explore the decision history →

Staying can be a decision, too.

Darko Tushev ·
An argument within the Polaris framework, with a fictional teaching example. No company findings or measured results are claimed.

If every AI signal leads us to a new North Star, we have made changing direction the goal. I think the framework should leave room for a less dramatic answer: the current direction still deserves our commitment.

That answer needs reasons. “We have already invested too much” protects a past decision. “The outcome still matters, the route still works, and the proposed alternative has not earned the disruption” makes a claim we can examine.

Signal: notice the possibility without making the commitment.

Imagine a retailer considering an AI assistant that drafts refund replies. The demonstration is promising. The team's existing North Star is durable issue resolution, and its current process already carries a case through to someone who can resolve it.

For this invented discussion, suppose a small review of completed cases finds no recurring handoff failure, while the demonstration has not yet shown how it handles missing payment records or exceptions. Those are scenario assumptions, not research evidence. They make Stay plausible. They do not prove the existing process is best.

Shift: ask what changed in the work.

The demonstration changes what may be possible in drafting. It has not established that the customer's need changed, or that the proposed workflow resolves refunds more reliably. The existing changing-work evidence review offers a related caution about comparisons: check what work enters the measure before interpreting a gain. That research does not settle this fictional retailer's decision.

Keep curiosity alive through an offline comparison of representative cases, including exceptions. Compare the full path to resolution, staff effort, and error handling. A faster draft could still be useful. The question is whether its benefit survives the rest of the work.

Star: say exactly what we are staying with.

Stay, here, means retaining durable resolution as the governing outcome and keeping the current customer-facing workflow for now. It does not require stopping investigation. The commitment under review is a rollout of the proposed assistant, not whether the team may learn about AI.

Adjust becomes more persuasive if comparable cases show that a different route improves resolution or reduces effort without unacceptable errors. Shift requires a stronger argument: evidence that the governing outcome no longer captures the value people need. Dissatisfaction with one tool does not establish that the North Star should move.

System: give Stay an owner and a review trigger.

In this fictional decision, the support lead records the scope, assumptions, and reasons for deferring rollout. The payments partner checks whether the case review misses unresolved refunds. Review in four weeks, or sooner if repeat contacts, exception delays, or a relevant capability change challenge the reasoning.

Agree before the comparison what counts as resolution, which cases are comparable, and which errors would make rollout unacceptable. If there are too few cases or refunds have not settled, extend observation. An average reply-time improvement alone cannot answer the resolution question.

What would change my mind?

Repeated unresolved cases would weaken the assumption that today's route works. A credible comparison showing better resolution at acceptable effort and risk would strengthen Adjust. Customer evidence that exposes an unmet need beyond the current outcome would reopen the Star itself.

Missing evidence deserves a different sentence: “We do not know enough yet.” A bounded pause can be sensible when the decision is reversible and delay is tolerable. It should also name the cost of waiting and the evidence we will gather. Otherwise, Stay can become a comfortable way to avoid deciding.

For the next conversation, try this: What are we choosing to preserve, what would make that choice wrong, and when will we look again?

Record the decision in a North Star Brief →

Provenance: this is a Polaris argument applying SIGNAL → SHIFT → STAR → SYSTEM and Stay/Adjust/Shift. The retailer, case observations, comparison, and review schedule are fictional. For a different decision using the same setting, read the dashboard-versus-outcome example. For the full framework, read the white paper.

The dashboard improved. Did the customer's life?

Polaris Shift ·
An expanded version of the Lab's customer-support rehearsal. This is an invented teaching example, not a company case study or research finding. No business results are claimed.

Imagine a customer contacting a retailer about a refund that has not arrived. An AI assistant replies quickly, politely, and with the right policy. The conversation closes. The refund is still missing.

At the next team meeting, the dashboard looks encouraging: replies are faster and more conversations are automated. But the customer has to explain the same problem again. We might have made the support system more productive while leaving the person with more work.

Signal: a faster reply is now possible.

In the existing fictional rehearsal, AI reduces drafting time. Simple requests are resolved, but repeat contacts remain unchanged and complex billing problems still need human judgment and access to another system. Those observations invite a closer look. They do not prove that automation caused the unresolved problems.

Shift: the work can change. Has the need changed?

Drafting an answer and resolving an issue are different jobs. The new capability may change who prepares the response, how context moves, and when a person steps in. In this example, the customer's need remains familiar: understand what happened and get the refund problem resolved without starting over.

The useful question is: where does the case get stuck after the first reply? If the assistant cannot see the payment status or hand the case to someone who can act, better wording will not remove that obstacle.

Star: keep durable resolution in view.

A North Star names the outcome that should guide the work. Here, durable customer issue resolution still makes sense. Time to first reply and automation rate can help diagnose delivery, but neither tells us whether the missing refund arrived.

Adjust is a defensible provisional choice: preserve the outcome and change the route. Stay could be justified if the existing route already resolves problems reliably and the proposed change offers no useful improvement. Shift would need evidence that the governing outcome itself no longer captures the value customers need. A striking demo does not establish that.

System: try a small change that can teach us something.

For a bounded refund-support trial, keep human escalation available. Give one support owner responsibility for carrying case context into the handoff, and agree with the payments team on who can verify and resolve the refund status.

Before starting, define what counts as resolved and choose a follow-up window long enough for a refund to arrive. Compare similar simple and complex cases, record repeat contacts and failed handoffs, and check whether customers still have to repeat their story. Keep reply speed and support effort visible as trade-offs. If the comparison is small or cases differ, treat the findings as directional rather than causal.

At a review two weeks after the trial starts, ask what happened to the unresolved cases, not just the average response time. Continue only if resolution improves without unacceptable errors or escalation delays. Revise or stop if speed improves while customers remain stuck. If most refunds take longer to settle, extend follow-up before judging the outcome.

What would change our minds?

If the new route fails to improve resolution, the workflow proposal needs to change. If further customer evidence shows that resolution alone misses a more important need, reopen the North Star. We should be willing to question both, without assuming they must move together.

In your next meeting, try one question: When this number improves, what becomes easier for the person we are trying to help?

Try the Lab rehearsal, then choose Customer support →

Origin: the existing fictional customer-support rehearsal in Polaris Lab. The scenario, proposed trial, and decision interpretation are teaching material. They are not evidence of adoption, validated research, or measured impact. For the full framework, read When to Move Your North Star.

Foundational paper · Working draft

The Polaris Shift

AI strategy should not begin with where the technology can be deployed. It should begin with a harder question: what changed enough that the organization may need to reconsider what it is optimizing for?

Read the working draft →
Concepts in orbit

Ideas that extend the framework.

Each concept gives leaders a different way to notice when the current model is beginning to fall behind the environment around it.

North Star Debt · In development

When yesterday's definition of success becomes expensive.

The accumulated cost of continuing to optimize an old objective after behavior, economics, interfaces, or competition have changed.

Journey Compression · Interactive framework

When entire stages of the customer journey disappear.

AI can collapse discovery, evaluation, decision, and action into fewer interactions, changing what should be measured and where value is created.

Explore Journey Compression →
Agency Migration · In development

When decisions and actions move from people toward intelligent systems.

The strategic question is not only what AI can automate, but where responsibility, authority, and customer agency are moving.

Reorient Before You Rewire · In development

Do not redesign the organization around yesterday's destination.

Operating model transformation becomes dangerous when the system gets faster while the strategic reference point remains unquestioned.

Choose your depth

Enter the idea from where you are.

Polaris Shift is designed for both the curious visitor and the leader who wants to spend time with the full argument.

10 MINUTES

Experience the shift.

Start with the interactive homepage and understand the central thesis through Polaris, changing reference points, and the strategic framework.

Start the experience →
WORKING DRAFT

Read the argument.

Go deeper into why AI strategy should begin with changed assumptions rather than deployment opportunities.

Read the working draft →
ONGOING

Watch the environment.

Use Signal Watch to follow the developments that may create new strategic pressure on existing North Stars.

Open Signal Watch →
From ideas to evidence

Strategy should move when the evidence moves.

The Journal develops the ideas. Signal Watch tests them against a changing world. Together they create a loop between theory, evidence, and strategic interpretation.

THE RECURRING QUESTION

What changed this week that could matter to the North Star?

Explore Signal Watch →