Course Contents
Projects to Proof Converter >
Full Conversion Walkthrough, Data Analysis and Team Training
Article 13 of 15 / Projects to Proof Converter
Article Objective:
Apply the three format conversion process to analytical and people development projects, two of the most widely held and most chronically under documented types of professional experience, and observe the full transformation from raw input to polished, proof ready output in each format.
Full Conversion Walkthrough, Data Analysis and Team Training
Not all impactful professional work looks like a campaign with trackable impressions and a landing page dashboard. Much of the most valuable work in organizations happens in spreadsheets and in training rooms, in analysis that changes how decisions get made, and in programs that change how people perform.
Both of these project types respond fully to the extraction framework. Both produce compelling proof content when the three questions are applied honestly and the outputs are built carefully. Both are vastly underrepresented in professional portfolios and resumes, which means that the professionals who document them well have a significant and durable competitive advantage over those who don’t.
This article covers both.
Project A: Data Analysis
The Raw Input: “I helped analyze data for my team and made a report.”
Twelve words. Two immediate problems worth naming: “helped” signals partial ownership rather than primary accountability, and “made a report” describes the deliverable rather than the outcome. It says what was produced, not what changed because of it.
This is exactly the kind of raw description that sits on resumes, gets scanned in six seconds, and generates no response. Let’s extract what’s actually there.
The Three Extraction Questions:
What did you specifically do?
Conducted a twelve month sales and margin analysis at the individual SKU level, not at the category level where the team’s standard reporting operated. Built a dynamic Excel dashboard that consolidated data from three separate internal systems: the ERP, the sales CRM, and the inventory management platform. Applied trend analysis across rolling 90-day windows to surface performance patterns. Applied margin analysis at the SKU level to identify which products were generating revenue while quietly eroding profitability.
How did you approach it?
The three source systems had never been connected for this type of analysis, data normalization was required before any analytical work could begin. The analytical question was deliberately framed at the SKU level rather than the category level because aggregate category reporting had been masking individual product performance. The specific analytical lens, looking for revenue healthy but margin eroding products, was chosen because that pattern is the one most likely to be invisible in standard reporting and most costly when left unaddressed.
What changed as a result?
Identified three specific SKUs that were generating solid revenue but systematically eroding margin, a pattern that had been entirely invisible in the category level reporting the team used previously. The three SKUs represented approximately $80K in slow moving inventory. The inventory manager reviewed the analysis, validated the findings, adjusted reorder quantities for all three products, and launched a targeted promotional campaign to clear the accumulated stock. In the following quarter, inventory holding costs dropped by 15%.
Three layers extracted. All three outputs can now be built.
Resume Bullet:
Conducted 12-month SKU level sales and margin analysis consolidating data from 3 internal systems, identifying $80K in slow moving inventory and contributing to a 15% reduction in quarterly holding costs.
Quality checklist:
- Strong verb: ✓ “Conducted” signals primary ownership of the analytical work
- Number present: ✓ Multiple, $80K, 15%, 3 systems, 12 months
- Outcome stated: ✓ The outcome is the $80K identification and the 15% cost reduction, not the report itself
- Scale/context: ✓ “3 internal systems,” “12-month” both provide meaningful context
- Active voice: ✓
- Under 25 words: ✓ (24 words)
The bullet is proof ready.
Mini Case Study:
Challenge: The team’s standard sales reporting operated at the category level, making individual product performance invisible. Revenue metrics looked healthy, but there was no mechanism to identify which specific SKUs were quietly eroding margin and building up costly inventory balances, a problem that was financially significant but structurally undetectable with existing tools.
Approach: I built a dynamic Excel dashboard connecting three previously siloed internal systems, ERP, CRM, and inventory management, and ran 12 months of SKU level trend and margin analysis. The analysis was specifically designed to surface products where revenue appeared strong but margin was being eroded, the pattern most likely to be missed by standard category level reporting.
Outcome: Identified 3 underperforming SKUs representing approximately $80K in slow moving inventory. The inventory manager adopted the recommendations; holding costs dropped 15% in the following quarter.
Proof: Dashboard model available on request.
Word count: 139. All four sections present. The challenge explains specifically why the analysis was needed, the structural gap in visibility, not just “we needed better data.” The approach shows the analytical reasoning. The outcome is specific and consequential. Within the target range.
STAR Interview Story:
Designed to answer: “Tell me about a time you used data to solve a problem.”
Situation: “My team was making product restocking decisions based on category level revenue data, which meant that individual product performance was essentially invisible. The categories looked fine, but we had no way of knowing which specific products within those categories were actually driving that performance and which were quietly building up inventory while eroding margin.”
(Two sentences, 56 words. Establishes the structural visibility problem clearly.)
Task: “I decided to build a more granular analysis, SKU level rather than category level, specifically to answer the question the standard reporting couldn’t: which individual products are performing well on margin, and which are generating revenue while quietly costing us money?”
(One sentence, 46 words. The task is framed as a diagnostic question, which sets up the Action section appropriately.)
Action: “First, I mapped the data sources I’d need to connect, we had three internal systems that tracked different dimensions of product performance but had never been integrated for this type of analysis. I built a consolidated dashboard in Excel, normalized the data across all three sources, and ran twelve months of trend and margin analysis at the SKU level. I designed the analysis specifically to surface a particular pattern: products where the revenue line looks healthy but the margin line tells a different story. That’s the pattern that’s hardest to see in aggregate reporting and typically the most costly when it goes unaddressed.”
(Six sentences, approximately 115 words. Shows the problem setup, three separate systems, never integrated. Explains the normalization challenge. Describes the specific analytical lens, revenue healthy but margin eroding products, and why it was chosen.)
Result: “The analysis surfaced three SKUs that matched exactly that pattern, solid revenue, significant margin erosion, and approximately $80K in slow moving stock that had been accumulating invisibly. The inventory manager reviewed the findings, adjusted the reorder quantities for all three products, and ran a clearance campaign to move the existing stock. In the quarter following the analysis, inventory holding costs dropped 15%. The dashboard became the team’s standard reporting tool, and the category manager added a quarterly SKU level review to the team’s regular cadence.”
(Four sentences, approximately 90 words. Three quantitative data points, $80K, 15%, three SKUs. The sustained impact, dashboard adoption, new review cadence, closes the story with organizational resonance.)
Full story delivery time: approximately 115 seconds. Within target.
Project B: Team Training and Onboarding
The Raw Input: “I trained new employees at work.”
Six words. Maximum vagueness. Complete absence of any element that would allow a reader to evaluate whether this was a one hour onboarding session or a six week comprehensive program; whether it was done well or adequately; whether it changed anything about how new employees performed.
Let’s extract.
The Three Extraction Questions:
What did you specifically do?
Designed a four module onboarding curriculum from scratch, there was no existing program, so everything was created new. The four modules covered: company systems and tools, role specific processes and workflows, cross-functional dependencies and communication protocols, and performance expectations and feedback mechanisms. Developed all supporting documentation. Built a structured shadowing schedule paired with guided reflection exercises. Delivered the full program personally to two cohorts of new hires over approximately six weeks.
How did you approach it?
The design process began with diagnosis before curriculum development. Interviewed the five most recently onboarded employees and asked specifically: where did they feel most underprepared in their first few weeks, and what would have made the biggest difference if it had been covered earlier? Used the interview findings to prioritize curriculum content, the four modules were chosen based on where the previous cohort reported the highest confusion, not based on assumptions about what new hires needed. Built the materials to be reusable and deliverable by others, so the program could be sustained after the initial design and delivery work was complete.
What changed as a result?
Average time from start date to full independent productivity dropped from six weeks to 3.5 weeks, a 42% reduction. All eight new hires who went through the program were still with the organization at the 30-day mark. The prior year retention rate at 30 days had been 75%. The onboarding program was subsequently adopted by two additional regional teams. The manager cited the program in the year end review as a significant contributor to team stability during a period of high hiring volume.
Resume Bullet:
Designed and delivered a 4-module onboarding program for 8 new hires, reducing average ramp up time by 42% (6 weeks to 3.5 weeks) and achieving 100% 30-day retention vs. a prior year benchmark of 75%.
Quality checklist:
- Strong verb: ✓ “Designed and delivered”, both the creation and the execution are claimed, accurately
- Numbers present: ✓ Four numbers: 4 modules, 8 new hires, 42%, 100% vs. 75%
- Outcome: ✓ Ramp up time and retention are both outcomes, not task descriptions
- Scale/context: ✓ The 75% benchmark contextualizes the 100% retention result
- Active voice: ✓
- Length: 33 words, slightly over the target, but the information density justifies it. Consider whether “4-module” and “8 new hires” can be compressed or whether a shorter version sacrifices too much specificity.
Mini Case Study:
Challenge: The team had no formal onboarding process. New hires learned through informal shadowing and trial and error, consistently taking six or more weeks to reach full independent productivity, creating ongoing capacity gaps during a period of high hiring volume. Thirty day retention was also a recurring problem, with 25% of new hires leaving within their first month.
Approach: I diagnosed the design problem before writing any curriculum, interviewing the five most recently onboarded employees to identify where they’d felt most underprepared. The four modules were built specifically around those high confusion areas. I developed reusable materials and a structured shadowing schedule with guided reflection, then delivered the program personally across two cohorts.
Outcome: Average ramp up time dropped from 6 to 3.5 weeks, a 42% improvement. All 8 new hires reached the 30-day mark, compared to a 75% retention rate the prior year. The program was subsequently adopted by 2 additional regional teams.
Word count: 150. Exactly at the upper limit of the target range. Every element earns its place. The challenge section names both problems, ramp up time and retention, which gives the dual metric outcome its full context.
STAR Interview Story:
Designed to answer: “Tell me about a time you identified a gap and built something from scratch to address it.”
Situation: “Our team was in a high hiring period, bringing on new people every few weeks, and we had no formal onboarding process. Every new hire learned through informal shadowing, which meant the quality of their start depended entirely on who happened to be available to answer questions. Average ramp up time was running at six weeks, and we were losing about a quarter of new hires within their first month.”
(Three sentences, 63 words. Two concrete problems: six week ramp up, 25% attrition in the first month.)
Task: “I took on building a formal onboarding program from scratch, curriculum design, materials development, and delivery, with the goal of getting new hires productive faster and reducing early attrition.”
(One sentence, 34 words. Specific scope: design, materials, delivery. Clear goals: faster productivity, lower attrition.)
Action: “I started by interviewing the five people who’d most recently joined the team, asking specifically where they’d felt unprepared and what would have made the biggest difference if they’d learned it earlier. That data drove the curriculum design, rather than building what I thought new hires needed, I built what the evidence said they actually needed. I developed four modules focused on the highest confusion areas: company systems, role specific workflows, cross-functional dependencies, and performance expectations. I built reusable materials and a structured shadowing schedule with reflection exercises at each stage, then delivered it personally across two cohorts of new hires over about six weeks.”
(Six sentences, approximately 120 words. The diagnostic first approach is the most distinctive element, interviewing before designing. The evidence driven curriculum design signals analytical thinking applied to a people development challenge.)
Result: “Average ramp up time dropped from six weeks to three and a half, a 42% improvement. Every one of the eight new hires who went through the program was still with us at the thirty day mark, compared to a 75% retention rate the year before. The program was subsequently adopted by two other regional teams, and my manager cited it in my year end review as a significant contributor to team stability during a challenging hiring period.”
(Three sentences, approximately 70 words. Percentage improvement with before and after. Retention comparison. Two sources of organizational resonance: regional team adoption and manager citation in the year end review.)
Full story delivery time: approximately 120 seconds. At the upper edge of the target range. If needed, the Situation section can be trimmed by one sentence.
What Both Conversions Demonstrate
The data analysis project and the onboarding project share nothing on the surface. One is quantitative, solitary, tool intensive. The other is interpersonal, collaborative, curriculum based. One lives in Excel. The other lives in training rooms.
But both respond to the identical framework, the same three extraction questions, the same four part bullet formula, the same four section case study structure, the same STAR organization. The content changes entirely. The structure that holds it doesn’t.
This is the generalizability of the framework. It is not calibrated to a particular type of work, a particular industry, or a particular career stage. It is calibrated to the challenge of extracting and communicating professional value, a challenge that is structurally identical regardless of what the work was.
What changes is the difficulty of the extraction. Some project types have obvious, available numbers. Others require calculation, estimation, or qualitative framing. Some projects have clear, single owner outcomes. Others are collaborative in ways that require careful framing. The framework accommodates all of these variations, not by changing its structure, but by providing the specific tools needed for each situation within the broader structure.
Key Takeaway:
The framework works because it’s built around a structural truth about professional impact, not around a particular type of work. Every project has three layers. Every project can produce three outputs. The extraction questions surface the layers. The output
templates give them the right format. The work is always the same, and the work is always worth doing.
Action Step:
Choose one project from your work history that you’ve never documented because it didn’t feel like the right “type”, too ordinary, too collaborative, too internal, too hard to quantify. Apply the three extraction questions to it fully. Write all three outputs. The discomfort you feel at the start of this exercise is the exact discomfort that this course is designed to help you move through. The output at the other end will be worth it.
- The final module addresses the long game, how to build and maintain an evidence bank that makes every future job search, performance review, and career conversation dramatically easier than the last.