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
  • When to do it?
  • How to do it?
  • Whiteboard template

Was this helpful?

  1. Deep Skills Organization
  2. About Deep Skills
  3. Meetings & Workshops

Retrospective

When to do it?

A retrospective workshop should ideally conclude a project. It helps the team to improve together and constantly iterate on internal processes. Joining the retrospective is not mandatory, but obviously helps everyone improve and learn from mistakes.

How to do it?

Total duration: 1:30 hours

Brainstorm positives and negatives

Duration: 10min

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

Read positives

Duration: 5-10min

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

Read 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 five dots on their favorite solutions.

Delegate

Duration: 10min

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

Whiteboard template

PreviousPresentation or landing pageNextDiscord Server

Last updated 3 years ago

Was this helpful?