Not a description of how I work. A direct look at it.
Three independent working examples — an orientation audit excerpt, an information architecture blueprint, and an orientation journey. Each is based on Bettina's own independent projects, not a paid client engagement, and is shown here as an illustrative working method rather than a finished deliverable.
← Back to For OrganizationsOrientation Audit — Excerpt
Independent working example · Gesundheitsnavigator (Health Navigator) concept page
This is an excerpt from an independent audit conducted on one of Bettina's own projects, used here as a working example of her analysis method — not a paid client engagement or a complete audit.
Subject: the Gesundheitsnavigator concept page — a German-language page introducing an orientation tool for women navigating complex health decisions. Method: a structural and content review against the same criteria applied across Praxis Liebenswert's own portfolio.
The page clearly explains the idea behind the Gesundheitsnavigator: helping women orient themselves in health information and decisions without diagnosing or directing. The concept is well-articulated and the target audience is specific.
The page describes what the tool is for, but a first-time visitor cannot yet experience the orientation logic itself — there is no interactive, state-based flow live on this page. The gap sits between the promise ("this will help you find your next step") and the immediate experience (a description, not a demonstrated next step).
The text itself is well-structured. But it asks the visitor to hold an abstract concept in mind — "a navigator that adapts to my situation" — without a concrete example. For someone already dealing with a stressful health situation, an abstract promise adds a small but real interpretive burden.
No visible, low-commitment first action exists between "read about the concept" and "get in touch." There is no sample question, no single worked scenario, no visible entry point into the underlying logic.
- Add one concrete example: a single situation → one sample orientation output, visible without any interaction required.
- Convert one section of prose into a visible decision-tree fragment, so the mechanism is shown, not just described.
- Add a low-commitment next step above the general contact call to action.
Add one worked example. Convert one paragraph into visible decision logic.
Build the interactive, state-based demo behind the concept.
Add micro-copy clarifying the current status of the tool.
Full visual redesign of the concept page before a working demo exists.
Axes: Impact on visitor orientation (vertical) · Implementation effort (horizontal)
Two changes — one worked example and one visible decision fragment — would close most of the orientation gap without any new development.
Information Architecture Blueprint — Excerpt
Independent working example · System Compass (Systemkompass)
A simplified view of the layered logic behind System Compass — an independent, privacy-first orientation tool for states of inner overwhelm. Shown here as architecture, not as finished screens.
Entry & Framing
A calm framing step: what this space is — and, just as important, what it is not (no diagnosis, no data storage, no therapy claim).
State Identification
Two inputs held separately rather than merged into one category:
- Current nervous-system state (e.g. overwhelmed, shut down, wired, calm)
- Life phase / situational context (e.g. fertility, pregnancy, postpartum, general)
Reflective Content
State and context together select from a library of grounding content and journaling prompts — written for that specific combination, not just for the general topic.
Local Processing
All input is processed in the browser only. Nothing is transmitted or stored — an architectural decision, not a privacy-policy footnote, and one that shapes what the tool can and cannot do (no history, no account, no cross-session personalization).
Branching Next Step
Three honest exit paths, not one generic "contact us":
Stay and continue reflecting
Routed to Quiet Rooms for audio-based regulation
Plain-language pointer to professional help — always visible, never hidden behind a menu
Decision points are kept separate instead of collapsed. A tool that merges "what state are you in" and "what is your situation" into a single question loses information a person could have given clearly.
Orientation Journey — Before / After
Independent working example · Illustrative framework, not a specific patient case
An illustrative comparison — not a medical journey, but an orientation journey: what changes when a structured orientation system exists between an event and a decision.
- Event — a diagnosis, referral, or difficult result
- Searches broadly for information
- Finds volume, not orientation — many pages, no clear priority
- Cognitive load rises — harder to judge what matters
- Uncertainty about the next concrete step
- Decision delayed, or made from fear rather than clarity
- Event — a diagnosis, referral, or difficult result
- Enters a structured orientation point (guide, navigator, or content architecture)
- Situation is identified, not just the topic
- Relevant information surfaces — the rest is deliberately withheld, not hidden
- One clear next step is presented, with its own boundaries stated
- Decision made with orientation, at the person's own pace
The difference is not more content. It's a system that decides, deliberately, what to show — and what to leave out.
See how this applies to your organization
These are working examples from independent projects. A project inquiry usually starts with a short look at your own content or patient journey — not a generic proposal.