Goal directed Design
summary
Company revamps its alert editor after defining seven goal-directed personas and runs cross-functional DPE workshops to map goals to features. The front end migrates from Ember to React, implements a Context API provider pattern with hooks, reducer and dispatch to eliminate prop drilling on a complex page, and splits visualization from business logic. The team ships an MVP, publishes a tiny sample app via QR with runnable code, and keeps a custom fetching library (not React Query) and react-table in place.
AI-written summary · about
chapters (16)
- 0:00Introduction and speakers
- 1:10About Sysdig and its product
- 2:36User personas and goals
- 3:41Building a small feature
- 5:28User personas in action
- 6:53Design collaboration process
- 7:59Engineering perspective on alert editor
- 9:24Problem with prop drilling
- 10:49Context API solution
- 12:12Implementing the provider pattern
- 14:59Updating state with context
- 16:47When to use context API
- 17:29Demo application and resources
- 18:12Key takeaways
- 18:34Closing remarks and quote
- 18:58Q&A session
related talks
39mNavigating front-end architecture like a Neopian
49mScalable Best Practices for Your Development Team
28mLessons in Managing Technical Debt
31mReact on Rails
26mEmpathy-Driven Development
21mMigrating critical apps to React
19mPivoting to React, at scale
26mFrontend At Scale - Experiences Using React In A Large Organization