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
  • General principles and etiquette
  • Structure
  • Facilitation
  • Note-taking
  • Prioritizing
  • Delegating tasks
  • Sharing results

Was this helpful?

  1. Deep Skills Organization
  2. About Deep Skills

Meetings & Workshops

We we try to optimise the value of each conversation by running structured workshops instead of meetings

PreviousAbout Deep SkillsNext1:1 Meetings

Last updated 3 years ago

Was this helpful?

General principles and etiquette

Use if you would like to easily create a calendar event from a template.

Every participant in a workshop should be familiar with at least the following principles:

Structure

Each workshop has a predefined structure which should be evident from the agenda on the calendar invite. Ideally, it should include timings so participants know what to expect and when.

Facilitation

There is always one facilitator who can keep track of time, especially during heated discussions. They should be familiar with workshop processes and this documentation.

Note-taking

Everyone is a note-taker. Whenever you hear someone say something that resonates with you, write it on a post-it. If it's a challenge or something that needs to be resolved collaboratively, write it as a How-might-we (HMW) and leave it on the canvas with other HMWs.

Prioritizing

Use circular shapes on the whiteboard to vote on a set of notes. This can be HMWs, ideas, solutions, screenshots, or concepts. Usually, it's enough to give every participant four or five "votes" to select their favorite ideas.

By prioritizing with votes, you will always make sure that if time runs out, at least the most important decisions have been made and worked on. Everything else can be revisited at a later point in time, as priorities always change.

Delegating tasks

At the end of each workshop, aim for clear updates and delegations of work. Everyone on the team is responsible for their own work and keeping track of it. Attach names of workshop attendees to make it clear who is working on what.

Sharing results

After each workshop, someone (ideally the facilitator) should share the results and outcomes with everyone. You can screenshot the relevant area and provide context on the decisions the team has made.

this Typeform