The accountable body plays a vital role in ensuring public money is managed responsibly, decisions are properly governed and funding requirements are met. For Mayoral Combined Authorities (MCAs), this responsibility becomes particularly important as funding arrangements, statutory powers and partnerships with delivery organisations evolve. The accountable body is not a new concept, local authorities have long been responsible for sound financial management, effective governance and statutory compliance. The challenge is understanding how these responsibilities fit within business as usual, where additional assurance is needed and whether existing arrangements are sufficient. Business as usual covers the organisation's ongoing operations. The accountable body function brings together the responsibilities and controls needed to demonstrate that public money and associated decisions are managed in accordance with the relevant legal, financial and governance requirements. The distinction is important because many of the activities that support accountability should already exist within the organisation. There are five areas that an effective accountable body function must get right. Clear accountability and decision making. Responsibilities, delegated authority and approval routes must be understood by everyone involved. Where an MCA administers funding or works with delivery partners, it must be clear who makes decisions, who approves expenditure and who is responsible for meeting the relevant conditions. Without this clarity, gaps and duplication can develop, leaving important decisions without clear ownership. Financial control. Appropriate arrangements must be in place to monitor budgets, authorise expenditure, maintain accurate records and demonstrate that funding is being used for its intended purpose. Controls should be proportionate to the value and risk of the funding involved, providing confidence without creating unnecessary bureaucracy. Risk management and assurance. Identifying risks is only the starting point. There must be clear ownership, effective controls and evidence that those controls are working. Leaders need to understand where assurance is strong, where gaps exist and what action is required. A completed risk register or a report confirming that a process exists does not, on its own, demonstrate that the underlying risk is being managed effectively. Compliance, audit and independent scrutiny. The authority must understand its statutory obligations, funding agreements and reporting requirements. Evidence must be retained, audit findings addressed and responsibilities between the MCA and its delivery partners clearly defined. Internal audit provides independent assurance on governance, risk management and controls, complementing the oversight undertaken by management and corporate functions. Effective oversight of delivery. Assurance must provide a meaningful view of whether funding is being managed properly and intended outcomes are being achieved. This requires reliable reporting on expenditure, progress, performance, dependencies and emerging issues. Where problems arise, there must be clear routes for escalation and corrective action. Accountability for funding should not, however, be confused with direct responsibility for managing every project or delivering every outcome. These five areas depend on assurance operating across the organisation. Operational teams must own and manage their risks and controls. Senior management and specialist functions must provide oversight and challenge. Internal audit must be able to provide independent scrutiny. Together, these arrangements should give decision makers a reliable picture of whether obligations are being met and where intervention is needed. For an MCA reviewing its operating model, the starting point should be to map existing responsibilities, processes and assurance arrangements. Finance, Legal, Governance, Procurement, Risk, Audit and Programme Management may already undertake much of the required work. The objective is to identify gaps, unclear ownership, duplication and opportunities to strengthen assurance, rather than automatically creating another team or layer of governance. The right arrangement might be a dedicated team, a coordinated function across existing departments or clearer responsibilities embedded within the current operating model. The answer depends on the authority's statutory responsibilities, funding arrangements, risk exposure and existing capabilities. Ultimately, accountability is not demonstrated simply by having policies, committees and reporting templates in place. It is demonstrated by clear responsibilities, effective controls, reliable evidence and action when things go wrong. A well designed accountable body function should provide confidence that public money is being managed responsibly while enabling the organisation to deliver its objectives. Getting that balance right is both a governance responsibility and an organisational transformation challenge.

