Before the Program: Find the Binding Constraint
For women in Dare IT’s technology-transition programs, “not employed in technology yet” is an outcome, not a diagnosis. This chapter focuses on the difference between a genuine skill deficit and a failure of matching, access, or employer information. The practical value of that distinction is straightforward: Mentoring and Challenges can help when a participant is ready enough to use them, but neither program should be asked to solve a shortage of jobs, missing foundational skills, or a barrier that prevents participation in the first place.
A labor-market intervention begins with a tempting shortcut. If someone has not found work, give them more training. Sometimes that is correct. But training is only one possible response to a stalled transition, and it is often the wrong one when the person already has relevant technical ability. More lessons do not automatically create a professional network, make a portfolio credible, provide childcare, or persuade employers to open jobs in a place where few exist.
The question is not whether the person needs “help.” It is which part of the route from capability to employment is failing.
A stalled transition has more than one cause
The World Bank’s guidebook organizes employment constraints into four broad groups: labor demand, worker readiness, matching, and regulatory or institutional conditions. These categories are useful because they separate the visible symptom—a person has not obtained a job—from the mechanism producing it. They also prevent the comparison between Mentoring and Challenges from becoming a debate about program style detached from the labor market around the participant.
Demand constraints concern the availability and quality of opportunities. A participant may be capable of technology work while living in a local market with few employers, weak demand, or no openings in their specialization. A program that improves her résumé cannot create a vacancy. A mentor may help her look farther afield, but that becomes a mobility or remote-work question, not simply a network question. If the binding problem is insufficient demand, the relevant responses may include connecting workers to another geography, supporting employer hiring, reducing mobility costs, or stimulating new firms and sectors.
Readiness constraints concern the ability to perform and sustain the work. Readiness includes technical knowledge, but it can also include basic skills, work habits, communication, job-search ability, and the resources needed to keep participating. A participant may be interested in front-end development but not yet able to complete the level of work employers expect. In that case, a polished portfolio can conceal the gap temporarily without resolving it. A longer skills pathway, work-based learning, or remedial support may be more appropriate. The point is not to treat “readiness” as a fixed personal trait; it is a description of what the current opportunity requires and what the participant can reliably do.
Matching constraints arise when workers and employers exist but cannot find or evaluate one another effectively. Employers may know too little about a candidate’s ability. Candidates may know too little about vacancies, hiring standards, or which firms are genuinely seeking their skills. Informal referrals and personal contacts can dominate formal recruitment, making social capital part of the hiring process. This is the space in which Dare IT’s two programs are most directly relevant. Mentoring is designed to improve access to people and information. Challenges is designed to improve the evidence an employer can use to assess practical ability.
Regulatory and institutional constraints shape whether work and programs are accessible at all. Credentials may not be recognized. Employment services may be weak. Transport may be expensive or unsafe. Childcare may be unavailable. Social norms may restrict women’s choices. Income insecurity may make it impossible to spend weeks on assignments or unpaid search. These conditions are not peripheral to a program’s effectiveness. They determine whether someone can attend, complete, network, travel to an interview, or accept a job after receiving an offer.
The categories overlap. A mother returning after a career interruption may face a network gap because professional contacts have faded, an income constraint because time for unpaid search is costly, and an employer-information problem because her recent work history is thin. Calling that situation a simple skills gap hides the interaction among causes. Conversely, not every obstacle should be absorbed into a matching program. If the participant cannot yet perform the work, or if the local market has almost no relevant demand, Mentoring and Challenges may be useful later but are not the first repair.
A diagnosis should therefore distinguish at least four things: the outcome we observe, the cause most likely producing it, the conditions that make that cause harder to overcome, and the intervention that can change the mechanism. That sequence matters. It keeps a program from claiming credit for solving a problem it never addressed, and it gives decision-makers a way to notice when a promising intervention is being used in the wrong setting.
The final branch is intentionally narrow. If matching is the main problem, the next question is not yet “Mentoring or Challenges?” It is whether the mismatch is primarily about access to opportunities or about the employer’s uncertainty regarding ability. That is a more demanding diagnosis than asking which program has the better reputation.
Place the person and the place on two axes
The guidebook adds a second lens by crossing local opportunity with worker readiness. This produces four broad situations, not four permanent identities. The same person can move between them as their skills, location, family circumstances, and labor market change.
In a high-opportunity, high-readiness setting, the central task is often to connect a capable worker to existing jobs. Job intermediation, credible skill signals, labor-market information, and measures that reduce social or institutional barriers are especially relevant. This is the quadrant closest to the Dare IT comparison when participants possess technical skills and technology employers are hiring. Even here, however, “high readiness” does not mean that every participant has the same network or the same evidence of practical competence. A work-ready candidate can still be invisible to employers.
In a high-opportunity, low-readiness setting, jobs may exist but workers need more preparation to meet them. Technical or vocational training, apprenticeships, internships, soft-skills development, and placement support may be necessary together. A portfolio can be useful as part of that route, but it should not be mistaken for the preparation itself. If a candidate cannot perform the underlying tasks, making the résumé more persuasive will not create durable employment.
In a low-opportunity, high-readiness setting, the challenge is not mainly to make the worker more employable. It is to connect their capability to demand beyond the immediate location or to help create new demand. Mobility assistance, remote-work access, employer incentives, entrepreneurship support, or cross-border matching may matter more. Mentoring could widen a person’s reach into a larger technology ecosystem, but the mechanism would include geographic access and labor demand. A portfolio alone cannot compensate for the absence of suitable vacancies.
In a low-opportunity, low-readiness setting, a narrow job-search intervention is least likely to be enough. People may need income protection, basic skills, productive assets, childcare, transport, and a sequence of support that makes sustained participation possible. The World Bank describes such packages as more comprehensive because multiple constraints reinforce one another. This is far from the specific population studied by Dare IT, and the comparison should not be stretched to cover it.
The two axes clarify why context changes the value of an intervention. A network is more valuable when there are real opportunities elsewhere in the network. A signal is more valuable when employers are present and have vacancies but cannot confidently assess candidates. Both become less useful when the participant lacks the foundation to use them or cannot afford to participate. “Scalable” delivery does not remove these dependencies; it can make a mismatch happen more quickly and to more people.
What would count as evidence of the problem?
No single indicator proves a participant’s binding constraint, but different patterns should lead to different questions. A likely network problem might appear when a technically capable participant has few contacts in the sector, lives outside a major technology hub, has experienced a long career interruption, or reaches interviews mainly through rare personal referrals. The relevant follow-up is not simply whether she wants a mentor. It is whether access to introductions, hiring information, and sector-specific guidance would change the opportunities she can realistically pursue.
A likely credibility problem might appear when an early-career participant can describe relevant tools but has little work history or few concrete artifacts to show. If applications produce little response despite evidence of underlying ability, the question becomes what an employer can verify. Does the candidate have a reviewed project tied to real tasks? Can an interviewer inspect decisions, revisions, and trade-offs? Does the signal come from an intermediary or evaluator that employers recognize? A certificate with no trusted interpretation may be weaker than a smaller portfolio that makes competence visible.
A likely readiness problem requires a different test. Can the participant complete the work represented in the application? Can she explain the choices in a project, respond to feedback, and manage the basic requirements of the role? If not, a portfolio program may still be useful, but its function is skills development rather than merely signaling. The intervention should then be evaluated on whether capability changes, not only whether the final artifact looks persuasive.
A likely demand or institutional problem also requires different evidence. Are suitable vacancies available in the relevant geography or specialization? Are employers willing to hire candidates with this background? Do transport, care, safety, legal status, or income constraints prevent participation or job acceptance? If the answer is yes, assigning a participant to either Dare IT program without an enabling response risks treating a structural barrier as an individual shortcoming.
These questions are deliberately practical because diagnosis should guide observable choices. The aim is not to place every applicant in a neat category. It is to identify the most changeable bottleneck and to remain open to more than one. A person can need both a credible project and a route into employer networks. A participant may start with Challenges to create evidence, then use Mentoring to learn how to put that evidence in front of the right people. Conversely, a mentor may reveal that the participant needs more preparation before either referrals or a portfolio will help.
This also explains why the World Bank framework should be used as a map rather than a label. Its four quadrants are a reminder to inspect the place and the person together. Its five design principles—contextual tailoring, comprehensive support, aligned incentives, private-sector engagement, and integration with social protection—make the same point from the program side. The Dare IT comparison isolates two particularly important matching mechanisms, but a real employment pathway may need to supply the missing conditions around them.
The diagnostic conclusion is modest but consequential: a stalled technology transition does not tell us which program to choose. It tells us where to look. Once the surrounding demand, readiness, and access conditions are understood, the network route can be examined on its own terms: how a mentor’s relationships and knowledge change the participant’s practical access to opportunity, and how that mechanism differs from simply receiving encouragement.