As described in the first blog of this series, from our earliest days here at Method Grid HQ, we recognised that the more we used our own solution (took our own medicine) the better we would understand the feedback we received from our user community.
It is probably fair to say in the early days that this was a somewhat forced, contrived behaviour i.e. we were using the solution to handle aspects it was not optimised for. Now, however, we can hand-on-heart say that we would really struggle to run our business – and connect our team – without own own application at the heart of it.
In this Art of Gridding blog series, therefore, the aim is to describe the multiple ways we use the solution – with the hope that it initiates further ideas as to how you can derive even greater value from your own accounts.
How we use Method Grid …. here at Method Grid HQ
By way of summary – we use Method Grid for (at least) the following:
- To deliver structured service methods/projects to our clients (Methodology playbooks)
- As a (connected team) weekly task progress list (Kanban board)
- To coordinate our fortnightly product development sprints (Kanban board)
- To capture our ideas (and bug fixes) (Kanban board)
- Strategic plan prioritisation and allocation (Prioritisation matrix)
- Staff Induction (Induction playbook)
- Team Summit agenda planning (Event grid)
- Sales Playbook (Capability playbook)
- Repetitive monthly process (e.g. month-end financial close) (Procedural elements)
- Marketing Initiatives (Kanban board)
You can read the previous example blogs via the links above.
This blog post focuses on the next two examples …
04 To capture our ideas (and bug fixes) (Kanban board)
Another Kanban board type adaption that we harness is a grid for all of those brilliant ideas we receive from our user community (new feature suggestions etc.) and all those annoying bug-glitch fixes that accumulate with any developed product.
The best place to hold all of these for constant review and prioritisation re-ordering?
You’ve guessed it.
Our “Ideas and Bugs” grid.
Each element can capture a wealth of information and resource on a specific idea or bug; with regular team discussion, these elements are drag-dropped to our current assessment of priority order. Visual ownership and bespoke element labelling further helps with the sense of future task categorisation.