Coordinate launches, reviews, meetings, and team availability in a weekly view with enough project context to avoid collisions. The screen connects Calendar and My schedule so product teams can find the “Add event” action while checking events this week and conflicts.
Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Roadmap review and Design critique, rather than an empty visual shell.
Calendar
Add event
Calendar
Default, loading, empty, error, permission, success
Adaptable product UI theme
Product teams need a clear “Add event” action without losing sight of events this week, conflicts and the affected records. Keep the decision and its outcome clear before moving to the next task.
Calendar → My schedule → Add event → Review outcome
Calendar, Calendar, My schedule, Team, accessible states, contextual actions
Show timezone, time range and conflicts before a user commits. Offer a clear path back to available slots.
In this design, people should be able to compare Roadmap review with Design critique. Make events this week clear, then use conflicts to explain whether the next step needs attention.
Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Add event” action. The happy path alone is not enough.
Related UI examples: Product Roadmap, Docs Workspace, Sprint Planning.
Design a team calendar screen for our existing software product. Use our real design-system tokens, components and product language. Show Calendar and My schedule, include believable records such as Roadmap review, and make add event easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.