How to do shaping Datopian style: a guide to better shaping analysis

[olayway]

How to do Shaping Datopian Style?

Background: https://lifeitself.org/tao/shapeup

## Situation

What's the current situtation:

- facts, objective truths about the current situation
- shouldn't include opinions on it (this should be part of the "Problem" section)
- shouldn't include consideration of the potential problem (this should be part of the "Problem" section)
- can also include facts about what is not working if this info is *factual*  e.g. we have had 3 reports that X button is confusing

Example:

Currently, URLs with spaces are encoded as %20.

## Problem & Opportunity

What's problematic about the current situation OR just how the current situation could be improved.

Example:

The %20 encoding for spaces in URLs makes them less readable and can negatively impact user experience (compared to e.g. + encoding).

## Solution

How to solve the above problem:

- general solution idea
- followed by implementation analysis
  - should show that you know HOW to solve the problem **within in our application**
  - can include pseudo-code
  - can include mermaid graphs / excalidraw sketches showing 
  - doesn't require production-ready code pieces
  - should address obvious risks/obstacles

Example:

Solution: Replace `%20` encoding with `+` encoding.

{Details related to implementation after you've analysed the code a bit and have a rough idea of how to solve the problem}

## Appetite

How long you think the implementation will take

## Rabbit-holes

Possible **unadressed** obstacles, time-burners or unanswered questions:

- things that are put here may end up being moved to solution or no-goes after being analysed a bit
- it's about flagging *risks* that could absorb a lot of time

## No-goes

We definitely don't want to go there:

- items that go here could be e.g. rabbit holes that you have decided are not worth resolving and so you moved them here
- things that came up to your mind that may be related to the problem, but are not really within the scope of the issue
- bigger things that definitely require shaping on its own

## Appendix

(Optional, if you have some detailed analysis or extra information, attachements)

[rufuspollock]

Very useful post about tools for shaping from originator of shaping idea:

https://www.feltpresence.com/small-tools-for-shaping/