Shane Murphy on Presenting an Unfinished Prototype Honestly in Cambridge

An unfinished prototype invites imagination, which is both its strength and its difficulty. A visitor may see a rough object and dismiss an idea that deserves attention. Another may imagine a finished capability that the team has not yet built. I think presenting a prototype well means giving people a clear frame for interpretation. The team should explain what the object is intended to explore, what can be demonstrated today and which questions remain open, then let the demonstration support that explanation.

Imagine a fictional Cambridge maker showing an early adjustable reading stand. The prototype can change angle and hold a sample booklet, but its folding arrangement is still being explored. The team wants feedback on whether the angle adjustment feels understandable. If the presenter introduces it simply as the company's new reading stand, visitors may judge the unfinished folding arrangement as a final choice. A more precise introduction directs attention to the part of the idea that is ready for a meaningful conversation.

I would separate visible qualities from intended qualities in everyday language. “This version lets us try the angle adjustment” describes the object in front of the visitor. “We are exploring a folding arrangement” describes work that remains open. Neither sentence needs an elaborate disclaimer. As Shane Ian Murphy, I think this distinction makes a demonstration more confident because the presenter is speaking clearly about the state of the work. Confidence does not require every aspect of an emerging idea to appear settled.

The physical setup can reinforce that clarity. Show the prototype in the condition visitors will actually experience, with sample material that suits the question being explored. If a part requires assistance from the presenter, explain that before inviting someone to use it. If a movement is fragile, demonstrate it in a controlled way rather than allowing a visitor to discover the limitation through an awkward failure. The purpose is to make the conversation useful, not to stage an impression of completeness that the object cannot sustain.

Feedback questions should follow the prototype's purpose. Asking “Do you like it?” may produce politeness or a broad reaction that is difficult to interpret. Asking someone to adjust the angle and describe what they expected to happen can reveal whether the action is understandable. The presenter should listen without turning every hesitation into a defence of the design. An explanation offered too quickly can hide the very uncertainty the team needs to see. The person's interpretation is part of what the prototype can teach.

My former role as chief business development officer and cofounder of Limitless Mobile gives context to my interest in presenting developing offers, but it does not supply a shortcut through the uncertainty of this imagined example. The maker still needs to distinguish a visitor's observation from the team's conclusion. If one person finds a movement awkward, that observation deserves attention. It does not by itself prove that every future user will struggle. A thoughtful discussion preserves what was observed without inflating its meaning.

Visitors may naturally ask when the product will be available or what its eventual form will include. The presenter should answer only to the extent those decisions have actually been made in the scenario. It is reasonable to say that the current session concerns the adjustment and that other choices remain in development. People can handle an open question when it is expressed plainly. Trouble begins when enthusiasm encourages the team to convert an aspiration into something that sounds like a settled commitment.

The session should close by returning to what was learned. Which movements were immediately clear? Where did people search for a control? Which expectations came from the shape of the object itself? Those questions connect the prototype to the next design decision. Showing unfinished work honestly does not diminish the idea. It gives the audience a useful role and gives the team a better chance of hearing something it can act on. A prototype earns its place when it makes an uncertain question concrete enough for other people to explore.