Project management
Scope, plan, risk, budget, suppliers and stakeholder control for a defined piece of work.
Specialist practice
Project, Product & Transformation
Projects, programmes, product, analysis, governance and change work that makes complex delivery governable.
Ireland market context
Read the role in its real setting.
Project, product and transformation titles vary widely between employers. The practical question is whether the role owns delivery, product decisions, governance, operational change, or a blend of these. The SOLAS National Skills Bulletin and Skills and Labour Market Research Unit are useful starting points for evidence-led labour-market context; each brief still needs a local reality check.
Occupations named for this practice: The taxonomy does not assign a distinct Critical Skills Occupations List category to this full practice. Some technology project and programme manager roles may fall within the IT occupations named on the list; eligibility depends on the occupation and the current official wording.
Check the current wording in the Department of Enterprise Critical Skills Occupations List. For broader evidence, see the SOLAS National Skills Bulletin and Skills and Labour Market Research Unit. This is general market context, not employment-permit advice.
Sub-disciplines we cover
Where the specialism becomes useful.
Titles are only a starting point. These are the work areas we use to understand relevance, evidence and the questions a role is likely to ask.
Programme management
Co-ordinating linked projects, dependencies, governance and benefits across a wider change agenda.
PMO & governance
Portfolio reporting, controls, RAID discipline, standards, assurance and decision cadence.
Business analysis
Requirements, process mapping, data, operating-model analysis and the translation between users and delivery teams.
Product management & ownership
Customer problem definition, prioritisation, discovery, roadmap, outcomes and product delivery.
Agile delivery & scrum
Team facilitation, agile ways of working, continuous improvement and delivery flow.
Change and transformation
People, process, technology and adoption work that makes a change stick in the organisation.
Service delivery management
Service performance, client governance, SLAs, operational improvement and cross-functional co-ordination.
Portfolio & benefits management
Investment cases, prioritisation, benefits tracking and executive-level portfolio choices.
Role families by seniority
Typical titles in the Irish market.
Organisations use titles differently. The work, decision scope and evidence of delivery determine the real level.
| Seniority | Typical titles |
|---|---|
| Entry | Project Co-ordinator; PMO Analyst; Junior Business Analyst; Product Operations Analyst; Scrum Master Assistant |
| Mid | Project Manager; Business Analyst; Product Owner; Scrum Master; Change Manager; Service Delivery Manager |
| Senior | Senior Project Manager; Programme Manager; Senior Product Manager; PMO Manager; Transformation Lead; Portfolio Manager |
| Lead and above | Programme Director; Head of PMO; Head of Product; Transformation Director; Chief of Staff; Portfolio Director |
Credentials and skills that matter
Use credentials as evidence, not decoration.
PMP and PRINCE2 are common project signals; Agile and Scrum credentials such as PSM or CSM can support delivery experience; IPMA, Lean Six Sigma and BCS Business Analysis are also relevant in the right context. A credential does not replace evidence of the size of change, governance exposure, decisions made and outcomes delivered.
Reference points include Project Management Institute, PeopleCert / AXELOS, BCS and IPMA.
What we look for in a credible profile
Relevant setting, clear scope, named tools or standards where they matter, honest responsibility, and outcomes that can be explained under interview. We do not inflate experience to make a profile look neater than it is.
If you are a job seeker in this practice
Translation, then focus.
People are rarely underqualified. They are usually under-translated. In this practice, translation needs to be technically and professionally precise.
Why this matters
Good work is often hidden behind a broad title, an internal system name or a list of duties. Employers need enough context to understand the level, setting and consequence of your contribution.
What we actually do
We translate delivery work that may sit under titles such as operations, implementation or analyst into clear evidence of scope, stakeholder groups, risk, milestones, decisions and outcomes. A parse-safe CV makes project terms searchable without turning an experienced practitioner into a list of methodologies. You keep a target strategy, STAR-ready evidence bank and role-specific interview preparation.
How it works
We review your target, qualifications, authorisation where relevant and full exposure. Then we build the Career Storyboard, evidence bank, positioned CV and Job Matrix before practising the conversations that decide the move.
What you get, and what changes
You keep a written strategy, designed and parse-safe CV, reusable achievement evidence and practice notes. The change is focus: fewer applications, clearer claims and answers that show what you actually did. We do not promise a job or an outcome.
If you are hiring in this practice
A sharper brief makes a specialist search possible.
A sharper brief identifies the business problem, scope boundary, sponsor, team, governance, measures of success and authority to act. We need the delivery context, current pain points, named stakeholders, non-negotiable experience and the decisions the hire can make. You receive a brief that distinguishes a project manager from a product owner or change lead, and a shortlist tested against that distinction.
1. Define the work
We agree the responsibilities, environment, must-haves, learnable skills, reporting line and first-year outcomes.
2. Test the market reality
We discuss availability, competition, location, process and the evidence that can reasonably be expected.
3. Interview against the brief
You receive a shortlist with written rationale and a process that tests the work, not confidence alone.
Interview themes in this practice
Prepare for the decisions behind the questions.
Common themes include delivery governance; prioritisation; stakeholder conflict; requirements quality; risk and dependency management; business value; adoption; and explaining what changed because of the work.
Good preparation means selecting real examples, being exact about your authority and explaining your reasoning, not memorising a generic answer.
Example questions
- Describe a project that went off plan. What did you escalate, reset and protect?
- How do you turn an unclear request into prioritised requirements?
- Tell us about a stakeholder disagreement that affected delivery. What did you do?
- How have you measured benefits or adoption after go-live?
- What would you put into a first programme governance pack?
Adjacent moves that work
Make the bridge visible.
Operations management into project delivery; business analysis into product ownership; implementation consulting into programme management; scrum mastery into delivery management; and PMO analysis into portfolio support. Credible moves need proof of ownership, reporting, decision support and measurable change rather than only meeting attendance.
What makes an adjacent move credible
Comparable context, a defined gap plan, evidence of responsibility and a realistic target level. We would rather name a step that can be defended than sell a leap that will not survive an interview.
Explore all specialist practicesNext step
Project, Product & Transformation: start with the real work.
Tell us what you have done, the environment you know and the move you are considering. We will begin with evidence and an honest view of the next step.