[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-261430-105":53,"doc-detail-261430-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","athlon-designops-presentation-what-weve-learned-from-teamwork-between-design-and-engineering-teams","Athlon DesignOps Presentation - What We’ve Learned From Teamwork Between Design and Engineering Teams","","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.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/athlon-designops-presentation-what-weve-learned-from-teamwork-between-design-and-engineering-teams/261430/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/athlon-designops-presentation-what-weve-learned-from-teamwork-between-design-and-engineering-teams/261430.png","ImageObject",442,249,{"name":88,"@type":89},"Seraphina","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-11-05","2026-09-14",true,{"@type":98,"interactionType":99,"userInteractionCount":35},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What does the presentation say about when design is considered “ready”?","Question",{"text":108,"@type":109},"Design is not ready until the product is ready, meaning designers must align with engineering and production readiness.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"Which principles are emphasized as most important in the DesignOps process?",{"text":113,"@type":109},"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.",{"name":115,"@type":106,"acceptedAnswer":116},"How does the presentation describe the evolution of their process over time?",{"text":117,"@type":109},"It moves from documents to collaboration tools, showing how the growing designer toolset supported more collaborative, iterative teamwork across stakeholders.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},261430,1791744467,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":35,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":15,"preview_page_count":4},962075114101,"https://ap-avatar.wpscdn.com/avatar/e000253a75eb197efd?x-image-process=image/resize,m_fixed,w_180,h_180&k=1780044092746381165","Hello DesignOps.  \nDesign isn't ready until the product is ready  \nWhat we’ve learned from years of teamwork between design and engineering teams.  \n© Athlon 2022  \nHello DesignOps.  \nMihajlo Nikolic  \nShort bio:  \n– Design career from early age  \n– Later shifts from design to technology  \n– 34 years experience with computers  \n– 24 years professional experience in the digital field  \n– Co-founded Athlon in 2007  \n©  \n©  \nThe designer’s nightmare  \n– Limiting / restrictive  \n– Cumbersome administration  \n– Boring!  \n– So not creative…  \n– … add random rant  \n© Athlon 2022  \n© Athlon 2022  \nFocus on what’s important  \n– Effective communication  \n– Clear responsibilities  \n– Properly timed feedback loop  \n– Involve the right people and the right amount of people  \nProcess 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.  \n© Athlon 2022  \nWho are the right people?  \nIt varies from project to project…  \nbut it most likely involves a few of these roles:  \n– You, the designer  \n– Decision makers  \n(product owners, manager etc.)  \n– Product or project managers  \n–  ENGINEERS!  \n© Athlon 2022  \nWhat?  \nDesign is not only visual, it’s functional.  \nYou can’t have great product design if you don’t involve good engineers.  \nDesign and engineering teams need to communicate well and frequently. If your process does not include that, you are in trouble.  \n© Athlon 2022  \nPast and present – how our process has evolved  \nFrom documents to collaboration tools, the benefits of the growing designer toolset  \n© Athlon 2022  \n| Stages of process needs |\n| --- |\n| 1998 > 2022 evolution (personal and with Athlon)\u003Cbr>Solo player “We work” Shit got serious |\n\nAcceptable for  \n- Simple projects, freelance gigs  \nAttitude / conflict areas  \n- I know what I’m doing  \n- It’s not my problem  \nProcess  \nWhat process?  \nAcceptable for  \n- Slightly more challenging projects requiring more than one person  \nAttitude / conflict areas  \n- It’s ready when it’s ready  \n-You didn’t make it clear  \n- I can’t do it, I’m on another job  \nProcess  \nHandovers, meetings, planning etc.  \nAcceptable for  \n- Product development. Things have to work!  \nAttitude / conflict areas  \n-Who’s responsible?  \n- I didn’t get the notification/update.  \n-Where can I see it?  \nProcess  \nFocus on iterative and collaborative teamwork with multiple stakeholders.  \nTask management + Mails  \n> PM system + Documentation  \n> Team Workflows  \n© Athlon 2022","cbCaisCanJ0WjgGR","https://ap.wps.com/l/cbCaisCanJ0WjgGR","pdf",6824458,35,"English","# Hello DesignOps\n## The designer’s nightmare\n## Focus on what’s important\n# Who are the right people?\n## Design is not only visual\n# Past and present - how our process has evolved\n## Stages of process needs","[{\"question\":\"What does the presentation say about when design is considered “ready”?\",\"answer\":\"Design is not ready until the product is ready, meaning designers must align with engineering and production readiness.\"},{\"question\":\"Which principles are emphasized as most important in the DesignOps process?\",\"answer\":\"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.\"},{\"question\":\"How does the presentation describe the evolution of their process over time?\",\"answer\":\"It moves from documents to collaboration tools, showing how the growing designer toolset supported more collaborative, iterative teamwork across stakeholders.\"}]","Athlon DesignOps Presentation - What We’ve Learned From Teamwork Between Design and Engineering Teams | PDF",1789353552]