9d • Posts
How to integrate your systems with your goals (GRAFTS + QUESTS)
Most companies just do.... whatever.
They just run around, decidin to do a thousand things, and the founder is multitasking.
This is why we use GRAFTS. To laser target the few blockers and suggest a specific project or new policy change to achieve that.
And Pic related, these problems come from root causes. So we go as DEEP AS POSSIBLE to figure out ALL of the problems for the 1-5 main high level bottleneck breaking outcomes we decide we want, and come up with projects for the quarter.
We want to neutralize bad conditions. Red to Green. Off track to On Track.
But after the project and steps and tasks are done, then what? Find the next project and the next? This is the problem every client/community/owner faces. They spent weeks or months on a project, launched it, and then they either get stuck maintaining it... doing the misc junk drawer type of tasks to fix a system, and this capacity of time gets sucked up... They can't focus entirely on problem solving.
So how do we solve this?
GRAFTS figure out the project/policy to fix problems, and QUESTS is the solution stack to fix it.
We have QUESTS come out to keep things on track.
I struggled with the longest time switching back and forth.
I would have a project be done, and it would work. It works with 100% certintiy, and it made sense. But then it would get "undone".
The rule or project worked until we stopped thinking about it. The problem got solved, so we're done, right? No. There is a maintance, or permanent sort of routine and problem solving and tracking AFTER it.
With my pirate ship analogy, just becuase you patch a hole in the ship, doesn't mean you're done. You still need to review it, make sure the nails/board don't get undone, and maybe group this work with all the other holes in the ship.
This entire batch of work is needed to run the ship (or else it sinks). We use a framework of QUESTS to manage each area's systems and processes.
This doesn't overwrite quests in progress but stays in as a maintance quest -- the easiest QUESTS to run. They are literally just made up of a recurring task to "is everything still good?". We just to add a simple row or new obeya view to monitor a specific company-breaking problem. The problem may need to be paid a lot of attention early on, but if it gets solved, it still needs to make sure it sticks. Maybe switching from a daily check to a weekly check to a monthly check, but never just "forgotten about". These checks
Basically
1) Quarterly build out a full GRAFTS tree stack. This might be 100 nodes of bad/green cause and effect. Its fully MECE of all problems until they reach their source. (Using the Goal, Reality, Assumption, Future) trees.
2) For solving the goals (At their source) we build out the GRAFTS project and it pinpoints all of the (Tasks) and (Support) that it needs to tactically be completed.
3) With a tree, we might see 100 of nodes, but maybe 1-2 clear and obvious QUESTS to implement that if implemented get a lot of specific nodes to turn from red to green, and may get the entire goal tree green. So we flesh out the GRAFTS project, and when we start to solve it, we keep track of the project using its own QUESTS obeya board.
4) Each "QUESTION" of a QUEST is simple, a simple yes or no. So these questions are really just either reflections of these GRAFTS condition nodes (e.g. if we run this quest, it makes (this) condition true). If the goal is to unbottleneck break the business, and we have a FINITE measurement of what that is, e.g. "botlteneck is -$5k/mo loss", then we know until we break the bottleneck that the quest isn't met yet. So if the project can show that they're trending to break it, its off track. Red or dark red. Whoever is the manager can decide what are the QUESTIONS. But the goal is the same, reach green and get it on track and flowing.
5) For obsessive problem monitoring, AI can track each item asap as a sort of "andon light". An andon is a light that flashes if a system, process, or machine isn't working. It alerts people when a problem MAY form also (yellow light). When the undesirable outcome is neutralized, we can update a distilled team GRAFTS tree of clickup nodes. This can be programmed, showing each node, and allowing people (and AI) to leave comments. This takes the business from COMPLEXITY to completely SOLIDIFIYING with order and certainty how the business works. In a massive company, each "node" can have an AI monitor with a simple check "is this condition or area still working", and it sums it up at the main board. This way the business can capture problems as soon as it happens, and not need to wait.
This lets us build from the bottom up, by doing only the MINIMAL amount of work to double the business. If it didn't work, then the GRAFTS tree didn't have all its nodes or the project didn't have enough of a "dose" of strength to flip cards.
I have some videos scheduled to be posted that show a huge grafts tree implementation, and I'll build one for the community as we build a final published paid-course product for the owners.
But. this unites two major frameworks in one. It was obvious to some people, and not to me.
tldr: GRAFTS finds and suggests new QUESTS to do and maintain
2
1 comment
How to integrate your systems with your goals (GRAFTS + QUESTS)
powered by
skool.com/delegate-and-elevate-1300
Get trained, certified and placed into a company as an AI Scaler
Suggested communities
Powered by