When shaping a department, there is rarely one agreed view of how it should work. Leaders may have a clear vision for the future, managers may be focused on operational reality, and employees may have a different perspective based on what happens day to day. All of those views have value, but they will not always align. The challenge is not to find a way to make everyone agree. It is to understand the different perspectives and use them to shape a department that is fit for purpose. A restructure can quickly become a debate about reporting lines, roles and where responsibilities should sit. While these things matter, starting with the organisation chart can make it harder to see the bigger picture. The more important questions are what the department needs to deliver, what is currently getting in the way and what needs to change. Different viewpoints should therefore be tested against the same set of objectives. What does the department need to achieve? What capabilities are required? Where are there duplication, gaps or unnecessary layers? How should decisions be made? What needs to be closer to the customer, service user or frontline? These questions move the conversation away from personal preference and towards organisational need. This does not mean every view should be treated as equally valid in every circumstance. Experience and evidence matter. So does accountability. A senior leader may have responsibility for the overall direction, but that does not mean operational insight should be dismissed. Equally, an established way of working should not automatically be retained simply because people are comfortable with it. The best restructures create space for constructive challenge. People should be able to explain not only what they think should change, but why. Assumptions should be tested, evidence considered and different options explored. Sometimes the right answer will be a combination of several perspectives. Sometimes it will mean recognising that an existing approach is no longer appropriate. There is also a human element. People can interpret a restructure through the lens of their own role, team or experience. That is understandable. Clear communication about the purpose of the change can help create a shared understanding and reduce the risk of the process becoming a competition between competing interests. Ultimately, the question should not be whose idea wins. It should be whether the proposed structure enables the department to perform effectively, make good decisions and deliver what the wider organisation needs. A successful restructure brings different perspectives into the conversation without allowing individual preferences to determine the outcome. It combines leadership, evidence, operational knowledge and constructive challenge to create a structure designed around what the department needs to achieve. That is how different points of view become an asset rather than an obstacle to change.

A job description should do more than list responsibilities and requirements. It should give potential candidates a clear understanding of the role, what is expected of them and the contribution they can make. Done well, it can help attract the right people, set realistic expectations and reduce the risk of recruiting someone who is simply not suited to the role. Too often, job descriptions are written from the perspective of the organisation rather than the person being asked to apply. They can become a long list of duties, qualifications and corporate language that tells a candidate very little about what the job is really like. A good job description starts with purpose. What is the role there to achieve? The answer should be clear from the outset and should connect the position to the wider objectives of the organisation. Candidates should be able to understand why the role exists and the difference they are expected to make. Responsibilities should then explain what the person will actually do. These should be specific enough to provide clarity without creating an exhaustive list of every possible task. A job description that contains twenty or thirty responsibilities can quickly become overwhelming and may suggest that the organisation has not properly defined the role. It is equally important to distinguish between essential and desirable requirements. Asking for an unrealistic combination of qualifications, experience and technical skills can unnecessarily narrow the candidate pool. Organisations should consider what someone genuinely needs on day one and what could be developed through training, coaching and experience. The language used also matters. Excessive corporate jargon, unexplained acronyms and generic phrases such as "dynamic self starter" can make a role sound interchangeable with hundreds of others. Clear, straightforward language gives candidates a better sense of the organisation and makes the opportunity more accessible. A strong job description should also explain how the role fits within the organisation. Who does the person report to? Who will they work with? What level of responsibility will they have? Where appropriate, it can also explain the opportunities available to develop and progress. There is also a practical benefit to getting this right. A well defined role provides a stronger foundation for recruitment, interviews, onboarding and performance management. It creates consistency between what is advertised, what is discussed during the recruitment process and what the successful candidate is ultimately expected to deliver. A job description should not try to sell a role that cannot live up to its promises. The objective is not to attract as many applications as possible. It is to provide enough clarity for the right people to recognise that the opportunity could be right for them. Ultimately, the art of writing a winning job description is about clarity, honesty and purpose. Give people a realistic picture of the role, explain the contribution they can make and be clear about what really matters. The result is more than a better advert. It is a stronger starting point for the employment relationship. Checklist Define the purpose of the role clearly. Explain the contribution the role is expected to make. Keep responsibilities specific, relevant and realistic. Separate essential requirements from desirable ones. Avoid unnecessary qualifications and experience requirements. Use clear language and remove excessive corporate jargon. Explain reporting lines, relationships and level of responsibility. Describe what success in the role should look like. Be honest about the challenges as well as the opportunities. Check that the job description reflects the role that will actually be offered.

