Overview

The Dare IT playbook replaces a universal winner with a conditional rule: choose Mentoring when network access is the binding gap, Challenges when employers lack credible evidence of practical ability, both when the gaps interact, and neither when demand, readiness, or participation barriers dominate. Define the outcome and context, make the mechanism testable, involve employers and enabling supports, measure mechanism and employment outcomes, and revise before scaling. The randomized findings concern particular programs, populations, and settings, with mechanisms not perfectly isolated.

Learning outcomes

Mentoring is a stronger first hypothesis for network access; Challenges for employer uncertainty about practical ability.
Both routes may be sequenced when gaps interact, but neither replaces demand, foundational skills, or enabling support.
The durable rule is to match the intervention to the constraint, then verify and adapt within evidence limits.

Keywords

Dare ITConstraintsMentoringChallengesDiagnosisAdaptation

A Constraint-First Playbook for Tech Transitions

The Dare IT study does not end with a universal winner between Mentoring and Challenges. It ends with a more useful decision rule for women moving into technology work: match the intervention to the obstacle that is blocking the transition, then verify whether the predicted mechanism actually changes. Mentoring is the stronger first move when access to people, information, and referrals is the binding gap. Challenges is the stronger first move when employers cannot see or trust practical ability. Both may be appropriate when the gaps interact, while neither should be treated as the answer when the main problem is missing demand, foundational readiness, or the inability to participate.

That conclusion is narrower than a slogan and more demanding than a feature comparison. It asks a provider, employer, or participant to define the desired outcome, inspect the context, state what should change, and remain willing to revise the initial choice. It also preserves what the evidence cannot establish: the study evaluates particular programs, in a particular population and setting, with mechanisms that are distinct but not perfectly isolated.

Start with the constraint, not the program

The first question is not “Would this person benefit from mentoring?” Almost anyone can benefit from useful advice or a supportive professional relationship. The decision question is whether the participant’s path to a suitable technology job is primarily blocked by network and search friction, by employer uncertainty about practical ability, or by another constraint that these programs do not address.

A network-oriented diagnosis is plausible when a participant has relevant ability but few technology contacts, weak information about vacancies, limited access to hiring managers, or a career interruption that has reduced professional reach. It is stronger when the local technology ecosystem is thin and the participant’s existing work history would become more valuable if someone could connect it to the right employer. In the Dare IT study, Mentoring increased LinkedIn connections by about 52.7 relative to the control group and produced earlier employment movement consistent with introductions and direct search support. Those intermediate changes explain why a relationship-intensive program can be worth its scarce capacity.

A signal-oriented diagnosis is plausible when a participant can perform or learn the relevant work but has too little conventional evidence for an employer to judge it. This often describes early-career candidates with limited work history, but it can also describe career changers whose previous experience does not map clearly to a new role. Challenges is a stronger first move when an industry-designed, reviewed project can add information that a degree or résumé does not provide. Its 11-percentage-point employment effect in the study and its delayed timing are consistent with a portable work sample doing its work in later applications.

The distinction is not between a “people person” and an “online learner.” A mentor can provide technical feedback, and a portfolio can affect confidence. The distinction is what the program is principally designed to change. Mentoring changes access to relationships and opportunities. Challenges changes the evidence available to an employer. That difference should appear in the first hypothesis about fit.

The surrounding labor market then determines whether either mechanism has somewhere to operate. The World Bank’s opportunity-readiness framework is useful here. A work-ready participant in a market with real technology vacancies may need connection or signaling. A participant with low readiness may need skills, work-based learning, and placement. A highly capable participant in a low-opportunity location may need mobility, remote-work access, demand stimulation, or employer-side intervention. A person facing both low readiness and low opportunity may need a broader package involving income protection, productive opportunities, and several coordinated services.

Published by DeepMox

FAQ

When should a provider choose neither Mentoring nor Challenges first?

A provider should choose neither first when missing demand, foundational readiness, or participation and access barriers dominate. Mobility, skills, income, childcare, transport, or institutional support may need to come before a matching intervention.

What should a provider measure after assigning a Dare IT route?

It should measure the predicted mechanism and employment, along with participation conditions, employer response, costs, and subgroup access. Contacts without useful access or projects without employer engagement are weak confirmation.

What are the main limits of the Dare IT playbook?

The playbook rests on particular programs, populations, and settings; its mechanisms are not perfectly isolated, subgroup estimates are uncertain, and later operational expansion is not a completed causal replication.

Previous9 minDare IT: Scale Without Losing Fit

All chaptersBack to Topic

Dare IT: Constraint-First Playbook

A Constraint-First Playbook for Tech Transitions

Start with the constraint, not the program

FAQ