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.
The next example focuses on …
Team Summit agenda planning (Event grid)
Our recent team-working pattern has been to intersperse working-from-home (as a Method Grid connected team) with – as the pandemic situation has allowed(!) – monthly team summits: intense two days-two nights physical gatherings – to hatch new plans, innovate new features, socially catch-up and generally energy-rejuvenate.
There is always a host of stuff to cram into such agendas and – of course – these agenda ideas are being created and shuffled right up to the event start itself.
Need we ask you how we best coordinate these sessions?
You guessed it.
A grid is effectively the event days (stage/columns) broken down into the main working blocks (themes/rows) with assigned elements to agenda topics/sessions. Summit events are then pre-planned but this flexible grid allows us to constantly review and re-configure the sessions (drag-drop element-modules) as we go.
This is somewhat of a side-bar use case but a really helpful one nonetheless for any such event planning and delivery coordination.
So there you have it.
Another example of a use case scenario.
We are clearly at the more mature end of solution use (indeed, we were the platform’s first ever users!) but, hopefully, this series gives a flavour of the breadth of benefits that can be derived once the intuitive (connected team) features are fully harnessed.
Hopefully, the series has provided you with one or two new examples to take back to your own operations.
As always, we love hearing about all such innovative grids and real-world user stories so please just drop us a line if you would like to feature in a future “Art of Gridding” blog.