Good collaboration can make a significant difference to how teams work. It can bring different perspectives together, improve decision-making, share expertise and help organisations achieve better outcomes. But effective collaboration is not necessarily about involving more people. It is about connecting the right people at the right time, with a clear purpose and a shared outcome. When collaboration works well, people understand their role, contribute their expertise and build on the work of others. When it doesn't, processes can become more complicated, responsibilities can become blurred and work can sometimes be repeated unnecessarily. So how can organisations reduce silo working while making sure collaboration genuinely adds value? 1. Start with the outcome Before thinking about who needs to be involved, be clear about what you are trying to achieve. A shared outcome gives teams something to work towards and helps everyone understand how their contribution fits into the bigger picture. 2. Bring the right people together to encourage collaboration Effective collaboration is about having the right expertise involved — not necessarily having everyone involved. Think about who can add knowledge, insight or challenge to the task and involve them where their contribution will make a difference. Sometimes that may mean a group discussion. At other times, it may simply mean a conversation between two colleagues. 3. Make every step add value As work moves between people and teams, it is worth occasionally stepping back and looking at the process as a whole. Are we adding expertise at each stage, or are we simply repeating work that has already been done? A process can involve several people and still be collaborative, but each person's involvement should have a clear purpose. 4. Look out for unnecessary double and triple handling One of the easiest ways for a well-intentioned process to become inefficient is for the same task to be handled several times. Information may be checked, re-entered, reviewed or passed between several people, with each handover adding another opportunity for delay or misunderstanding. A useful question is: "What is the additional value being added at this stage?" If the answer is clear, the step may be necessary. If not, there may be an opportunity to simplify the process. 5. Give people clear ownership Collaboration works best when everyone knows who owns the outcome. Clear ownership does not mean working in isolation. It means there is someone responsible for moving the work forward while drawing on the expertise of others when needed. Without clear ownership, work can easily become a series of handovers rather than a coordinated effort. 6. Share information, not just tasks Breaking down silos is partly about making sure teams have access to the information they need. When information is difficult to access, people can end up recreating work, asking several colleagues for the same information or maintaining separate versions of the same information. Better information-sharing can remove some of the need for additional meetings, emails and handovers. 7. Involve expertise early Collaboration is often most valuable before work is completed rather than afterwards. If another team's expertise is likely to influence the outcome, bringing that perspective in early can prevent unnecessary rework later. This can be particularly helpful for complex pieces of work where several teams have an interest or responsibility. 8. Don't confuse communication with collaboration Keeping people informed is important, but not every communication requires a meeting, a review or an action from someone else. Ask whether people need to contribute, decide, advise or simply know. Being clear about the difference can help teams stay connected without creating unnecessary activity. 9. Look at the whole process Silo working can be difficult to spot when everyone is focused on their own part of the process. Taking a step back and mapping the journey from beginning to end can reveal where work is being duplicated, where information gets lost and where unnecessary handovers occur. The aim is to understand how the pieces fit together, rather than simply optimising each individual team's part. 10. Focus on purposeful collaboration Ultimately, the goal isn't to collaborate more for the sake of collaboration. It is to collaborate better. Good collaboration should make work clearer, more effective and more joined-up. It should bring together different skills and perspectives where they genuinely improve the outcome, while still allowing people to take ownership of the work they are responsible for. Sometimes collaboration means bringing several teams together around a complex problem. Sometimes it is a five-minute conversation that prevents hours of rework. And sometimes the best form of collaboration is knowing when another person's involvement isn't necessary. Better collaboration, not more collaboration Breaking down silos doesn't mean removing every boundary between teams. Different teams exist for good reasons, and people need clarity about their responsibilities. The opportunity is to build stronger connections between those teams while keeping processes proportionate and purposeful. More people involved does not necessarily mean more collaboration. The real measure is whether people are sharing the right information, contributing their expertise and working towards the same outcome — without creating unnecessary duplication along the way. When we get that balance right, collaboration becomes less about passing work between people and more about working together to make the work better.

