Wanted to show you something Nitwyt's been up to... 🤯
I recorded a quick tour (about two minutes) of the boards we run everything on now.
Here's the short version:
Every single piece of work that needs to get done has it's own task.
A task is a "card" that is active and on the board.
The card says what it is, whose move it is, and when it closes...
When I want Nitwyt to do something, I drag the card into a column called Ask Nitwyt and ping the system from the IDE.
It picks the card up, does the work, and answers me in the card's comments.
(That's the part I want you to catch. I'm not sitting in a chat window typing prompts!)
The human is OUTSIDE the loop... not in the loop.
The work is organized around the cards, not around me.
There's even a card that explains the board's own rules to me - written by Nitwyt, with Nitwyt constantly double-checking as it self-corrects to be sure it's on track to produce whatever the card is there to produce.
This is what I mean when I say automated organization...
The tour only shows my control board (I call it the Operator Desk).
There's more behind it...
Client work, products being built, whole other rooms with completely different functions.
Happy to show more of the backend if you want it...
Say so in the comments and I'll record the next piece.
Questions welcome!
(That's what this space is for.) 😁