---
created: {{date:YYYY-MMM-DD}}
alias: {{Title}}
tags: "#doc"
---

# Write ticket guideline

## How to write a ticket that anyone to understand

Everything is based on the question of Why, How, What, then iteration of the question. When writing the brief, we should follow up on the structure as a reference to what we want to communicate with each other.

Other people expect that they would get the information of the section (eg. How) quickly. So they would like to recognize it soon as possible. If don't, they don't understand it and don't willing to continue reading.

This is a sample template of sections designed to use:


# Strategic space

> Biz Needs or User Needs

## What

## Why

## Expectation

# Opportunity Space

> As Biz HMW or As Users HMW questions

## Context

## Problem

## How might we

## Solution picked

# Solution space

> Solve problem for Biz or Solve problem for Users

## How

## Resource

# Additional space

## Who

## When

## Where

---

# Approad types

## Approad Canvas

- [Biz Modal Canvas](https://railsware.com/blog/business-model-canvas/) - Biz based
- [Lean Canvas](https://railsware.com/blog/lean-canvas-a-tool-your-startup-needs-instead-of-a-business-plan/) - User based

## Approad Matix

| Space | Biz | HMW | User |
| ------------ | --- | --- | ---- |
| Strategic | - | - | - |
| Opporturnity | | | |
| Solution | | | |
| Additional | | | |

## Approad Biz based

1. Define Biz model
2. Generate solution
3. Apply to User needs

flowchart LR  
    id1(Biz) --> id2[[HMW]]
    id2 --> id3(User)

## Approad User bized

1. Define User
2. Generate solution
3. Establish to Biz model

flowchart LR  
    id1(User) --> id2[[HMW]]
    id2 --> id3(Biz)