A poor decision rarely ends with the decision itself. The real cost is often what follows. In any organisation, decisions have consequences. Some are financial, some operational and others affect people, customers, reputation or future opportunities. The difficulty is that the impact of a poor decision is not always visible at the point it is made. It can take weeks or months before the consequences become clear. Not every decision will be right. Organisations operate with incomplete information, changing circumstances and competing priorities. Good decision making is therefore not about guaranteeing the right outcome every time. It is about creating the conditions for decisions to be made with the right information, appropriate challenge and a clear understanding of the consequences. A poor decision can begin a costly chain reaction. A project may need to be redesigned. A system may not meet the requirements of the people who need to use it. A restructure may create new problems rather than solving the original ones. A process may become more complicated because the underlying issue was never properly understood. Once that happens, organisations often spend additional time and money trying to put things right. People who could have been focused on delivering priorities are pulled into resolving problems. Teams become frustrated. Deadlines move. Confidence falls. In some cases, the organisation then has to make another difficult decision simply to undo or correct the first one. There is also a less obvious cost. Poor decisions can affect trust. Employees notice when decisions repeatedly change direction or when the rationale behind them is unclear. Customers experience the consequences when services become slower or less effective. Partners can lose confidence when commitments are repeatedly revised. Over time, this can create decision fatigue, where people become reluctant to act because they expect the direction to change again. The challenge is finding the right balance between making a decision and making sure it is the right decision. Good decision making is not about endless analysis. It is about having a disciplined approach that provides enough information and challenge to make a sound decision at the right time. Before a significant decision is made, there should be a clear understanding of the problem being addressed, the outcome required and the evidence available. The people closest to the issue should have an opportunity to contribute, particularly where a decision will change how work is delivered. Alternatives should be considered, assumptions challenged and risks understood. Importantly, the decision should also be capable of being explained. People do not necessarily need to agree with every decision, but they should be able to understand why it was made. Good governance has a role here, but governance should enable better decisions rather than create layers of approval that simply slow everything down. The right level of scrutiny depends on the scale, risk and consequences of the decision. When a decision turns out to be wrong, organisations should also resist the temptation to defend it simply because time and money have already been invested. Continuing with a poor decision because changing course feels uncomfortable can increase the eventual cost. Sometimes the most effective decision is to acknowledge that circumstances have changed, learn from what happened and take a different direction. The cost of a poor decision is therefore rarely limited to the original investment. It can include wasted resources, lost time, frustrated people, reduced confidence and missed opportunities. Good organisations will not get every decision right. They will, however, create an environment where decisions are properly considered, challenged when necessary and changed when the evidence shows that they should be. Good organisations are also able to pivot when needed. The objective is not to eliminate every bad decision. It is to make better decisions, recognise poor ones early and avoid allowing one decision to create a much bigger problem.

The announcement that the Government is pausing and reviewing parts of the Local Government Reorganisation programme raises an important question beyond the immediate uncertainty about which councils will eventually exist: what is the cost of changing course after significant work has already been undertaken? On 7 September, the Government announced that decisions affecting Essex, Hampshire, Norfolk and Suffolk would be withdrawn following updated legal advice. Proposals in a further 14 areas have also been paused while the programme is reviewed. The Government confirmed that decisions on Cambridgeshire and Peterborough and West Sussex had yet to be made, with both areas included in the wider review. The review is intended to ensure that the process is robust, lawful and aligned with the priorities of the new administration. Whatever the eventual outcome, substantial work has already been undertaken by councils preparing for potential structural change. Business cases have been developed, options assessed, consultation undertaken and programme structures established. Specialist expertise has been commissioned and resources committed. While much of this work may continue to provide value, particularly through research, analysis, data and organisational learning, some expenditure will inevitably become sunk cost where resources have been committed to a structure, timetable or implementation model that no longer proceeds. There is also a human cost to changing direction. Councils have brought in consultants, interim professionals and additional programme capacity to support demanding timescales. Where work is paused or no longer required, people can find themselves without a role, sometimes with little notice. How such decisions are communicated therefore matters. People delivering transformation are stakeholders in the programme and should be treated as such. Clear, timely communication is an important part of responsible change management. The experience of Local Government Reorganisation also provides a wider lesson for programme management. Large transformation programmes need clear decision and review points, defined dependencies and regular testing of the assumptions on which plans are based. External factors can change, including legislation, legal advice, funding, political priorities and economic circumstances. Effective programmes need the ability to respond to those changes rather than simply continuing because significant investment has already been made. There are circumstances where stopping, reassessing or changing direction is the responsible course of action. The measure of effective programme management is whether decisions are taken at the right time, with a clear understanding of the consequences. That means considering what has already been invested, what can be retained, what should be stopped and what lessons can be applied elsewhere. For local government, the current situation demonstrates the complexity of delivering structural transformation at scale. Reorganisation affects governance, services, systems, workforce, culture and communities. It cannot be treated simply as an organisational redesign exercise. Changing direction can affect programme capacity, commissioned work, organisational priorities and the ability of councils to maintain momentum while the future remains uncertain. Ultimately, these consequences have a financial impact on the public purse. The money spent on planning, consultancy, programme teams, business cases and preparation is public money. Where work is paused, changed or abandoned, some of that investment may no longer deliver the outcome for which it was originally intended. The decision by government underlines the importance of robust decision making, effective governance and strong programme management from the outset. Changing direction will sometimes be necessary. The responsibility is to understand the cost of doing so, protect the value of work that has already been undertaken and ensure that the lessons are carried forward. The taxpayer ultimately pays for the cost of changing course, making it essential that those lessons are not lost alongside the work itself.

