Deep Skills Internal
  • Welcome to Deep Skills
  • Deep Skills Organization
    • Quick Start Guide
    • About Deep Skills
      • Meetings & Workshops
        • 1:1 Meetings
        • Alignment and delegation
        • User journey
        • Presentation or landing page
        • Retrospective
      • Discord Server
  • Working at Deep Skills
    • Project-based work
      • General Etiquette
      • Roles & Responsibilities
        • Director
        • Expert
        • Contributor
        • Shadower
    • Getting Paid
      • Contributor Agreement
  • Skills and roles
    • Consultancy
      • Project owner
        • Workflow
          • Preparation
          • Consultation Call
          • Proposal Process
          • Payment Process
          • Retrospective
      • Data Steward
        • Workflow
          • Skills Interview Guide
      • DAO Steward
        • Workflow
          • Project Scoping Workshop
          • Retrospective Workshop
    • Operations
      • Operations Steward
        • Workflow
    • Engineering
      • Engineering PM
        • Workflow
      • Backend
        • Workflow
      • Frontend
      • DevOps
        • Workflow
      • Quality Assurance
        • Workflow
          • Project Testing
      • Solutions Architect
        • Workflow
    • Finance
      • Finance Director
    • Creating a new project →
      • Create a discrete project
        • Complete a discrete project
      • Create a recurring project
        • Complete a recurring project
      • Create a long-term project
  • Tools & Resources
    • Knowledge & Learning
    • Feedback
    • Historiography
Powered by GitBook
On this page
  • Feedback your buddy
  • Brainstorm positives and negatives
  • Read out positives
  • Read out negatives
  • Brainstorm solutions
  • Vote
  • Delegate
  • Implement Results

Was this helpful?

  1. Skills and roles
  2. Consultancy
  3. DAO Steward
  4. Workflow

Retrospective Workshop

PreviousProject Scoping WorkshopNextOperations

Last updated 2 years ago

Was this helpful?

After each cycle of workshops/prototyping/user testing, we run a short 1-hour retrospective to reflect on our experience and evaluate how to improve. It follows are very simple process:

  • Write down all positives and negatives (7 minutes)

  • Readout all positives individually (1 minute each)

  • Readout all negatives individually (1 minute each)

  • Vote on negatives (3 minutes)

  • Brainstorm solutions for negatives (7 minutes)

  • Vote on solutions (3 minutes)

  • Discuss feasibility and delegate

You can find a Miro board with most Retrospectives here:

A Retrospective Workshop is a great chance to experiment with facilitation techniques, new music or tools alternative to Miro.

Feedback your buddy

Before going into the Retrospective on the project, it's important that Experts leave their Collaborator some personal feedback with . If you like, .

After everyone is done, start the retrospective and focus on only the challenges within the sprint. Any interpersonal discrepancies or confrontations should be discussed afterwards in private.

Brainstorm positives and negatives

Duration: 10min

Ask everyone to write down everything that stood out as positive (green notes) and everything you think that can be improved (red notes).

Read out positives

Duration: 5-10min

Let each participant read out the positives and provide a bit of context.

Read out negatives

Duration: 5-10min

Let each participant read out their negatives and clarify what they mean.

Brainstorm solutions

Duration: 7min

Ask everyone to read through the negatives and place solution notes (blue) underneath in silence.

Vote

Duration: 7min

Without discussion, ask all participants to read through the notes and place 5 dots on their favourite solutions.

Delegate

Duration: 10min

For the clearly actionable steps, delegate the work to the Creative Directors, Experts or set up as community bounties. In difficult cases suggest improvements, create a governance proposal or reach out to the Creative Directors to help solve the problem.

Implement Results

Once the project is complete, it is up to the Creative Director to spend up to two hours implementing any changes that need to be made in order to improve the process. Please reach out to the department representative to make the changes or .

It's important that after each change you fill out to let everyone else know.

https://miro.com/app/board/o9J_lfNSlU4=/
this Typeform
you can also review anyone on the project
refer to this guide
this typeform
(you can also use the built-in Miro voting for this)