After a tech event: make a follow-up plan that doesn’t depend on a reply

You leave a tech event with a useful idea, a name in your notes and an intention to stay in touch. Then the question arrives: what should you actually say? A broad request for career advice can be difficult to write, and difficult for the other person to answer.

Keep two next steps: something you can do yourself and a small invitation the other person can choose to accept. This gives the conversation a direction while keeping your learning moving if their inbox stays quiet.

This feels timely after Women in Tech Week, which ended on 16 October 2026. The organiser’s closing recap encouraged people to follow up and apply advice. The exercise below works after a local meetup, an online session or a conference, including when you are new to tech or exploring a different role.

Choose an outcome you can influence

Professional networking means building and maintaining relationships around work, interests and mutual help. Oxford’s careers guidance describes it as reciprocal assistance. A useful follow-up can continue an exchange of ideas, share something you promised or thank someone for a specific explanation.

Choose one outcome for this message. Perhaps you want to clarify one part of a role, compare approaches to a practice task or return a resource. Keep a separate action that belongs to you, such as trying the public exercise discussed at the event.

Send the message while you can still describe the conversation accurately. If time has passed, briefly restore the context. Avoid treating a fixed number of hours as a deadline after which a professional relationship is lost.

Turn your notes into four clear decisions

1. Recover the shared context

Purpose: Help the person recognise the exchange without inventing familiarity.

Write down where you met and one topic you discussed. If you only watched their talk, say that. Attending a presentation does not mean the speaker knows you or remembers a conversation.

Check their name and the professional channel they offered. Keep only the details needed to describe the exchange accurately.

2. Pick an action you own

Purpose: Make the learning useful before a reply arrives.

Choose a small task related to the discussion: try a practice exercise, read the recommended public guide or write down how two roles differ. Define what you will produce and when you will review it.

Choose something realistic for your time and skills. Their reply can enrich the work without becoming the condition for starting it.

3. Ask one answerable question

Purpose: Make it clear what responding would involve.

“Can you help me get into tech?” asks someone to work out the problem as well as the answer. A question about one decision is easier to understand: “When comparing entry-level analyst roles, which part of the job description would you investigate first?”

Check whether the answer is already in the resource they shared. If you want them to review something, describe its size and ask whether they are open to it before attaching a large portfolio or requesting ongoing mentoring.

4. Leave room for their choice

Purpose: Offer a next step with a clear, manageable boundary.

A short written answer may be enough. If a conversation would help, explain its subject and suggest a limited length, with flexibility about timing. Give the person an easy way to decline.

Keep promises separate from new requests. If you agreed to send a resource, send that resource first. A thank-you does not need an additional question, meeting request or job application attached.

A fictional example: one question about data work

Illustrative example: Hina is considering a move into data analysis. At a fictional local meetup, she talks with Bex, an analyst, about checking unfamiliar data before making a chart. Bex suggests practising with a small public dataset and agrees that Hina can send one question afterwards.

Hina will inspect a practice dataset and write three questions about its meaning. She asks Bex one question, keeping responsibility for the investigation herself.

Continue an agreed conversation

Hi Bex, we spoke at the data meetup about checking a dataset before making a chart. I’m trying that with a small public example. I can see missing values, but I do not know what they mean. Is there one question you would ask the dataset owner before deciding how to handle them? A short reply would be helpful if you have time.

The people, conversation and message are fictional. No reply or career result is assumed. Hina can still record what she knows, what remains uncertain and what she needs to learn next. The example does not prescribe a technical treatment for missing data.

Match the message to what actually happened

These further fictional examples show two different purposes. Adapt the names, context and details to your real exchange. Only describe actions you have taken and resources you can genuinely share.

Share an exercise you promised

Hi Jo, we discussed explaining product decisions after the session. Here is the practice exercise I promised: choose a fictional product decision, write down two options and give one reason for your choice. Then ask a peer which part needs more explanation. Thank you for sharing your team’s approach.

Thank a speaker you did not meet

Hi Sam, I watched your session on testing assumptions. Your explanation of checking what a customer means gave me a useful question to try in my next practice interview. Thank you for making that distinction clear. I wanted to let you know what I’m taking away from the session.

The session and exercise exchange are fictional. The speaker example asks for no additional work and does not imply a personal conversation.

Keep a five-line follow-up note

Context: Where did the exchange happen, and what was actually discussed?
Purpose: Am I continuing a conversation, returning something promised or saying thank you?
My action: What will I do, produce and review independently?
Invitation: Is there one question or bounded request, and was contact welcomed?
Next decision: What will I do if they reply, decline or do not respond?

Keep one note per useful exchange and update it when you fulfil a promise or change your plan. This is a suggested exercise, not a formal networking framework.

Continue your plan when the inbox is quiet

A quiet inbox tells you that you have no reply. It does not tell you why. Continue the practice task and use appropriate public resources or existing support around you.

If someone explicitly invited a follow-up and an agreed time has passed, you can consider one brief reminder. Respect a decline and avoid chasing the same person across different channels. Keep your own next action moving.

Choose one conversation today. Complete the five lines, draft the message and check that it describes the exchange accurately. Then set aside time for your action. You finish with a clear invitation and something useful to do, whatever happens next.

This recent-event-inspired evergreen guide was prompted by WeAreTechWomen’s 16 October recap. The four decisions, five-line exercise and fictional messages were composed for Coded Female. Specificity and reciprocity are established networking practices. No response rate, hiring outcome or universal follow-up deadline is claimed.