Leadership is often described in terms of vision, strategy and decision making. Delivery, meanwhile, is frequently treated as something that happens further down the organisation. In reality, the relationship between leadership and delivery is far more connected and getting the balance right is essential if an organisation is going to perform effectively. Good leaders need to understand what is happening on the ground. They need enough knowledge of the work to ask the right questions, challenge assumptions, identify risks and make informed decisions. Leadership does not mean becoming detached from delivery or simply receiving reports about what other people are doing. The problem starts when understanding the work becomes doing the work. A leader who continually steps in to solve problems, take over tasks or make decisions that should sit elsewhere may feel that they are helping. In reality, they can unintentionally weaken the capability of the organisation. People stop taking ownership because they know someone else will step in. Decisions become concentrated at the top. Leaders become overloaded and the organisation becomes increasingly dependent on them. There is an important difference between being accountable for delivery and personally delivering everything. Effective leaders establish clarity about what needs to be achieved, why it matters and who is responsible for delivering it. They create the environment in which people have the authority, resources and support to do their jobs well. They provide direction when it is needed, remove barriers and intervene when there is a genuine issue that cannot be resolved at the appropriate level. That requires trust. Trust does not mean stepping away and hoping everything works out. It means setting clear expectations, establishing appropriate controls and allowing capable people to get on with the job. Where capability is lacking, the answer should not automatically be for the leader to take the work back. It may instead be to coach, develop, resource or reorganise so that the capability exists where it is needed. There is also a balance to be struck between leadership and expertise. Technical or professional knowledge matters, and experienced leaders will often have considerable expertise themselves. But being the most knowledgeable person in the room does not mean being the person who should make every decision or undertake every task. Organisations become stronger when knowledge and responsibility are distributed rather than concentrated. This is particularly important during transformation and organisational change. Change creates uncertainty, competing priorities and pressure to deliver quickly. Leaders can easily become drawn into the detail because they want to maintain control. Yet sustainable transformation depends on people throughout the organisation understanding their role, taking ownership and developing the confidence to make decisions. The strongest leaders therefore know when to step forward and when to step back. They remain visible and engaged without becoming the bottleneck. They challenge without undermining. They support without taking over. Most importantly, they recognise that their success should not be measured by how much they personally do, but by what the organisation is capable of achieving without them having to do it all. Leadership is not about being the person with all the answers. It is about creating the conditions in which the right people can provide the answers and deliver the results. Leaders lead. People deliver. The real skill is knowing where one ends and the other begins.

