Model the operation first
Events, units, staffing and stock are the core planning domains. Pitches belong to events and connect to units.
VendorHQ
A connected model for festival events, units, staffing and stock, designed around roles and real operations.
Planning and design only. This is not a shipped product, delivered client outcome or working application demonstration. The visual is a proposed conceptual model.
The starting pointThe problem
The problem
behind the idea.
Festival vendor operations span events, pitches, units, staff and stock. Treating those as disconnected lists makes coordination and responsibility harder to manage.
The planned rebuild starts with the operating model and relationships, then designs appropriate roles and views for the people doing the work.
Make the connections useful.
Design around responsibility
Role-aware access is part of the design, from the owner and event manager to unit leads and crew.
Make the relationships useful
Shared records are intended to support clearer views and reduce disconnected operational lists.
Current status
Still taking shape.
The operating model and interface direction are taking shape. Application development is the next phase.
What this could mean for youA useful principle.
A useful principle.
Applied to your business.
Start with the records and the work around them. Then choose the interfaces, automation and reporting that make the next step easier for your team.
Talk about your own workflowA useful first conversationBring us the
Bring us the
messy bit.
Tell Adam what takes too long, what keeps going wrong, or what you wish your systems could do.
Let’s make sense of it adam@dicekey.co.ukSmall fixes welcome. Bigger ideas too.