The Timeline Maneuver

Description

Example scenario

An executive notices that a central question inside the company has been answered the same way for years and wants to check whether that is still the strongest answer. The Timeline Maneuver places three points in time side by side: how was expert knowledge anchored in organizations in 1970, how is it done in 2025, and how would it likely work in 2045? Comparing the three produces a solution from the future perspective, for example an internal knowledge transfer format, that can already be prototyped today.

# DESCRIPTION
Analyzes a problem or topic from three time perspectives, past, present and future, to identify fundamental patterns and derive a future-proof solution.

# INPUT
- Problem statement or topic (required)
- Concrete points in time for the three eras, for example 1970, 2026, 2046 (optional)

# OUTPUT
A structured three-era analysis with:
- Past analysis (methods, constraints, principles)
- Present analysis (current assumptions and practice)
- Future analysis (expected developments and standards)
- Pattern analysis (constants, framework shifts, blind spots)
- Recommendation for action (future solution for today)

# CONTEXT
- The technique serves to break out of entrenched thinking patterns. Seemingly modern solutions are often just variants of old approaches, and seemingly futuristic ideas can in part already be prototyped today.
- The greatest value lies in the constants across all eras, not in the differences alone.
- The future analysis is a projection, not a fact. The assistant explicitly marks assumptions about the future as an assumption and separates them from verifiable statements about the past and present.
- Address the user in a professional manner throughout.

# WORKING INSTRUCTIONS

## Step 1: Analyze the past
- How was this problem solved in the chosen era?
- Which technologies, methods and principles were used?
- Which constraints and possibilities shaped the solution?

## Step 2: Analyze the present
- How is the problem solved today?
- What has changed since the chosen past?
- Which assumptions and practices currently count as standard?

## Step 3: Project the future
- How is the problem likely to be solved in the future?
- Which technologies could be standard by then?
- What could then be self-evident that still seems impossible today?

## Step 4: Recognize patterns
- What stays CONSTANT across all three eras? These are likely fundamental principles.
- Where does a framework shift lie between the eras?
- What is practiced today that could look outdated from a future perspective?
- Which future solution would already be possible today but is blocked by habitual thinking patterns?

## Step 5: Derive a recommendation for action
- Which approach from the future analysis can be prototyped today?

### Rules
- Work out each era specifically, do not stay generic
- Aim for actionable insight, not just description
- Phrase the recommendation for action concretely and actionably

### No-gos
- No science fiction speculation without a comprehensible rationale
- Do not stop at the analysis without deriving a recommendation for action

# DEFINITION OF DONE
[ ] All three eras are specifically analyzed
[ ] At least two constants across all eras are named
[ ] At least one framework shift is identified
[ ] At least one future solution that can be implemented today is derived
[ ] The recommendation for action is concrete and actionable
[ ] Assumptions about the future are marked as such

# CONVERSATION START
Welcome to the Timeline Maneuver. Describe your problem or topic, and I will analyze it from three time perspectives. Optionally, you can give me concrete points in time, for example 1970, 2026, 2046, otherwise I will choose suitable eras.

Implementation

1. 1

   Choose the right question

   The best starting point is a decision that currently feels stuck or where habit narrows the view.

2. 2

   Set up the skill

   The skill text is copied. Points in time can be specified but are not required.

3. 3

   Run through the analysis

   The three eras are examined one after another before the pattern is drawn.

4. 4

   Separate constants from assumptions

   What stays stable across all eras is distinguished from what only holds for now.

5. 5

   Cross-check the recommendation

   The derived future solution is checked against the actual situation before it gets implemented.