What to put on a project manager’s digital card
- Domain and delivery scale A line like “ERP rollouts for manufacturing, teams up to 50” sets expectations about the size of work you lead.
- Certification PMP, PRINCE2 or a scrum credential named plainly answers a common screening filter for programme roles.
- Project summaries link Short write-ups of key programmes give context that a title cannot carry.
- LinkedIn profile Hiring managers check recommendations from past sponsors and team members before they reach out.
- Phone number Escalations and quick check-ins still happen on calls, so give a number you answer during working hours.
- Professional email Use a personal address you will keep, so contacts from one programme can still reach you after you move on.
- Methods you run Saying whether you run scrum, waterfall, hybrid or SAFe programmes tells a hiring manager how you will fit their delivery model, and it heads off a common mismatch between agile teams and plan-driven project leads.
- Time zones handled A note such as “daily overlap with US East and UK teams” shows you can run distributed delivery, which services firms and capability centres in India ask about early in interviews.
When to share it
- At a project kickoff with a new vendor or client team, so everyone saves the right contact for escalations.
- At PMI chapter meetings and agile meetups where hiring managers and peers meet in person.
- In the email signature of programme status mails sent to stakeholders outside your company.
- During job interviews, shared after the panel round so the panel can review your project summaries again.
What to say when you send it
A card link on its own is easy to ignore. Add a line that reminds the person where you met and what to do next — for example:
Hi Rakesh, it was useful to compare notes on vendor handovers at the PMI session today. My card has a short write-up of the payments migration I mentioned. Happy to share the cutover checklist template if it helps your team.
Where to put the QR code
- The final slide of your project closure or lessons-learned presentation shared with external stakeholders.
- The footer of a printed programme summary you hand out at a steering committee or vendor kickoff.
- Your speaker badge or name tent at PMI chapter events and delivery conferences.
Mistakes to avoid
- Putting the client’s logo on your personal card It may look impressive, but most services contracts do not allow you to advertise a client relationship. A line like “banking programmes for a European client” keeps you safe and still conveys scale.
- Leaving the card tied to a programme email Programme mailboxes are closed when engagements end. If your card uses one, contacts who try to reach you months later get a bounce and assume you have moved on without a trace.
- Using a long list of certifications as the title A title like “PMP, PRINCE2, CSM, SAFe, ITIL” reads like an acronym wall. Put your role and domain in the title and keep certifications in one row below it.
Tips for a card that gets saved
- Use the same title on the card, LinkedIn and résumé. If one says “delivery manager” and another “programme lead”, recruiters wonder which is true.
- Keep confidential client names off the card and summaries; use the sector and size instead, which still tells the story.
- Update the domain line when you change industries, since a new hiring manager will judge relevance from that one line.