Maybe you accept work immediately as it comes in, no questions asked. That type of process might work in smaller companies but probably wonât scale well as your company grows. Once you get to that point, youâll have more requests coming at you from many different directions, which can be overwhelming. A good project intake process will help control how work is accepted and gets done.
A basic process intake process includes the following elements:
- Initial request: An internal or external request is made for some type of work to be done, like a new product or new feature.
- Review: Consider if the project is a good fit for your team. For example, do you have the right skills and the time to take on the project?
- Accept or refuse the request: If you have the resources and the project fits within your teamâs scope of work, accept the request. If not, politely reject the request or suggest another team that might be able to complete the work.
- Start the project: Assign tasks, set a time frame, and get to work.
Why do you need a formal project intake process?
Itâs not enough to just come up with a processâthe process needs to be documented and practiced to optimize understanding and follow-through.
Providing teams and individuals with a well-documented project intake process can benefit your organization in the following ways:Â
- It establishes a single entry point for internal and external work requests, offering more control over the ways you accept new work.
- It helps you decide which projects are right for you and your team.
- It can help you develop a visual method for tracking project assignments and task ownership while managing upcoming work.
- It lets you distribute work evenly so one team or individual does not take on more than can be reasonably handled.
- It helps you prioritize projects and assign them to teams or individuals with the right skill sets.
- It helps you analyze and determine where skills may be lacking so you can bring in new resources or provide adequate training for current employees.
Signs that you might need to update your project intake process
You might want to redefine your project intake workflow if you see any of the following signs in the current way you do things:
Requests are entered manually from a variety of channels
You might have requests coming in from too many different channels, like email, text messages, social media, handwritten sticky notes, verbal requests, and so on. Things can quickly get out of control as these requests pile up. Some could fall through the cracks and make you miss important deadlines.
You donât have a formal, documented process for turning requests into projects
Even if you arenât over-burdened with requests, you still wonât get very far if you donât have a way to determine which requests are most important and who they should be assigned to. Without a formal process, youâre just guessing about which requests should move forward.
Your project requests arenât tied to larger goals
As requests pile up and you struggle to keep up with demands, it can become harder to review upcoming work before you have to tackle the next project. Your project requests may become little more than a to-do list full of items that arenât strategically mapped to larger project goals. Without a process for determining what should be prioritized, important requests are often missed or delayed for too long.
You donât have a way to visualize and share your work
Itâs hard to plan for whatâs coming next if you canât see that far down the road. To effectively manage project requests, you need a way to visualize where you are right now, where youâve been, and whatâs coming next. Visual aids like calendars, Gantt charts, and Kanban boards let everybody see and understand whatâs been done, whatâs being done, and what the next priorities are. Without visuals, itâs harder to successfully align your team. Consider a collaboration software like Lucidspark to collaboratively visualize your workflow from top to bottom.