There is a version of male allyship that lives on LinkedIn — public, polished, and conveniently costless. Then there is the version that happens in standups, hiring panels, and promotion discussions when the only audience is the people directly affected. One of these changes outcomes. The other changes follower counts.
The Difference Between Performance and Practice
Allyship That Needs an Audience Is Not Allyship
You have seen it. The male senior developer who shares the International Women is Day post on LinkedIn, tags three women colleagues with fire emojis, collects his engagement metrics, and then spends the remaining 364 days talking over the same women in sprint reviews. That is not allyship. That is personal branding with a diversity filter.
Performative allyship looks good in screenshots. Structural allyship changes outcomes when no one is documenting it. The distinction matters because one costs nothing and the other costs comfort, social capital, and sometimes professional risk.
In NZ tech, the performative version is especially tempting because the community is small enough that reputation travels fast. Being seen as “one of the good ones” carries social currency. But the women who work alongside these men know the difference between the LinkedIn post and the Monday morning standup. They know who amplifies their ideas and who absorbs them. They know who sponsors their promotion case behind closed doors and who only mentions support in public-facing contexts. The gap between the two is where allyship either exists or does not.
Girl Geek Dinners and the Invited Guest Model
Girl Geek Dinners has always operated on a specific principle: men are welcome as invited guests, not as hosts. The distinction is not gatekeeping — it is architecture. The events exist to centre women is voices and experiences in tech. Men are invited to listen, learn, and participate, but the space does not revolve around them.
This model reflects a broader philosophy about what allyship requires: showing up in someone else is space on their terms. Not to lead, not to fix, not to explain — to be present and useful in whatever way the space needs. For some men, this is straightforward. For others, being in a room where they are not the default audience is a genuinely unfamiliar experience, and that discomfort is itself educational.
The GGD approach acknowledges a reality that corporate diversity programmes often avoid: you cannot be an ally and the centre of attention simultaneously. The men who attend GGD events and then carry what they learned back into their workplaces — adjusting their own behaviour, not just their awareness — are demonstrating the kind of allyship that scales. It starts with accepting that your role in this particular story is supporting cast, not lead.
In the Room Where It Happens

Amplifying Credit Where It Belongs
There is a well-documented phenomenon called “hepeating” — when a woman suggests an idea that gets ignored, then a man repeats the same idea minutes later and receives credit. It happens in NZ tech meetings with depressing regularity. Not because the men involved are malicious, but because conversational dynamics and unconscious status hierarchies shape who gets heard.
Effective allies interrupt this pattern actively. The technique is simple and specific: “That is a great point — I think Sarah raised exactly that five minutes ago. Sarah, can you expand on your original suggestion?” It redirects credit, it makes the dynamic visible, and it costs the ally nothing except a moment of social awareness.
The Obama White House formalised a version of this called amplification: women staffers agreed to repeat and attribute each other is points until the pattern became self-sustaining. NZ tech teams can adopt the same practice without a policy memo. It just requires one person in the room paying attention to who is being credited and who is being absorbed. In small teams — which describes most NZ tech companies — one ally doing this consistently changes the entire conversational culture within weeks.
Meeting Dynamics and Who Gets Airtime
Research from Virginia Tech found that in mixed-gender groups, men speak 75% of the time. The ratio gets worse in technical discussions where confidence in domain expertise correlates with volume rather than accuracy. NZ tech is not immune to this — anyone who has sat through a sprint retrospective where one person dominated the conversation while three others stared at their laptops knows the pattern.
Allies with meeting facilitation power can change this structurally. Round-robin formats that give every person equal speaking time. Written input collected before discussion begins, so ideas are evaluated before social dynamics filter them. Explicit time limits on contributions. These are not radical innovations — they are basic facilitation practices that most teams skip because “we are all adults here” feels easier than admitting the current format advantages the loudest voices.
For allies without facilitation authority, the intervention is smaller but still effective: noticing when someone has been trying to speak and creating space. “Hey, I think Priya had her hand up” or “Let us hear from the people who have not spoken yet” are low-friction phrases that redistribute airtime without making a production of it. The key is consistency — doing it once is a gesture; doing it every meeting is a structural change.
The Sponsorship Gap Nobody Talks About
Mentorship is giving advice. Sponsorship is staking your reputation. The difference is enormous, and it is where allyship in NZ tech most often falls short.
A mentor says “you should apply for that senior role.” A sponsor says to the hiring panel “I have worked with her for two years, she is ready, and I am putting my name behind this recommendation.” Mentorship is private. Sponsorship is public, carries professional risk, and directly influences career outcomes. Research from the Center for Talent Innovation (now Coqual) found that sponsorship is the single strongest predictor of promotion for women in technical roles — stronger than performance reviews, tenure, or self-advocacy.
In NZ tech, the sponsorship gap is acute because decision-making circles are small and relationship-driven. When senior men sponsor other men for leadership roles — often unconsciously, through the “who comes to mind” heuristic — they replicate existing demographics. Actively choosing to sponsor women requires overriding that default. It means saying her name in rooms she is not in, advocating for her promotion when the budget is tight, and being willing to be wrong publicly if the appointment does not work out. That last part is why sponsorship is rarer than mentorship: it has actual stakes.
Calling It In, Not Calling It Out
Challenging Bro Culture Without the Showdown
The fantasy version of allyship involves a dramatic confrontation: someone says something sexist, the ally delivers a devastating rebuke, the room applauds, culture shifts overnight. The reality is less cinematic and more effective.
Most exclusionary behaviour in NZ tech is not overt. It is the Slack channel where women is technical contributions get emoji reactions while men is get threaded discussions. It is the beers-after-work culture that functions as an informal decision-making space from which parents are excluded. It is the “just banter” that new joiners laugh along with because they are reading the room.
Calling in — as opposed to calling out — means addressing behaviour privately, specifically, and without moral grandstanding. “Hey, I noticed you cut across Mei is point in that meeting — probably worth circling back to her idea” works better than a public lecture about gender dynamics. Not because the public version is wrong, but because the private version is more likely to produce behaviour change rather than defensiveness.
The NZ Human Rights Commission has resources on bystander intervention that apply directly to workplace dynamics. The consistent finding: frequent, low-intensity corrections shift culture more reliably than rare, high-intensity confrontations.
The Social Cost and Who Should Pay It
Challenging exclusionary behaviour carries a social cost. The person who says “that joke was not great” gets labelled humourless. The person who pushes back on a hiring decision gets labelled difficult. The person who insists on structured interviews instead of pub chats gets labelled bureaucratic. These labels stick, and they affect career progression.
Here is the thing: men in NZ tech can absorb this cost more easily than women can. A senior male developer who challenges bro culture is “thoughtful” or “progressive.” A woman who does the same thing is “difficult” or “aggressive” or — the perennial favourite — “not a cultural fit.” The social penalty for the same behaviour is distributed unequally, which means the responsibility for bearing it should be as well.
This is not comfortable to hear if you are a man in tech who considers himself a good person. Nobody wants to be told that their silence has a cost that someone else is paying. But that is the arithmetic: every time exclusionary behaviour goes unchallenged because challenging it feels awkward, a woman in the room files that data point. She learns who will show up when it is uncomfortable and who only shows up when it is easy. Allies are defined by the second category, not the first.
Structural Allyship Beyond Individual Behaviour

