Athlon DesignOps Presentation - What We’ve Learned From Teamwork Between Design and Engineering Teams

Sep 14, 2026

DesignOps presentation outlining practical lessons from long-term collaboration between design and engineering teams. Content emphasizes that design becomes complete only when the product is production-ready, with focus on effective communication, clear responsibilities, and properly timed feedback loops. It identifies suitable roles and stakeholders per project, contrasts restrictive and cumbersome processes with collaborative workflows, and traces how the process evolved from documents to collaboration tools. It also highlights iterative task management using PM systems, documentation, and team workflows.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages35

Reading Time12 min

AccessFree to download

Hello DesignOps

The designer’s nightmare

Focus on what’s important

Who are the right people?

Design is not only visual

Past and present - how our process has evolved

Stages of process needs

Hello DesignOps. Design isn't ready until the product is ready What we’ve learned from years of teamwork between design and engineering teams. © Athlon 2022 Hello DesignOps. Mihajlo Nikolic Short bio: – Design career from early age – Later shifts from design to technology – 34 years experience with computers – 24 years professional experience in the digital ﬁeld – Co-founded Athlon in 2007 © © The designer’s nightmare – Limiting / restrictive – Cumbersome administration – Boring! – So not creative… – … add random rant © Athlon 2022 © Athlon 2022 Focus on what’s important – Effective communication – Clear responsibilities – Properly timed feedback loop – Involve the right people and the right amount of people Process doesn’t mean boring documents and spreadsheets, it simply means ensuring you have what’s necessary, when you need it. It boils down to commitment and teamwork. © Athlon 2022 Who are the right people? It varies from project to project… but it most likely involves a few of these roles: – You, the designer – Decision makers (product owners, manager etc.) – Product or project managers – ENGINEERS! © Athlon 2022 What? Design is not only visual, it’s functional. You can’t have great product design if you don’t involve good engineers. Design and engineering teams need to communicate well and frequently. If your process does not include that, you are in trouble. © Athlon 2022 Past and present – how our process has evolved From documents to collaboration tools, the beneﬁts of the growing designer toolset © Athlon 2022 | Stages of process needs | | --- | | 1998 > 2022 evolution (personal and with Athlon)
Solo player “We work” Shit got serious | Acceptable for - Simple projects, freelance gigs Attitude / conﬂict areas - I know what I’m doing - It’s not my problem Process What process? Acceptable for - Slightly more challenging projects requiring more than one person Attitude / conﬂict areas - It’s ready when it’s ready -You didn’t make it clear - I can’t do it, I’m on another job Process Handovers, meetings, planning etc. Acceptable for - Product development. Things have to work! Attitude / conﬂict areas -Who’s responsible? - I didn’t get the notiﬁcation/update. -Where can I see it? Process Focus on iterative and collaborative teamwork with multiple stakeholders. Task management + Mails > PM system + Documentation > Team Workﬂows © Athlon 2022

FAQs

What does the presentation say about when design is considered “ready”?

Design is not ready until the product is ready, meaning designers must align with engineering and production readiness.

Which principles are emphasized as most important in the DesignOps process?

The presentation highlights effective communication, clear responsibilities, properly timed feedback loops, and involving the right people at the right time and in the right amount.

How does the presentation describe the evolution of their process over time?

It moves from documents to collaboration tools, showing how the growing designer toolset supported more collaborative, iterative teamwork across stakeholders.

Sep 14, 2026

Uploaded by Seraphina