Research Workbench v8How It Works
This page was not opened in the Loom recording. What follows is the wording the recording did show: the legend of the Blueprint page and the v8 release note Factory posted in Slack #project-x.
Part 1
How to read a block
- 4 of 4 vendors: how many of FieldRoutes, PestPac, Briostack and GorillaDesk show this block in the public pages we read. “Close match” means only a near term.
- Not Explored: how well we know the block, on a 5-step scale: Not Explored, First Look, Vendors Compared, Plan Drafted, Full Clarity. Ivan or Thomas sets it inside the block, and the block keeps who set it and when. The 5 boxes fill up one by one. Today every block is Not Explored, set by nobody.
- FieldRoutes: {n} screens: how many FieldRoutes screenshots the research placed in this block, out of {total} from the account. Open the FieldRoutes tab to read them. The other vendors have no screens yet.
- 2 new: items from Slack, an upload or the agent. They wait in the block inbox until a person accepts them.
v8 is ready: 20 blocks rebuilt from industry research, Commercial accounts included.
- Each block opens with why it matters, then tabs: Our CRM first, then FieldRoutes, PestPac, Briostack, GorillaDesk. Our CRM also has its own page across all blocks.
- Scale of 5, Not Explored to Full Clarity; a person sets it, with who and when. All blocks are Not Explored now. I read "assignable by a person" this way; say if you meant a block owner.
- 2 stakeholder reviews first: 10 of 11 blocking findings fixed; 1 partly (Our CRM is the first tab, but not full screen on first visit).
One action: post your 19 FieldRoutes screenshots here. ServSuite's site refuses access, so that vendor is thin.
Part 2
Where a block is stored
Not shown in the Loom recording. Block pages link here as “How it works, part 2”.