What to put on a business analyst’s digital card
- Domain focus A phrase like “retail lending and collections” tells a hiring manager whether you already speak their business language.
- Analysis type Requirements, process improvement, data analysis or UAT lead; naming your strength routes the right conversations to you.
- Sample artefacts link A page with redacted BRDs and flows lets the person judge your clarity before any call.
- LinkedIn Recommendations from product owners and delivery leads carry weight for BA roles.
- Phone or WhatsApp Recruiters schedule calls quickly; a number you answer keeps you in the shortlist.
- Email address Use a personal email so contacts made during one engagement can reach you after it ends.
- Modelling notations Saying you work in BPMN, UML activity diagrams or simple swimlanes tells a delivery lead how your process maps will look and whether their developers already read that format comfortably.
- Data skills A short line such as “SQL for reconciliation checks, Excel pivots for impact sizing” shows you can test requirements against real data, which separates analysts who question numbers from those who only take notes.
When to share it
- After a requirements workshop with a new client team, so business users know whom to contact with follow-up questions.
- At BA community meetups and IIBA chapter sessions where peers and hiring managers network.
- In your email signature when you send meeting notes and clarification lists outside your organisation.
- At career fairs for analysts switching into the role, to share your samples with recruiters on the spot.
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:
Hello Priya, thanks for the conversation about claims turnaround at the meetup. Here is my card with a sample process map and user story set I built for a mock insurer. Do send across the role details when the opening is live.
Where to put the QR code
- The cover page of a printed workshop pack or process map you hand out to business users.
- The last slide of a requirements walkthrough presented to a client team.
- Your name badge at IIBA chapter meetings and analyst community sessions.
Mistakes to avoid
- Linking samples that still show real client data A blurred account number or a screenshot with a policyholder name can slip through. Recheck every image, header and file name in your samples page before the card goes out.
- Describing yourself only as a “bridge” Almost every BA calls themselves a bridge between business and technology. Replace it with the specific outcome you deliver, such as “shorter claim cycles through clearer rules”, so you are remembered.
- Forgetting to mention UAT ownership In many Indian projects the BA runs or coordinates user acceptance testing. If you have, say so on the card; many hiring managers look for exactly that experience.
Tips for a card that gets saved
- Keep the domain line specific; “BA, banking” is weaker than “BA for credit card operations and disputes”.
- Check that every sample linked from the card is fully redacted, including screenshots and file names, before you share it.
- Put your strongest artefact first in the linked page; many people will open only one document.