Let the answer change the interview. Keep the question still.
An adaptive form still needs a stable place to read, answer, and understand progress.
Questions were moving out of the useful reading area. The interview could generate relevant content, but its layout made that content harder to follow. I asked for the whole flow to be reviewed.
An adaptive interface has to change without becoming unstable. There is a difference between choosing the next question and changing the question someone is already trying to answer.
See the original requestInside the screen
One question. A brief beside it.
The active question needs to stay easy to find while the request grows more detailed.
Select a detail
The date control is directly below the active question. I want a person to understand what they are answering without searching around the page.
The summary sits in its own area. That gives previous information a home while the current question remains the main task.
The service cards introduce prices alongside the interview. Their presence does not make those estimates correct. I would check how they were derived and how uncertainty is communicated.
This July capture records one customer interview state. It cannot demonstrate focus retention, keyboard behaviour, or the stability of an animated transition.
The original request11 Jul 2026 · excerpt
the questions on the side are going off the screen and on the left the questions dont stay in the center
Excerpted from the development conversation. Punctuation is lightly edited; the surrounding story is an edited retrospective.
01
The model can plan ahead without moving the question.
The AI may have new information while someone is still reading or typing. That does not mean it should replace the visible question. I wanted the implementation to protect the current interaction and let the next step adapt after the answer. The person needs a stable object to act on, even when the system behind it is doing more work.
This is a subtle responsibility in an adaptive product. A model output can be relevant and still arrive at the wrong moment. The recorded change stopped the AI from replacing a question already on screen. That gives me a concrete behaviour to inspect: start an answer, allow the surrounding context to update, and check that the question and control remain the ones the person began answering.
02
A live brief is supporting information
The brief gained independent scrolling and was hidden when there was not enough room. It remained useful as a preview of what the system understood, but it no longer had to compete with the main question at every width.
The contact step was simplified, and an unclear final question was removed. That kept the end of the flow focused on the information needed to continue, rather than adding another vague prompt simply because the form could ask one.
03
The brief is useful until it steals the conversation.
The live brief helps someone see what the system understands. As it grows, though, it can become a second document competing with the current task. Independent scrolling on a wider screen gives that information a place without stretching the whole page. Hiding the supporting column on a narrow screen protects the space needed for the active question.
The answer history has the same problem at a smaller scale. Each new answer should remain reachable without widening the page or pushing the current control away. The actual intake capture lets me inspect these competing areas together. The responsive checks covered layout and validation, while the final submission was left unperformed to avoid creating a real request. That is enough to describe the interface milestone precisely, without inventing a completed customer journey.
A stable interview can still adapt the way someone answers. I return to that question in Let the answer shape the form.
Where this chapter landed
What changed.
Question positioning, visible question stability, answer history, and live brief behaviour were improved and checked responsively. Final request submission was deliberately not exercised in that review.
Added while revisiting this story · September 2026
The thinking behind the detail.
Research notes to take these decisions further. These sources were reviewed for this retrospective.
Stability includes keyboard navigation
W3C explains that focus order must preserve meaning and operation. My inference for this adaptive flow is that keeping the visible question stable is only part of the job; keyboard focus must continue to describe a coherent sequence too.