Episode #59: Designing Usable Products with Paper Prototypes and Customer Feedback with Johnny Bilotta

A better digital experience can begin with an index card, not a polished interface. In Episode #59, Johnny Bilotta explains why product teams should make ideas tangible early, observe real behavior, and create several paths for customers to keep the team honest.

What you'll learn

• Why industry context matters even when software problems look similar

• How sketches and paper prototypes expose usability issues before teams invest heavily

• Which feedback methods work when time and access vary

• Why using your own product can reveal problems hidden by implementation familiarity

• How humility, empathy, and a strong professional network support product leadership

Learn the variables that are specific to the industry

Bilotta's career moved through design, software, finance, clinical-trial technology, and supply-chain products. Across those settings, he noticed that software teams often solve structurally similar problems with different industry variables. The reusable pattern matters, but so does domain knowledge.

He gives a financial software example: login decisions that seem routine can carry security implications that inexperienced teams miss. If a product is built on the wrong assumption, changing the account structure years later can become expensive. The same principle applies beyond finance. Product teams should identify the rules, terminology, risks, and workflows that are specific to their market before treating a familiar interface pattern as universally safe.

At Chain.io, Bilotta discusses another recurring challenge: helping a company separate bespoke professional services from software that customers can use more independently. That means relying less on training and more on support documentation and an interface that guides people toward the right action. This is not merely a visual design task. It is a product model and change-management problem.

Make ideas tangible before polishing pixels

Bilotta connects his industrial design background to what he calls digital ergonomics. His process still starts with sketching. A feature can begin as lines and boxes drawn from a high-level view. Index cards are particularly useful because they approximate a mobile screen and can be rearranged quickly to explore different flows.

Paper prototyping gives the team something visible to discuss without creating the false confidence of a finished design. Colleagues can move a view, challenge a sequence, or notice where an interaction breaks before anyone spends time perfecting pixels or writing code. This preserves a traditional design-studio practice while making collaboration easier.

The practical lesson is not that teams must avoid software. Bilotta sometimes goes directly to code when the path is clear. The warning is against making that the default. A low-cost representation creates room for disagreement and learning while changes are still easy.

Combine observation, prototypes, and product usage

No single research method fits every situation. Bilotta notes that the right approach depends on the industry, user profile, team, and available time. When possible, his teams have placed prototypes in front of prospective customers, walked through a demo, and observed people using the flow.

For interface audits, he has also spent a day watching and filming someone do their job with the software being improved or replaced. That kind of observation exposes muscle memory and recurring behavior. Some patterns may be efficient; others may be workarounds created by a poor experience. Either way, watching the work provides context that a verbal description can miss.

Teams should also use their own product when possible. At Chain.io, the staff may not need supply-chain software for their everyday responsibilities, but that distance is risky. Developers and designers can become familiar with what they built without experiencing it as a customer would. Regular internal use, testing, and exploration can reveal ergonomic flaws earlier, even when the internal use case differs from the customer's task.

Build feedback into the product and the operating rhythm

Bilotta outlines several complementary feedback channels. In-product controls can let users report bugs or comment on a particular view. He said Chain.io was also considering a product analytics tool such as Pendo to identify where users leave flows or disengage. These signals could help the team locate friction, although they would still require interpretation.

Chain.io also established a quarterly customer advisory board that includes purchasers and power users. The team keeps its product update brief, then uses most of the session as a customer town hall. Bringing together people with budget authority and people with deep day-to-day experience creates different forms of accountability. Bilotta sees this customer group as an oversight mechanism that can challenge the team's assumptions and recognize what is working.

His leadership lessons reinforce the same approach. Earlier in his career, believing he was the smartest person in the room led to mistakes. He found more success by listening, provoking useful reactions, and accepting that other people held information he needed. A professional network also became a source of resilience when a role ended, producing immediate opportunities through relationships built over many years.

Design with humility and empathy

Bilotta describes sensitivity to criticism as something he learned to use constructively. Feedback can hurt, but design must communicate and function clearly for other people. Empathy helps teams receive criticism, resist harmful patterns, and consider inclusion in their decisions.

Listen to Episode #59 with Johnny Bilotta for the full conversation on digital ergonomics, customer feedback, community, and product leadership: play the episode.