Restructuring an organisation often begins with a familiar question: should the organisation start again from the ground up, or should it build on the structure and capability already in place? There is no universal answer. The right approach depends on why the organisation is restructuring, what it needs to achieve and whether the existing organisation provides a sound foundation for the future. A restructure should not be an exercise in moving boxes on an organisation chart. It should be an opportunity to determine how the organisation needs to work. Starting again from first principles can be tempting. It creates an opportunity to challenge assumptions, remove legacy arrangements and design an organisation around its future strategy rather than its historical development. This can be particularly valuable where responsibilities have become fragmented, duplication has developed or the organisation has changed significantly since its existing structure was created. However, starting from ground zero does not mean ignoring what already exists. Organisations contain valuable knowledge, experience, relationships and capability that may not be immediately visible on an organisation chart. Removing these simply because they belong to the existing structure can create unnecessary disruption and potentially weaken the organisation rather than strengthen it. Building on what exists can provide greater continuity. It allows an organisation to retain successful teams, established expertise and effective ways of working while addressing the areas that are no longer fit for purpose. It can also make implementation easier because people are not being asked to adapt to an entirely new operating environment at the same time. The danger is that an incremental approach can become little more than rearranging the existing structure. Teams are renamed, responsibilities are moved and reporting lines are changed, but the fundamental problems remain. If the organisation's processes, decision making, accountability and ways of working are not examined, a new structure may simply reproduce old problems in a different form. The starting point should therefore be the organisation's purpose and future requirements, not its existing hierarchy. What outcomes does the organisation need to deliver? What capabilities will it require? Where should decisions be made? Which functions need to work more closely together? Where are there unnecessary duplication, gaps or barriers? What does the customer, resident, service user or wider organisation actually need from the service? These questions provide the basis for determining the functions and capabilities required. Only then should consideration be given to the structure needed to support them. This does not mean every restructure needs a blank sheet of paper. In many cases, the most effective approach is a combination of both. Start with a clear view of what the organisation needs to become, assess the existing organisation against that future state, retain what works and redesign what does not. That distinction matters. The objective is not to preserve the existing structure simply because it exists, nor to dismantle it simply because change is being proposed. The objective is to create an organisation that is capable of delivering its strategy effectively. People also need to be part of that assessment. Existing employees often understand the organisation's strengths and weaknesses better than any organisation chart can show. Their knowledge can identify practical issues, dependencies and opportunities that may otherwise be missed. Restructuring should therefore recognise what people bring to the organisation, rather than treating the existing workforce as another element to be moved around. Ultimately, successful restructuring is about more than organisational design. It is about creating the conditions for better performance. Structure, governance, processes, technology, capability and culture all need to work together. The question is therefore not simply whether to start again or build on what exists. It is whether the organisation is prepared to understand what it needs to become, objectively assess what it already has and make deliberate choices about what should stay, what should change and what needs to be built. Sometimes that means starting again. Sometimes it means building on a strong foundation. The important thing is to make that decision based on organisational need, not organisational habit. BONUS - Useful Questions to ask 1. Why are you restructuring? What problem are you trying to solve? What has changed to make the current structure no longer appropriate? Is the driver strategic, operational, financial, regulatory or cultural? What happens if nothing changes? 2. Is the current structure actually the problem? Are the problems caused by structure, or by processes, governance, systems or ways of working? Are responsibilities unclear? Is there duplication between teams? Are there gaps in accountability? Are decisions being made at the right level? 3. What needs to be different in the future? What does the organisation need to achieve over the next three to five years? What capabilities will be needed that do not currently exist? What will customers, residents or service users need from the organisation? What does the future operating model need to enable? 4. What is already working? Which parts of the current organisation perform well? Where is there strong capability and expertise? Which processes work effectively? What relationships or knowledge would be difficult to replace? What should definitely not be lost through restructuring? 5. Where are the weaknesses? Where is performance consistently below expectations? Where are there bottlenecks or unnecessary layers? Where does work cross organisational boundaries unnecessarily? Are resources aligned with priorities? Are teams spending too much time maintaining processes rather than delivering outcomes? 6. What do your people tell you? Do employees understand what their role is and how it contributes to organisational objectives? Where do people experience frustration or duplication? What do staff believe needs to change? Are there skills or capabilities that are being underused? What knowledge could be lost through restructuring? 7. What would starting again really mean? Would a blank sheet genuinely solve the underlying problems? What would you keep if you were designing the organisation from scratch? What would you remove? What would you create? Are you prepared for the disruption that a completely new structure could create? 8. What would building on the existing structure mean? Can the current organisation realistically deliver the future strategy? Which parts can be retained? Which parts need to change? Are you genuinely redesigning the organisation, or simply moving boxes on an organisation chart? Would incremental change address the underlying issues? 9. What evidence supports your decision? Have you used performance data? Have you mapped key processes? Have you considered demand and workload? Have you assessed current capability? Have you tested the assumptions behind the existing structure? 10. Finally, ask the most important question: If we were designing this organisation today, knowing what we now know, what would we design differently?

