Past speaking WordCamp Ottawa 2017 Panel
Designers & Developers: Bridging the Gap (Panel)
A five-person panel at WordCamp Ottawa 2017 on the working relationship between designers and developers — the experience of collaborating across the role boundary, advice each side has for the other, and the communication techniques that actually scale on real projects.
Where and when
- Event: WordCamp Ottawa 2017
- Date: Saturday, July 22, 2017
- Room: Bytowne Room (Room 2)
- City: Ottawa, Ontario, Canada
- Format: Panel discussion
The premise
From the published WordCamp Ottawa 2017 session listing:
“Designers and Developers discuss their experiences working together, including advice for one another and communication techniques.”
Panel members
- Meagan Hanes
- Christie Witt
- Miriam Goldman
- Shannon Smith
- Christopher Ross
Watch or read
This panel was not recorded for WordPress.tv.
What this kind of panel typically argues (stance ranges, not quotes)
Reconstructed framework. Panel transcripts are rarely archived, and this talk wasn’t recorded. The section below maps the documented tensions in the designer–developer working relationship that a 2017 panel of this composition would have engaged. Specific positions taken on stage by any individual panelist are not attributed.
The recurring tensions
- Handoff vs continuous collaboration. The “throw it over the wall” model — designer finishes mockups, developer implements — was already aging out in 2017. The continuous-collaboration alternative (designers in the implementation conversation from week one, developers in the design conversation from week one) was becoming the accepted best practice but was still uneven in actual freelance teams.
- Design system vs custom-per-project. Component libraries and design tokens were entering the mainstream. Panels of this era debated whether small WordPress projects needed the overhead of a system, or whether the system itself created friction that wasn’t worth the consistency gains.
- Deadline vs polish. Designers and developers feel deadline pressure differently. The panel-style format usually surfaces this honestly — and “we cut the polish” usually has different meaning to each side.
- Code literacy on the design side, design literacy on the dev side. The 2017 conversation about “should designers code” had moved past binary yes/no into nuance: designers who can prototype in-browser and read enough CSS to spec changes were noticeably more effective. The reciprocal — developers with enough visual literacy to make small design judgment calls — was less discussed but equally important.
- Shared language for ambiguity. The hardest part of designer-developer collaboration isn’t the work — it’s having a shared vocabulary for the grey areas (responsive break behaviour, motion design, accessibility trade-offs, edge-case content states).
What this panel format adds
A five-person panel produces something a solo talk can’t: live disagreement. The format makes it visible that there isn’t a single correct answer to the designer-developer relationship — different teams, different stack choices, and different client types all push the equilibrium around. Panels of this composition tend to be more useful for attendees who already work in cross-functional roles than for those looking for a single playbook.
The 2017 framing has aged into 2026 mostly intact: the same tensions still surface in cross-functional teams. The added layer is AI tooling, which changes some of the handoff dynamics — designers can now generate working component code from a Figma file, and developers can now generate plausible visual variants from a brief — but the core question of how the two disciplines collaborate hasn’t fundamentally shifted.
Sibling Ottawa 2017 talk
The same speaker delivered a solo talk earlier the same day: The Secret Art of WordPress — WordCamp Ottawa 2017.
Related work
- Other Ottawa talks by the same speaker: WordCamp Ottawa 2013 · WordCamp Ottawa 2014
- Working with the speaker: WordPress services · Get in touch
Ready for the Next Step?
If this is relevant to your goals, we can scope practical next steps for Designers & Developers: Bridging the Gap (Panel).
