📗
Processes
  • Intro
  • Getting Started
    • Your first day
    • General work ethic
    • Important contacts
    • Important Links
    • Team Communication
    • Remote work code of conduct
  • Product processes
    • Roles & Responsibilities
    • Meeting Structure
      • 1:1 Meetings
      • Design Kick-Off
      • Design Review
      • Dev Kick-Off
      • Estimation Meeting
    • How to Introduce a Feature
    • Writing Effective User Stories
    • Writing a Design Overview
    • Prioritization (with RICE)
    • How to roughly estimate as PM & Designer
    • Design Sprints
      • Setup/ Preparations
      • Monday
      • Tuesday
      • Wednesday
      • Thursday
      • Friday
      • Sprint Decision Making Process
      • Recruiting customers for Friday's interviews
    • Project Management - Product, Dev and Design
    • Definition of Ready (for development)
  • Stakeholder requests
  • Submit a Bug Report or Feature Request
  • Data Protection: User Deletion Requests
  • Testing structure
    • Testing mobile
    • Manual Regression Tests
  • Technology
    • Development Process
Powered by GitBook
On this page
  • Basics
  • Goal

Was this helpful?

  1. Product processes
  2. Meeting Structure

Design Kick-Off

The goal of design kick-offs is to introduce a new feature and changes to user journeys to the product design team. During the meeting, they have the opportunity to ask questions to understand the issue better and to challenge assumptions & motivation. Additionally, the weekly kick-off is used to prioritize design tasks and plan the design roadmap for the upcoming week.

Basics

Frequency: Weekly on Mondays 9am (in urgent cases ad-hoc)

Duration: 45 - 60 minutes

Participants: PMs, Designers

Goal

1. Review last week's design roadmap items

  • Check the status & priority of tasks

  • Inform about changing product priorities

2. Introduce new features

  • Inform about upcoming product features:

    1. Which screen(s) are affected

    2. User journey changes

    3. The motivation for the changes

    4. Assumption tests completed

    5. To-Dos & Deadlines

  • Designers challenge assumption/ proposed soluion

3. Prioritize this week’s design roadmap

  • Re-organize open tasks according to prios

  • Add new tasks into pipeline with priority

  • Set-up review meetings for designs and agree on deadlines

  • Plan user testing for designs/ assumptions (if applicable)

Previous1:1 MeetingsNextDesign Review

Last updated 4 years ago

Was this helpful?