| name | einfach-machen |
| description | Apply the 5-step "Einfach-Machen-Methode" by Tom Sadowski to a goal. The method reduces complexity by analyzing user journey, focusing on key conversion drivers, eliminating noise, simplifying the essentials, and testing. Universally applicable — business goals (revenue, conversion, onboarding) or personal goals (weight loss, habits). Triggered by phrases like "wende einfach-machen an auf <Ziel>", "einfach-machen-methode für <Ziel>", "einfach machen auf <Ziel>", or the slash-command "/einfach-machen <Ziel>". The argument is the goal that the method should be applied to. Method by Tom Sadowski (book "Einfach machen") — see ATTRIBUTION.md. NOTE: Do not confuse with the built-in `simplify` skill (which is for code review). |
Einfach-Machen-Methode
A 5-step framework for reducing complexity to reach a goal more easily and efficiently. The core idea: don't focus on end results — identify the biggest conversion drivers and conversion killers, then optimize those specifically.
Method by Tom Sadowski (book "Einfach machen"). This skill is a tooling adaptation. See ATTRIBUTION.md for IP details.
When invoked
The user provides a goal as the argument. If no goal is given, ask the user to state the goal first — do not guess.
Walk through the 5 steps in order. Output each step as its own numbered heading with concrete, actionable recommendations — no abstract prose.
Step 1 — User Journey
Map out the typical path the target audience takes toward the goal. List the discrete phases the user moves through. Be specific: name the touchpoints, screens, decisions, or actions.
Step 2 — Focus
From the journey, pick the 1–2 phases with the highest leverage — the biggest bottleneck, the biggest drop-off, or the biggest opportunity. Justify the choice: why this phase and not another?
Step 3 — Eliminate
For the focus phase(s), list specific things that lower conversion and can be removed: extra steps, unnecessary form fields, distracting copy, redundant clicks, hidden defaults, friction points. Each item must be concrete and removable in practice — no "improve UX" placeholders.
Step 4 — Simplify
For what remains after elimination, list specific ways to make it easier, faster, or clearer: smart defaults, pre-selection, reduced decisions, plain-language wording, fewer required fields, lower cognitive load. Each item must be concrete and implementable.
Step 5 — Test & adapt
Always provide both of these — never just one:
- (a) Ideal measurement — what metric or instrumentation would prove the change works? Examples: A/B test on the focus phase, funnel analytics with event tracking, conversion rate before/after, time-to-completion.
- (b) Pragmatic measurement — if no analytics setup exists, what's the realistic alternative? Examples: 3–5 user interviews, beta-tester feedback round, before/after screen recording, manual observation, gut-check by a fresh-eyes reviewer.
Output format (hard requirements)
- Five numbered headings, in this exact order: User Journey → Focus → Eliminate → Simplify → Test & adapt.
- Each step's bullets must be concrete and actionable. If you cannot be concrete, mark the item as a question to clarify with the user before proceeding.
- Step 5 must always include both ideal and pragmatic measurement options.
- Do not write code. Suggest what to change; implementation is a separate follow-up.
- If the goal is too vague (e.g. "make the app better"), ask the user to narrow it before applying the method.
When NOT to use this skill
- Code-review / refactor / quality tasks → use the built-in
simplify skill or normal Claude Code tooling instead.
- Pure research / exploration → use Explore-style agents.
- Architecture decisions without a user-facing goal → use Plan mode.
Example invocations
/einfach-machen Sub-Conversion von Free zu Paid steigernwende einfach-machen an auf den Onboarding-Floweinfach-machen-methode für Gewicht reduziereneinfach machen auf Checkout-Abbruchrate
The argument is always the goal. The skill walks the 5 steps and outputs structured recommendations.
