Experience Engine Blueprint >

The Project Selection Decision Tree; Choosing What to Build Based on Your Real Constraints

Article 3 of 9 / Experience Engine Blueprint

Article Objective:

Help members select the right project path based on their actual time, access, and risk tolerance so they start with a plan that will realistically be completed.

The Project Selection Decision Tree; Choosing What to Build Based on Your Real Constraints

 The biggest mistake professionals make when starting a project-based experience-building effort is choosing the most impressive-sounding project rather than the most executable one. An impressive project that stalls in week two because it requires 20 hours per week that you do not have. An executable project that fits your real constraints and gets completed produces a deliverable, a metric, and a story;  three things that move your job search forward in ways that an abandoned ambitious project never can.

The decision tree has three variables. How many hours per week can you realistically commit, accounting for your current work, personal obligations, and the active parts of your job search? What kind of access do you have to external organizations, clients, or data sources? And how much risk are you comfortable taking on in terms of the complexity of the work, the dependence on another party’s availability and cooperation, and the potential for the project to take longer than planned?

Five to ten hours per week with limited external access points to self-initiated projects. You work independently on your own timeline, using public data or your professional context, and produce deliverables for your portfolio. The risk is low because the only variable is your own execution. The flexibility is high because nothing depends on someone else’s schedule or availability. The proof is slightly less externally validated than a project involving a real client. Still, it is entirely within your control and control matters when you are managing a complex job search alongside other obligations.

Ten to twenty hours per week with some access to nonprofits, small businesses, community organizations, or professional contacts opens the door to pro bono and volunteer engagements. The added effort required to secure the engagement and coordinate with an external party pays dividends in credibility. 

A third party who can vouch for your work, provide a reference, and potentially offer a LinkedIn recommendation adds a layer of validation that no self-initiated project can produce. 

The tradeoff is dependency; the project timeline is no longer entirely within your control, because it also depends on the organization’s responsiveness and availability.

Twenty or more hours per week with existing client relationships or a strong professional network makes micro-freelance add-ons the strongest available path. Paid work with a real contract is the gold standard of proof in this program, and if your constraints allow for it, a small, scoped freelance engagement delivers the most persuasive evidence in the shortest time. Even a project that earns a modest fee and takes four weeks carries more weight in a hiring conversation than a self-initiated project of equivalent quality because someone made a business decision that your work was worth paying for.

Matching Projects to Gaps

Once you identify which path fits your constraints, the next step is cross-referencing your chosen path with your Gap Library to find the recipes that most directly address your highest-priority gaps. The goal is not to choose the most interesting project or the one that sounds most impressive. The goal is to choose the project that closes the most critical gap with the most efficient use of your available time.

A common mistake at this stage is trying to address too many gaps with a single project. Each project in this program is designed to address two or three related proof requirements, not a dozen. Trying to build a project that covers everything produces something unfocused that is hard to describe clearly in an interview and harder to evaluate as evidence. Pick two or three recipes, assign each one to a specific gap or cluster of related gaps, and execute them sequentially rather than simultaneously.

Your action step:

 Using your Gap Library, identify which project path self-initiated, pro bono, or micro-freelance, is realistic for your current situation. Then identify the two or three gaps from your Gap Library that are most critical to close. In the next article, you will find nine specific project recipes organized by role type. Before you read them, have your path and your priority gaps clearly in mind so you can choose with intention rather than browsing.