Workflow

Once the DAO has been opted into receiving a GitBook, it is helpful to join their discord for further coordination.

The first interview will be two hours long and should involve the domain experts. Feel free to move around the time in the calendar and add the invitees to the meeting. You can use lettucemeet to agree on and schedule the interviews.

The second interview, for review, should be with someone who is either new to the organization and project or another expert. You can also use lettucemeet to set up a meeting with them.

  1. 1.
    Review the existing documentation of the project (GitBook, Notion, etc.)
  2. 2.
    Get a sense of general familiarization with their products and mission through Google, website, blog, etc
  3. 3.
    Collect all information into a Notion page for the project

During the call:
  1. 1.
    At the beginning explain goal/value with gitbook examples
  2. 2.
    Have them describe their workflow
  3. 3.
    Follow the SkillsInterview protocol in the Interview Guide to:
    • Decide on the granularity of the skill breakdown. More granular steps result in higher educational quality of the onboarding document.
    • Gather granular information about the day-to-day workflow and recurring tasks
    • Gather information about tools, logins, and general onboarding processes
    • Gather information about compensation and how to get paid
    • Gather information about the process to get started in the role and internal coordination

Move notes from miro into GitBook. Make sure to utilize our pre-existing GitBooks as a reference for how to structure your menu and pages. For the first GitBook, focus on only one skill and make sure to create links between our pages and any applicable existing material they have.
Important elements for the first draft:
  • An introduction to the DAO
  • A Quick Start Guide
  • A page about how to get paid
  • A brief description of the role
  • The workflow with a skill breakdown

Roles should be broken down into granular, delegatable skills. Under the role’s workflow, break down each separate skill discussed in the Skills Interview.
Each skill should have a deliverable that can be expected at the end. You can use this page as an example! Each skill, such as “DraftReview” below, has a short title with an extended explaination and a breakdown of the individual steps. Skills are chunked by their deliverables. When breaking down a skill, ask yourself if you were new to the role, would you feel overwhelmed? If so, you might need to break it down into more than one skill.
Optimize skill description for:
  • Learning - If the team needs new contributors to learn a lot, the breakdown might require higher granularity.
  • Individual progressions - If there are many skills in the organization, it’s important to see the skill in context to the others to help an individual understand how they up-skill and progress.
  • Hiring - If the organization needs to hire more workers, focus on information that will help them screen the candidates.
  • Scope definition - To communicate internally how deep/complex a role is.
  • Task split - The individual tasks should make it easy to split the work between two individuals. One of them will be the leader, the other one a student.

The second interview should be helpful to review your work and get an external opinion.
  1. 1.
    Have them share their screen so you can see where they are looking
  2. 2.
    Have the expert walk through the GitBook as if they were a new hire and provide commentary on what they notice.
  3. 3.
    Ask questions throughout about whether anything is missing and if everything included seems helpful.
  4. 4.
    Afterward, ask for honest feedback and any areas of improvement
  5. 5.
    Follow the DraftReview protocol in the Interview Guide
  6. 6.
    Take plenty of notes in Miro, which can then be integrated into the second GitBook iteration.

  1. 1.
    Move notes from Miro into GitBook
  2. 2.
    Integrate any new feedback
  3. 3.
    Create the final version with any finishing touches
  4. 4.
    Double-check all links

  • If the DAO has added us to their GitBook, simply notify the DAO that the finished version has been completed.
  • If the GitBook has been worked on through the DeepSkills Gitbook, sync with GitHub and notify the DAO that they can now transfer the information to their own. Walk them through the following process to successfully integrate the new pages with their existing documentation.
After you handed over the GitBook, signal to everyone that you completed the project by filling out this Typeform.
Copy link
On this page
Schedule - Arrange and schedule skill interviews
Research - Research existing information
SkillsInterview - Conduct an interview with domain expert(s)
FirstDraft - Create first version of the GitBook
DraftReview - Run additional interview or user test
SecondDraft - Refine the GitBook
Handover - Deliver the Gitbook to the DAO