A substantial part of my operational plan is about giving the team a workable structure. People need to understand the work they are responsible for, have enough capacity to carry it out and be able to develop the skills the business needs.
I brought employee maximums, improvement programmes and cross-department servicing together because they affect the same working week. Adding a responsibility to someone’s role changes their capacity. Training someone to support another department also needs time and a clear understanding of what they will take on.
What I mean by an employee maximum
An employee maximum is the amount of work a person can realistically carry across the tasks or services assigned to them. In the plan, I use it as a capacity limit for planning active projects and recurring client work.
A simple client count can be misleading. A recurring SEO service, a website build, content population and client communication make different demands on a person’s time. The plan includes a capacity model based on the time required to deliver each service, so that the workload can be considered in relation to the actual work.
I want operations and project or account managers to agree those limits together. They need to consider the person’s regular working schedule, the commitments already in place and the demands of the services being assigned. The assumptions in a planning table need to be checked against what delivery actually takes.
This gives a project manager something useful to work with before another project is allocated. It also gives the team a way to explain that capacity is reaching its limit while there is still time to make a decision.
Knowing when capacity needs to increase
The plan connects a department reaching its maximum with a decision about additional capacity. Hiring or adding resource should have a recognisable trigger, supported by operations and the people managing the work. That makes the conversation more concrete than waiting until everyone is struggling to keep up.
Budget-overreach thresholds form another part of that structure. Project and account managers, with directors where needed, should know when a budget requires review. We need to look at the work already delivered, the work remaining and the reasons time has moved beyond the original plan.
Capacity and budget information belong together. Asking an already full team to absorb more work can conceal the cost of delivery. Equally, a budget problem may reveal a scope or estimating problem that another employee would not solve. I want the information to help us identify which decision is needed.
An improvement programme with room to progress
My employee improvement programme is concerned with people being happy in their roles and progressing in their careers. I proposed individual development plans aligned with business objectives, with operations and team leads helping to identify the skills that would make a useful difference.
One example in the plan is training development staff to support SEO analytics tracking. That gives an employee a clear capability to work towards and creates another route for the business to deliver a necessary task. The development plan needs to explain how that skill will be learned and where it will be used.
Recognition is part of the programme too. I proposed a team stand-up that highlights people’s strongest contributions, with a £100 voucher awarded every two months. The aim is to make good work visible across the business and give people an opportunity to explain something they are proud of.
I also connected development to ownership of improvements. A team member can become the champion for a business issue, work through an approach and help implement it. That creates a practical opportunity to progress while contributing to an agreed company goal.
Training between departments
The plan asks departments to understand one another’s responsibilities, pressures and workflows. For a small team, that understanding matters when work needs to be shared. Development needs to understand why SEO carries out a task before trying to automate it or take part of it on.
I used an overloaded SEO team as an example. Some responsibilities might be supported by development or project management, provided the people involved have the knowledge and available time. The useful question is which tasks can be transferred or shared, and what preparation would make that safe and effective.
Cross-team training gives those arrangements a foundation. It allows us to identify a specific task, agree who could support it and put the necessary learning in place. The additional responsibility also has to appear in the receiving person’s schedule so that it can be considered alongside their existing work.
Clear roles when a service crosses departments
Cross-department servicing is about more than covering a busy week. SEO can identify an improvement to a client’s website which development then implements. Development can also help with the technical setup that SEO needs to carry out its work.
Those relationships need clearly defined roles. People should understand the responsibilities and capabilities around them, including who owns the next action. Team leads have a part in making that clear, especially when a task moves from advice or analysis into implementation.
I want that understanding to sit in the documented workflow. It gives the person doing the work enough context to continue and gives the person handing it over a clear destination. It also makes the relationship easier to explain when someone joins the team.
Giving the team a voice in operations
The wider plan provides fortnightly team-lead meetings and a monthly route for decisions to reach directors. Staff knowledge needs to inform those conversations. The people carrying out a process are well placed to explain where time is being lost or a handover is unclear.
Once a change is agreed, a champion and the relevant team lead can take responsibility for putting it into practice. I want team operations to make that path understandable: raise an issue, decide what needs to change, assign the work and return to it to see how it is progressing.
The capacity limits, development plans and shared services all support that approach. They give us a way to organise the work while taking people’s time and progression seriously. As the plan is implemented, I want the team to be able to recognise where it is helping and tell us where the structure needs another adjustment.