Launching Internal Projects with Clarity

Launching Internal Projects with Clarity

How many well-intentioned internal projects, working groups, or thematic reviews have started with a flurry of activity only to fizzle out? Often, the cause is a vague or poorly defined starting point. Leaders can prevent this wasted effort and staff frustration by clearly 'commissioning' internal work. A strong, simple brief at the outset is the key to turning a good idea into a valuable, evidence-based improvement.

Define the 'Why' and the 'What'

Before you ask a colleague or team to start a project, you must be clear on the problem you are trying to solve. Without a precise question, any work will lack focus. A good brief is rooted in evidence and has a clear purpose.

• State the problem: Link the project directly to a specific finding. Is it a persistent trend in achievement data, a theme from the learner voice, a weakness identified in your self-assessment report (SAR), or a strategic objective from your Quality Improvement Plan (QIP)?
• Formulate a precise question: Move from a vague notion like "look at digital skills" to a focused inquiry such as, "To what extent are our level 2 construction apprentices developing the specific digital skills required by local employers, and what are the key gaps?"
• Specify the desired output: Be clear about what the project should deliver. Is it a short evaluative report with recommendations, a new standardised resource for staff, a proposal for a change in process, or a presentation for governors?

Set Clear Parameters and Scope

Scope creep is the biggest enemy of internal projects, leading to overburdened staff and unfinished work. Your initial brief must establish firm boundaries to keep the project manageable and on track.

• Define what is in-scope: Clearly state which provision types, learner or apprentice groups, departments, or business processes the project should focus on.
• State what is out-of-scope: Being explicit about what the team should not look at is just as important. This prevents the work from expanding into unintended areas.
• Provide a realistic timeline: Set out key milestones and a final deadline. Work with the project lead to ensure the timeline is achievable alongside their existing responsibilities.
• Outline the resources: Be upfront about the support available. This could include allocated time off-timetable, a small budget for resources, access to specific data sets from MIS, or administrative support.

Clarify Roles and Responsibilities

Ambiguity over who does what can quickly derail a project. The commissioning brief should act as a simple terms of reference that everyone involved can refer to.

• Appoint a single project lead: This person is responsible for coordinating the work, managing the team, and being the main point of contact.
• Identify the project sponsor: This is usually the senior leader who commissioned the work. Their role is to champion the project, remove obstacles, and provide strategic guidance, not to micromanage the process.
• Establish reporting expectations: Define how and when the project lead should provide updates to the sponsor. Keep it light-touch - a brief email or a short check-in is often enough to ensure the work is on track.

Trust the Team with the 'How'

A commissioning brief provides direction, not a step-by-step instruction manual. The goal is to empower your colleagues by giving them a clear problem to solve, then trusting their professional expertise to find the best way to solve it. This approach fosters ownership and often leads to more creative and effective solutions.

• Focus on the outcome, not the method: The brief should define the 'what' and 'why', leaving the 'how' to the project team.
• Encourage professional judgement: Let the team decide the best way to gather evidence - whether through learner focus groups, work scrutiny, data analysis, or discussions with employers.
• Create a safe space for findings: Reassure the team that the goal is improvement, not blame. They must feel confident they can report their findings honestly, even if they are uncomfortable.

Where this fits in QualityHero

This structured approach to internal projects is fundamental to effective quality improvement. A clear project brief can be attached as evidence to an action within your QIP module, demonstrating a thoughtful and well-managed approach to improvement. The project's findings and final report can then be logged within the relevant Toolkit Areas, providing an evidence-rich narrative for your next SAR cycle and populating your Leadership Reports with clear evidence of impact.