More Code with Jason episodes

337 - User Testing, Paper Prototypes, and Escaping Hourly Billing with John Athayde thumbnail

337 - User Testing, Paper Prototypes, and Escaping Hourly Billing with John Athayde

Published 17 Nov 2026

Duration: 01:17:50

Design solves problems rather than just aesthetics, requiring user testing and accessibility as core practices, while consulting shifts toward value-based advisory over hourly billing.

Episode Description

In this episode I talk with John Athayde, designer-developer and co-author of The Rails View, about what architecture school taught him about software...

Overview

The conversation explores how architecture training shapes software design thinking, emphasizing that design is fundamentally about solving problems rather than aesthetics. John Athay describes his background as a "broad-based designer developer" who went to architecture school and taught himself coding, noting that an architect "learns less and less about more and more, till they know nothing about everything" while an engineer is "a hyper specialist, typically." He argues that "every decision you make in the code base is actually a design decision" and that service design is "the closest thing we've got to architecture" because it addresses "the entire life cycle of a person with the organization."

The discussion covers practical user testing methods, including paper prototyping where the tester acts as the web server by sliding pages across a table, and recorded sessions capturing screen, camera, and clicks. Key principles include observing behavior rather than asking opinions, testing with five to ten people to surface most issues, and measuring concrete metrics like "time on task." The conversation also addresses accessibility as "table stakes to ship software today," progressive enhancement over JavaScript single-page applications, and the value of starting with "a blank HTML page with text on it" before adding visual elements.

The final portion shifts to consulting economics in the AI era, discussing the shift from hourly billing to flat-rate or retainer models, the higher value of advisory work over implementation, and how AI is compressing lower-level consulting while creating space for strategic, higher-ticket engagements.

What If

  • What if you validated your next feature with a single user before writing any code?

    • Move: Draw the interface on a blank sheet of paper, give a stranger a pen, and act as the "web server" by sliding subsequent pages across the table as they fill fields. Propose doing this before opening an IDE.
    • Why Now? Athay notes that "just one will get you like on initial product stuff" and that the first design pass is often "not even usable remotely," meaning a 10-minute paper session can surface fatal flaws before hours of coding are wasted.
    • Expected Upside: You may discover, as Athay's team did with their scheduler, that users "didn't realize it was a drag and drop interface" and need onboarding - fixes that are trivial on paper but expensive in code.
  • What if you stripped your marketing page to plain text in a blank HTML file before touching any styling?

    • Move: Create a page with only your copy in Times New Roman black text, no colors, no shapes, no layout. Propose evaluating whether the text alone "does the job" before adding any visual design.
    • Why Now? Athay argues that "if the text does the job, then it does the job. And if it doesn't, it doesn't," and that colors and shapes "can trick you into thinking that it's good" when the underlying content fails.
    • Expected Upside: You avoid polishing a page whose copy doesn't convert, and you build a foundation where added design elements are "design solutions to design problems" rather than "window dressing."
  • What if you replaced hourly billing with a flat-rate monthly retainer for advisory work?

    • Move: Package your expertise into a monthly retainer for strategic conversations - reviewing code, interviewing contractors, and advising on architecture - rather than charging per hour for implementation. Propose positioning it as a distinct service from "commodity coding."
    • Why Now? Athay explains that "if you charge something that's outside the range of perceived market rates, people are going to ask why," but a different service category avoids that comparison. He also notes AI is "nuking from orbit" the lower end of the consulting market, making implementation work harder to differentiate.
    • Expected Upside: You can command higher rates without justifying them against hourly benchmarks, and you free yourself from "arguing accounting" to focus on "solving problems."

Takeaway

  • Test your next feature with one person using paper and a pen before writing code: draw the screens, hand over a pen, and act as the server by sliding pages across the table.
  • Start every design as plain text on a blank HTML page with no colors or shapes; only add visual elements once the content "does the job" in its stark form.
  • Treat WCAG 2.2 AA compliance as your shipping baseline: check contrast ratios, semantic markup, and navigation landmarks before considering a product ready.
  • Build with progressive enhancement: make core functionality work with server-side rendering and boring HTML first, then layer in JavaScript enhancements as optional improvements.
  • Shift from hourly billing to a flat-rate or monthly retainer model, positioning your work as advisory or strategic rather than implementation, to avoid rate comparisons with commodity coding.

Recent Episodes of Code with Jason

5 Sept 2026 327 - Will Carey, CTO of Brand New Box

"Explores how software agencies are shifting from coding to defining client needs, emphasizing AI's role in development while stressing the importance of conceptual design and real-world problem-solving."

More Code with Jason episodes