Technology recruitment · Canada
Business & project talent
Connect technology work with business requirements.
The expertise in context
Connect business needs with delivery.
Business and project recruitment focuses on the people who connect organizational requirements, stakeholders and technology work. A useful brief explains what the role will own and how it fits into the team’s delivery responsibilities.
Business context
Explain the requirement, the stakeholders and the decisions the role supports. Include the industry or process knowledge that is essential.
Project responsibility
Describe the scope, deliverables and dependencies. Clarify where the role’s accountability begins and ends.
Technical environment
Identify the technology context and the teams the person will work with. Distinguish technical expertise from the ability to coordinate across disciplines.
Give the role a clear outcome.
A business or project title can mean different things in different organizations. Define the responsibilities and experience that will make the person relevant to your team.
Your hiring brief
- Business and project context
- Role responsibilities
- Stakeholder and technical environment
- Required experience and availability
Before your next step
A few useful answers.
What is the difference between a business analyst and a project manager to you?
An analyst owns the question; a project manager owns the delivery. Briefs that blur the two attract people who do neither especially well, so it is worth being explicit about which problem you are hiring to solve.
Do these roles need a technical background?
Usually some. Someone running a technology programme does not need to write code, but they do need to hold a credible conversation with the people who do, and that is what we screen for.
Can you support a programme that is already in trouble?
Often, and the brief is different. Tell us plainly what has gone wrong — people who are good at recovering a late programme are a different group from people who are good at starting one.