What changed
A large technology driven firm partnered with designers to tailor a new set of flow oriented tools intended to support the lead up to a major fashion event. The effort was not about a standalone product but about shaping a sequence of steps, approvals, and asset sharing to fit the shows calendar. The aim was to convert a complex set of cross team tasks into a clear, repeatable workflow. Designers, producers and operations staff participated directly in shaping how information moves from idea through to execution, with an emphasis on practical usefulness over novelty.
The result was a customised toolkit that reflects the unique tempo of a fashion week cycle. It was built around real world needs rather than generic templates, ensuring that creative decisions, styling notes, and production queries could be tracked in one place. The approach demonstrates how a collaboration between technology specialists and creative practitioners can deliver tooling that supports everyday work rather than adding to it. For SMEs this case shows a replicable method for turning bespoke event level planning into normal business operations.
Although the event in question was high profile and well resourced, the principle is transferable to SME operations. By engaging staff from design oriented roles alongside operations and IT, teams can shape simple tool sets that address their own workflows. The key is to start with the tasks that most often trip people up and then build a small set of features that remove friction, rather than chasing a fully featured system.
Why it matters for UK and Wales SME teams
SME teams across trades, professional services and local operations deal with multi step workflows that involve input from several roles. When these flows stall or break due to missing information or mis aligned handoffs, customer requests slip and response times lengthen. The example shows that introducing a purpose built flow can align creative intent with practical execution. For small teams, this means a clearer handoff between designers, sales and operations and a single place to track due dates and decisions.
Start with what exists rather than what is imagined. Use the idea of a customised event toolkit to adapt your own processes. Map one service line or product family from inquiry to delivery, assign owners, and keep the scope tight. The investment can be modest if you reuse existing software and rely on staff who already understand the workflows. The payoff is improved collaboration, fewer duplicated requests and better visibility into what is pending.
Beyond speed, such tooling can reduce errors and rework by enforcing standard steps, checklists and approvals. This matters in professional services where proposals and contracts must move between teams; in trades where site preparation, procurement and scheduling must align; and in support where escalation paths become clear. Even small teams can gain from a clear end to end process that everyone can see and follow, with a simple audit trail for accountability.
Constraints and trade offs
There are limits to this approach. Customising tools for one event means developing capabilities that may not fit another context exactly. Small firms should beware of depending on a single external tool for mission critical tasks because a vendor may change services or pricing. Integration with existing systems matters; without it, information flows feel disjointed and staff adopt parallel workarounds. Cost is another constraint; the time spent designing a workflow should be matched by measurable gains in productivity.
Data handling and security must be considered. When teams rely on external cloud based tooling for sensitive information it is essential to set governance, define owners and ensure data retention aligns with policy. The risk of lock in means teams should build in escape routes such as exporting data and using widely supported formats. Finally, diversification of tools helps avoid single point of failure and keeps options open if the initial approach needs adjustment.
What usually goes wrong
Change management is frequently underestimated. Teams may slide into adopting new tools without clear purpose, and staff may resist changes if training or ongoing support is lacking. Without explicit governance and routine touch points, the tool can drift away from the real work and become clutter. Managers should ensure that the proposed toolkit maps to real tasks, not creative fantasies, and that front line staff have a say in how the workflows operate.
Technical challenges also appear. Data migration between old and new systems can create gaps in knowledge and delays. Without documented processes and owners, it is easy for tasks to fall through the cracks. Early pilots with a small team will reveal practical issues with data formatting and permissions. Organisations must plan for ongoing training and simple updates and avoid making the tool a black box that only a handful understand.
What to do this week
Begin with a quick assessment of current workflows. Pick a service line where delays or errors are most common and outline the end to end process from inquiry to delivery. Identify the roles involved and the information that must move between them. This week you should capture the steps as a simple checklist and keep the scope small to avoid overload. A clear end to end view will help you decide what to change first and who should lead the effort.
Map the top three repetitive tasks that cause friction for staff and customers alike. Decide if these tasks can be simplified with a shared checklist, a standard email template or a basic automation rule. Involve sales and operations in this mapping to ensure that the handoffs are practical and that the information needed to proceed is openly available. After you choose a target area, assign an owner and a due date for the first improvements and set expectations for measurement.
Run a one week pilot using one existing tool to support the chosen end to end flow. Create a simple guide that explains who approves what and where data flows. Collect feedback from front line staff to capture wins and pain points. At the end of the week, review the outcomes with the team and decide if the approach should be scaled. Keep a log of issues and suggested tweaks so you are ready for the next iteration.
- Audit current workflows and identify a single end to end process to fix
- Map data flows across teams to reduce friction
- Assign owners to each step to ensure accountability
- Use existing tools to build a simple end to end flow with clear steps
- Run a one week pilot and gather feedback
- Establish a lightweight governance rule for data and changes
Start small with one end to end flow and build from there this approach keeps risk low and momentum high.