Product context
A second-generation AI plush companion, developed as an iteration on an existing platform.
A second generation is a different project from a first one. The internal layout exists, the service is running and the failure modes are known, so the work shifts from design to refinement. The risk also shifts: changes that look small can break something that was working.
The value of the iteration is that improvements can be specific. Sound clarity, response latency, battery behaviour and the plush feel can each be addressed against a known baseline.
Typical projects
Three situations lead to a second generation rather than a new platform.
Experience refinement
The layout stays; the audio, latency and behaviour are improved.
Cost optimisation
Components and assembly revised to improve margin without changing the experience.
Content expansion
New languages or content scope on the same hardware, which tests the update path.
Before sampling
What must not change is the first question in an iteration.
Write down the behaviours that made the first generation work before changing anything. Sound position, response timing and the feel of the plush are the three that are most easily disturbed by what look like minor changes.
- The list of intentional changes and the list of things that must not change
- Backward compatibility for content and accessories
- Which tooling is reused and which is re-cut
- How the new edition is distinguished from the previous one