Using Positional Power to Change Systems
Individual behaviour changes are necessary but insufficient. A man who amplifies women is voices in meetings but does not push for pay equity reviews when he has budget authority is doing half the work. Structural allyship means using whatever positional power you hold to change the systems that produce inequity, not just the symptoms.
In NZ tech, this looks like specific actions tied to specific authority. If you set salaries, audit them for gender gaps and fix the gaps you find — Stats NZ reports a persistent 9% gender pay gap nationally, and tech is not exempt. If you approve hiring panels, mandate diverse representation on every panel. If you control meeting agendas, build in structured participation that does not advantage the loudest voice. If you write performance reviews, examine whether your criteria implicitly reward behaviours more commonly exhibited by men (self-promotion, visibility-seeking) while penalising behaviours more commonly exhibited by women (collaboration, credit-sharing).
Xero and Trade Me have both tied diversity metrics to leadership KPIs — meaning managers are evaluated partly on whether their teams become more diverse over time. That is structural allyship codified. It takes the “good intentions” out of individual hands and builds accountability into the system.
Parental Leave and the Fatherhood Penalty That Is Not
When men take parental leave, they normalise it. When they take the full entitlement rather than a token fortnight, they erode the assumption that parenting is women is work — an assumption that underpins most of the career penalty women face in tech.
NZ offers 26 weeks of government-funded parental leave that can be shared between partners, plus many tech companies offer additional paid leave. But uptake by fathers remains low. A 2024 survey by Parental Leave NZ found that the majority of fathers in tech took less than four weeks, citing workload, team pressure, and concern about career impact. The irony is thick: the same career concerns that make men hesitant to take leave are the concerns women face in amplified form every time they become parents.
Allies in leadership positions can shift this by modelling the behaviour. When a male CTO takes three months of parental leave and the company does not collapse, it sends a signal that no policy document can replicate. When a team lead openly discusses his parental leave planning in standups, he normalises the conversation for every father on the team who was afraid to raise it. This is allyship that costs personal convenience — patchy sleep, nappy changes, career interruption — which is precisely why it carries more weight than a LinkedIn post.
The Long Game of Showing Up Consistently
Allyship is not a certificate you earn and frame. It is a practice — repetitive, unglamorous, and defined entirely by what you do when it costs you something. The men in NZ tech who are genuinely shifting the landscape are not the ones giving keynotes about diversity. They are the ones who have been quietly doing the work for years: redirecting credit, sponsoring promotions, challenging exclusion, taking leave, auditing pay, and accepting the social friction that comes with all of it.
Girl Geek Dinners events regularly feature men who describe their allyship journey as ongoing and imperfect. That framing matters. Perfectionism is the enemy of sustained effort — if you stop showing up because you said the wrong thing once, you were never really committed to the practice.
The test is simple and it is the same test it has always been: what do you do when nobody is watching, when there is no credit to collect, when the easier path is silence? That is where allyship lives. Not in the statement, not in the post, not in the conference panel. In the meeting where you notice who is not being heard. In the review where you notice who is not being promoted. In the moment where saying nothing is comfortable and saying something is not. That moment, repeated across months and years, is what changes a workplace.
Allyship is not a title or a moment. It is a pattern of behaviour sustained over time, measured by what changes in the room when you are in it and what you advocate for when you are not. The men doing this work in NZ tech know it is imperfect and ongoing. That is exactly why it works.