27d • Requests
How to request something, and how it gets built
This system grows out of real work. Mine, and from here on yours too.
The honest limit: my Brain improves because I use it every working day on client work. Your work is different. I cannot properly test a playbook for a job I do not do. So requests here get built together with the person who asked for them.
How to post a request. Answer these four things:
What task costs you the most time?
How often does it come up?
What do you do now, step by step?
What should the system hand you when it is done?
Why four questions instead of a wish list: a wish is hard to build. A description of your actual steps is already most of a playbook.
What happens next. Three people asking for the same thing is a pattern, and patterns get built. One person asking gets a real answer in the thread on how to do it in your own setup, and the request stays on the counter. Most requests turn out to be a variant of something that already exists, and then it is a small change that can be in the next release.
The deal: if you ask, you test. I write the first draft, you run it on your real work and tell me what actually happened. Two or three rounds and it is done, and then it goes to everyone in the monthly release.
Built something yourself that works? Send it in. If it goes into the core system, your name is on it.
Small requests are welcome. They are usually the ones that get built first.
0
0 comments
How to request something, and how it gets built