It is a simple question, but one that can create considerable confusion in project governance. In some organisations, the project start date is recorded when an idea first emerges. In others, it is when business case development begins. Some organisations only regard the project as having started once funding has been approved and delivery is authorised. These distinctions matter. The date a project is deemed to have started affects reporting, accountability, resource allocation, delivery timescales and how project performance is measured. The key question is whether developing an idea and building a business case should be considered project delivery, or whether they are activities that take place before the project formally begins. UK government project delivery guidance provides a useful framework for considering this distinction. The Government Functional Standard for Project Delivery defines a project as a unique, temporary management environment created to deliver one or more business products or outcomes. The standard also distinguishes between portfolios, programmes and projects. The Government's Teal Book expands on this standard and recognises that project delivery sits within a wider environment that includes policy development, evaluation, portfolios and programmes. Its structure separates project delivery from the wider work of developing and shaping proposals. This distinction is particularly important in local government and Mayoral Combined Authorities, where a potential project can spend considerable time in development before there is an agreed scope or a decision to proceed. An idea is not a project. An organisation may identify a problem, opportunity or strategic priority. It may then undertake research, stakeholder engagement, options appraisal, feasibility work and financial analysis. A business case may be developed and considered through several approval stages. All of this work is important. But it is not necessarily project delivery. The Government's current Guidance on developing business cases makes this distinction particularly relevant. The guidance uses the Five Case Model to develop business cases for projects and programmes. The process is designed to establish whether there is a compelling case for change, assess the available options and determine whether the preferred approach is commercially, financially and operationally deliverable. The Green Book describes appraisal as the process of assessing the costs, benefits and risks of different options for achieving government objectives. In other words, much of the activity undertaken during business case development is about deciding what should be done and whether it represents value for money. That is fundamentally different from managing an agreed project. A project manager cannot effectively manage delivery when the organisation is still deciding what the project should deliver. If the scope is still being developed, the preferred option has not been agreed, funding is uncertain and the delivery approach remains subject to change, the organisation is still developing the proposition. This does not mean that business case development should be unmanaged. It requires appropriate governance, clear ownership, defined decision points and sufficient project delivery expertise to test whether the proposed approach is realistic. Indeed, the Five Case Model includes a management case specifically concerned with how a proposal will be delivered. However, calling this activity the project can create some unintended consequences. A project may appear to have been running for eighteen months when, in reality, the first twelve months were spent developing and testing the proposal. A project may consequently appear to have missed its original milestones when those milestones were never intended to represent delivery activity. It can also make resource reporting difficult. If project teams are allocated against proposals that have not yet been approved, organisations can lose sight of the distinction between resources used to develop investment decisions and resources used to deliver approved projects. Most importantly, it can blur accountability. There is a fundamental difference between being responsible for developing a business case and being responsible for delivering an approved project. The skills, governance arrangements, risks and measures of success are not necessarily the same. A clearer approach is to recognise a defined development phase before formal project initiation. The terminology can vary. It might be called concept development, feasibility, business case development, pre project activity or project development. The label is less important than establishing a clear point at which the organisation moves from deciding whether and what to deliver into delivering an agreed proposition. Project initiation can then establish the delivery environment. This is where governance, roles and responsibilities, resources, risks, controls, milestones, dependencies, benefits and the delivery plan can be formally established. The project has something tangible to manage because there is now an agreed proposition against which delivery can be measured. Different project management methodologies will use different terminology and life cycle models. Agile, waterfall, PRINCE2 and government project delivery approaches do not all describe project stages in exactly the same way. The Government Functional Standard itself supports tailoring delivery approaches to the circumstances of the project. The principle, however, remains useful regardless of methodology. The starting point for a project should be clear enough that everyone understands what is being delivered, why it is being delivered, who is accountable and what authority exists to proceed. That does not make everything before that point less important. In fact, good project delivery depends on good development and appraisal. But development and delivery should not automatically be treated as the same thing. An idea starts a conversation. A business case tests the proposition. An approved scope creates something that can be managed. Project initiation should mark the transition from developing the proposition to delivering it. Getting that distinction right creates clearer governance, more meaningful reporting and greater accountability. It also gives organisations a much more accurate picture of how long their projects actually take and where time and resources are being spent.

