Bluebird perspectives · Practical guide
A request for “another business analyst” can mean very different things. One team needs someone to document operational processes. Another needs a bridge between business stakeholders and a technical delivery team. The job title alone rarely captures the difference.
Define the work before the profile
Start with the specific problem the person will help address. Describe the deliverables, the decisions they will support, and the people they will work with. A clear brief makes it easier to distinguish essential experience from skills that can be developed within the team.
Make the operating context visible
In banking, similar tasks can sit within very different environments. Include the relevant business area, systems, process dependencies, and internal review requirements. Explain where the role starts and where another team takes ownership.
A useful question: what should this person be able to understand, contribute to, and take ownership of during the first stage of the engagement?
Look beyond a list of skills
Communication and collaboration are part of the role. Consider whether the work involves clarifying ambiguous requirements, presenting to stakeholders, resolving exceptions, or coordinating across locations. These demands belong in the brief alongside technical and sector knowledge.
A short briefing checklist
- What work needs to move forward, and why?
- What are the first meaningful deliverables?
- Which experience is essential from the start?
- Who will provide direction and resolve questions?
- What timing and working arrangements are expected?
A precise brief does not need to be long. It needs to help everyone understand the same requirement.
General discussion for staffing and delivery planning.
All perspectives