Claude Cowork Tutorial from Cowork's Design Lead

Wen describes a flexible workday spent across several projects, often reviewing working prototypes with engineers and product teammates. She still uses Figma for polish, but specs and planning documents are usually brief, with prioritization captured in a few bullet points.

Wen uses Cowork for most tasks, reserving Claude Code for detailed production code work. She demonstrates gathering themes from interview transcripts, social media, Reddit, and reviews, then producing a presentation and feature ideas in parallel. She suggests scheduling this process for Mondays at 10 a.m. to help the team start the week with insights and options.

Wen asks Cowork to draft wireframe options for a step-by-step progress interface, then describes taking a promising direction into Figma or code for iteration. The team can use the resulting insights and artifacts as a shared starting point, while people contribute prototypes and ideas. She emphasizes that people still need to judge and curate what to build.

Wen says Cowork grew from a year of prototypes and technical experiments, although the decision to ship came together in a 10-day sprint. Increased use of Claude Code for nontechnical tasks suggested demand for an agent product aimed at knowledge workers. Earlier Cowork designs felt too structured, so the shipped interface moved toward chat and a shared task list.

Wen describes monthly planning with a short list of priority projects, each assigned a directly responsible individual, alongside looser quarterly or half-year direction setting. She says useful visions now cover roughly three to six months and can take the form of prototypes that help teams align. Her advice to designers is to adapt as tools and roles change, taking inspiration from engineers who have already adjusted their work.