Leadership is often incorrectly judged by visible measures. The size of a budget, the number of direct reports or the breadth of a portfolio can all create the impression of influence and success. Yet these are poor indicators of leadership effectiveness. The most successful leaders are not those who oversee the largest departments. They are those who build capable teams, deliver consistent outcomes and leave their organisations stronger than they found them. One of the most common misconceptions in organisational leadership is that larger teams automatically create greater value. As headcount increases, so do the demands placed on a leader's time, attention and judgement. Every additional member of staff requires direction, support, coaching, performance management and regular communication. There comes a point where a leader's capacity becomes stretched, reducing the time available to develop individuals, resolve issues and maintain close oversight. Without the right management structure and clear delegation, increasing the size of a team can reduce effectiveness rather than improve it. This is where the concept of empire building becomes relevant. It rarely begins with poor intent. A leader may assume responsibility for another function to improve coordination, absorb a team to address a capability gap or create additional roles to strengthen governance. Individually, these decisions can be justified. Collectively, they can create increasingly complex structures where success becomes associated with the size of a department rather than the value it delivers. The most effective leaders adopt a different mindset. Rather than asking how their function can grow, they ask how the organisation or team can perform better. Their focus is not on extending control but on increasing capability. They simplify processes, remove barriers to delivery and create the conditions in which others can succeed. Great leaders also recognise that capability exists across the organisation. They value the expertise of other teams, respect professional boundaries and understand that sustainable success depends on collaboration rather than ownership. No single function has a monopoly on good ideas or effective delivery. The distinction is significant. Leaders who build empires often accumulate responsibility, while leaders who build capability develop people. One increases organisational complexity, the other reduces it. One centralises decision making, the other empowers teams to make informed decisions. One creates dependency, the other creates resilience. Some of the highest performing teams are also the leanest. Their reputation is not built on organisational size but on professionalism, credibility and consistent delivery. They earn influence because colleagues trust them to solve problems, provide sound advice and deliver results. Their authority comes from competence rather than hierarchy. Conversely, organisations can become vulnerable when too much authority is concentrated in one area or one individual. Decision making slows, routine issues require unnecessary escalation and progress becomes dependent on a single leader's availability. Although these leaders may appear influential, they often become less agile and less effective over time. Perhaps the simplest measure of leadership can be expressed as: Leadership is measured by the capability you create, not the size of the team you control. Sustainable success is built on achieving results, earning trust and reducing unnecessary complexity, not on expanding organisational structures. As organisations continue to navigate financial constraints, increasing demand and continual transformation, this distinction has never been more important. The leaders who will have the greatest long term impact are those who invest in people, strengthen organisational capability and enable others to perform at their best. Their legacy is measured not by the number of people they managed, but by the capability they created. A useful question for every leader is therefore this: Could your team continue to perform successfully without you for a month? If the answer is yes, you have created capability. If the answer is no, you may have created dependency. History rarely celebrates those who built the largest departments. It remembers the leaders who developed talented people, solved meaningful problems and created organisations that continued to thrive long after they had moved on. Ultimately, great leadership is not about building empires. It is about building capability.