Adding Design to DevOps
summary
Claim: DevOps must own repeatable processes that let designers plug into CI/CD so features ship reliably. Workflow uses discover‑distill‑deliver with three discovery types: green field, as‑is/to‑be and plus‑one. Concrete fixes include component design systems, storyboards, deploy‑preview environments and one‑click human gates (legal separation) rather than blind webhooks. Example failures: designers forced to review only after PR merge, causing rework; client success: added manual deploy button and preview environments and reduced churn and review cycles. Tools referenced: Kubernetes, Docker, Jenkins, GitHub hooks and standard CI/CD pipelines.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 2:10What is DevOps and our role
- 5:46Process stability and responsibility
- 9:43Discovery in design and DevOps
- 15:24Human-centered design principles
- 22:29Distilling solutions for value
- 29:41Delivering continuous value
- 36:12Wrap-up and Q&A
related talks
34mYou only have to change one thing to do the DevOps
18mDesign Patterns For Efficient DevOps Processes
25mBringing Product thinking to DevOps
21mValue of DevOps Release Process in Data Teams
11mBreaking down the walls between developers and operations
34mDeploy, Release, CI/CD, Oh My! DevOps for the Rest of Us
28mDevOPs Lessons for Frontend Developers
41mThe Designers Are Coming