Pattern 10
Answer first, expand by need
Give orientation before inviting deeper study.
Concrete takeaway
Lead with a concise answer, then offer meaningful sections and depth controls.
Choose an approach
These are editorial decision conditions to validate. Some alternatives are successive states or can be combined; they are not always exclusive choices.
| Alternative | Use when | Tradeoff or requirement |
|---|---|---|
| A · Brief answer | The user needs orientation | Brevity can hide necessary qualifications |
| B · Structured depth | Several layers matter to the question | Structure takes space but aids scanning |
| C · Reader control | Users differ in desired depth | Depth settings must not alter quoted Scripture |
The problem
A long generated answer can bury its main point and overwhelm readers who wanted a short explanation.
The pattern
Lead with a concise answer, then offer meaningful sections and depth controls. Let people expand evidence or interpretation separately. A shorter explanation does not alter any quoted Scripture.
Compare the alternatives
Give orientation before inviting deeper study.
A · Brief answer
Orientation appears before detail.
B · Structured depth
Headings let readers choose the relevant layer.
C · Reader control
Length is a preference rather than a fixed word count.
Original wireframe proposals · No live controls · Grey rows represent schematic text, not loading states · Labelled placeholders are not Scripture quotations
Download this wireframe as SVGFailure modes
A wall of text with no navigation; hiding the answer behind repetitive disclaimers; shortening original Scripture when only the commentary length was changed.
What to validate
Ask people with brief and detailed tasks to find the answer and its evidence. Test that expansion remains understandable at enlarged text sizes.
Research-informed design proposal. These visual alternatives have not been tested with users in this atlas. Source findings, documented behaviour and this proposed adaptation are different kinds of evidence.
Sources and adaptation
This card is an original design synthesis. The following sources inform its content distinctions, interaction approach or review requirements; they do not validate the whole pattern.
- Progressive DisclosurePattern detail reviewed · The proposed reader transition is a domain adaptation.
- AI Chatbots Design GuidelinesPublished UX guidance reviewed · General chatbot research, not validation of these Bible-app patterns.
- GenAI UX Design PatternsPublic framework overview reviewed · The public overview supports this synthesis; linked material and individual examples were not exhaustively audited.
Common scenarios and flows
- Read a long passage from a conversation — Inspect complete Scripture without letting an embed take over the dialogue.
Design principles in this decision
Editorial application of Missional by Design. These values frame review questions; they do not validate a pattern’s effectiveness.
- Hospitality — Who can use this approach in their actual context, and what complete alternative exists for someone who cannot?
Compare alternatives using the task and evidence above. Record competing needs instead of treating a principle as an automatic verdict.