Atlas Flow
A collaboration tool for planning, handoff, and progress tracking across product and engineering teams.
Role
Full-stack contributor
Stack
React, API design, MDX, Workflow UI
Problem
The team needed a shared planning surface that felt simple for new users but still supported power-user workflows.
Problem
The team needed a shared planning surface that felt simple for new users but still supported power-user workflows.
Constraints
- The product had to support both lightweight viewing and deeper project editing.
- Content needed to be editable without touching component code.
- The UI needed clear states for handoff, review, and completion.
Approach
Used a file-based content model to keep page copy, workflows, and metadata aligned.
Separated overview content from the interactive planning surface.
Focused on route-level clarity so each page had one obvious job.
Technical decisions
Modeled content as structured fields so the site could grow without a CMS.
Designed the hierarchy to work as both a fast overview and a deeper reading experience.
Kept the shell simple so future project types could share the same layout.
Outcomes
Reduced ambiguity with clearer ownership and handoff states.
Made route structure easier to understand for both quick scans and deep dives.
Kept content and interface structure aligned through typed models.
Problem
The team needed one place to track planning, handoff, and delivery without forcing everyone into a heavy or confusing workflow.
Approach
I kept the product split into a lightweight overview and a deeper working surface. A file-based content model made it easy to keep page copy, workflows, and metadata aligned.
Outcome
The result was a product that was easier to scan and easier to grow. The route structure stayed clear, and the content model made future updates more predictable.