Page role
Support path, not core navigation owner.
The quiz belongs in the ecosystem because it helps route interest, but it should remain subordinate to the main Autonomous Living spine and the more direct support lanes.
Quiz and segmentation route
Time Management Archetype Personality Quiz
This route exists to preserve continuity and support early segmentation. It should function as a campaign/support surface that helps qualified visitors move into the right next step without pretending to be the main brand story.
What this page should do
Segment, qualify, and route — not replace the commercial architecture.
The quiz should help people identify a useful entry point into the system. It is valuable as a campaign and support asset, but it should not become a substitute for clear flagship, direct-help, or TMAAS positioning.
What the quiz should connect to
A good quiz should make the next move clearer, not trap people in novelty.
The point is not personality entertainment. The point is better route selection and cleaner movement into the right lane.
Main individual path
Flagship route for most people
For most users, the quiz should support movement toward Autonomous Living and the broader Silver-oriented path.
Go to the flagship routeHigher-touch path
Direct help for urgency or complexity
When the quiz reveals more pressure or complexity, it should support movement toward the higher-touch direct-help lane.
Go to direct helpCompany context
TMAAS for organizational fit
If the use case is clearly team- or organization-level, the quiz should not pretend that the consumer path is the right destination.
Go to TMAASImplementation note
The actual quiz mechanics still need a deliberate implementation choice.
The route shell is now preserved, but the real quiz mechanic still needs to be decided explicitly: embedded form, external quiz engine, Airtable-backed flow, or another routed support experience.
Next move
Keep the URL and page role now, then decide the actual quiz engine later.
That preserves launch continuity and architectural clarity without forcing a rushed implementation choice for the underlying quiz mechanics.