top of page

The Cost of Invisible Skills and Credentials

"Notes from the Field" is a series from Good Business Lab (GBL) that highlights the human stories behind the research and statistics. This piece is a personal reflection by Meghna Gopalan, a former member of GBL's design team, following field visits to an automotive shop floor to understand what happens to blue-collar workers' skills and credentials when they change jobs. What she found raised fundamental questions about where skills live once tenure ends, who the system is built to recognize, and what it costs when the system does not recognize all its workers.

You walk onto a shop floor, and the first thing you notice is a rhythm. Hundreds of machines, marked walkways, and a production line moving at a steady pace. On an automotive assembly line, the tact time, i.e., the seconds between one finished unit and the next, is less a target than a law of physics. If you watch the line long enough, you start to appreciate just how skilled these workers are. They know the exact sequence a component needs, the feel of a part seated correctly, what will go wrong three steps later if something is fractionally off now. I could only imagine how much more skilled they would become after a year or more on the line, and that this experience would surely count toward their careers, just as mine had always counted on my résumé.


I learned that most of the workers I was watching were apprentices, i.e., young trainees from ITIs, vocational streams, and Class 10th and 12th, who were brought onto the shop floor through India's National Apprenticeship Promotion Scheme (NAPS) for six months to two years of paid, hands-on training. Hundreds of thousands enter automotive shop floors this way every year, and a growing number are women, in a sector where their share of participation has historically sat below 10%. However, the shop floor we stood on had pushed well past that benchmark.



Why we were there

GBL was at a large automotive plant as part of its work on women’s participation in non-traditional sectors. Specifically, this field visit was intended to explore what happens when a blue-collar trainee (including NAPS trainees) finishes their tenure and walks back out into the job market. Would the experience they’d built travel with them? For any trainee, the answer matters, but for a woman navigating a sector that wasn't built with her in mind, it matters all the more.


Women workers of an auto-component manufacturing plant waiting in line.
Women workers of an auto-component manufacturing plant waiting in line.

Our broader fieldwork with ex-trainees and contractors up to that point had shown that, unfortunately, for most trainees, the skills did not travel with them. Their hard-earned skills didn’t usually help them compete in the job market even though their future employers value those skills. The intervention we were testing, a Skills Passport, was built on a simple premise: that skills actually learned by trainees on the shop floor should be legible in a way the next employer can read and act on. The idea existed before I arrived on the floor, but this specific field visit was meant to answer a more practical question: Does the system around it exist? Is there a process, a person, a moment at the end of someone's tenure where this passport could actually be produced, or would it land in a vacuum?


So we spent our days with supervisors, line managers, department heads, and the HR team, trying to understand how skills are assessed, how those assessments get recorded, and what happens on the last day a trainee walks out the gate.


What our initial design had missed

We had built the Skills Passport from the outside through interviews, surveys, value proposition canvases, and the works. Standing on the floor, I could feel the gap between what we had designed and how the system actually ran. The most precise record of a trainee's abilities wasn't on paper anywhere. It lived in the memories of the supervisors – people who could easily distinguish who steadied a line when it wobbled, who could be trusted on a difficult station, who could teach the person next to them. That knowledge was real, precise, and constantly in use – it just couldn't travel with the trainee when they left.


Male supervisor training a newly admitted woman worker.
Male supervisor training a newly admitted woman worker.

But the supervisor's knowledge staying behind was only one side of the gap. The trainees themselves often struggled to articulate what they'd built – not because they didn't know, but because nothing in the system had ever asked them to put it into words. So the question shifted: rather than relying on supervisors to capture what a trainee knew, could we help the trainee surface it themselves?


That question led us to a second realization, less about what we asked trainees and more about how we asked. Ask a trainee what skills they'd gained, and you'd get a generic answer, since the question was too abstract to hold onto. Ask them to walk you through their station, show you the sequence, tell you what breaks if a step is skipped, and the knowledge poured out, unprompted and specific. The articulation, as it turned out, wasn't the problem; the format was.




The moment that stayed with me

During our visits, the supervisors repeatedly mentioned a trainee called Padmaja before we even asked them to name their strongest one. What set her apart wasn't only that she had rotated through more stations than most. It was how she had done it, by sitting with her supervisors and learning to read the skill-tracking system itself, not just her own entries but the logic behind the whole thing. She understood the machines, the reasons behind each operation, and, crucially, that this knowledge was worth something.


So when her tenure was ending, she asked for a job, directly and unapologetically, in a setting where the standard exit process involves a clearance form and a returned set of tools. Asking directly for a job is rare for any trainee and rare still for women.


Padmaja had no document that could make her case. She had to carry the entire argument herself, relying on her confidence to speak up and her relationships. I kept thinking about the woman standing at the next station who might know just as much as Padmaja, work just as hard, but is quieter, or hasn't built the same rapport with her supervisor. Who would make her case? Who would advocate for her? Our team strongly believed that there was a system that could support workers to secure better jobs using their hard-earned skills. That gap, between what someone can do and what they can prove, is precisely what a Skills Passport is meant to close.


Understanding how a system works takes time, and can bring with it a certain humility about how your life might differ from the people involved in your research. On one of the field days, we wore the mandatory safety shoes: thick-soled, steel-toed. I felt a small relief peeling them off after a few hours, and immediately thought about what it would mean to wear them every day, for twelve months, at a pace that doesn't slow for weather or mood. How little of their endurance and capabilities appear in their experience letters today which often are restricted to "I worked in Engine Assembly for one year.

What I am still sitting with

I find myself thinking about how much of a manufacturing worker’s future depends on so much more than a single credential. How knowledge about a workforce so often lives informally, or how station assignments, even with the best intentions, can end up clustering in ways that don't always reflect what someone's capable of, a clustering that falls more often on women, whose records can end up narrower than their ability. These felt like questions the whole industry is still working through, shaped by how it has organized work for decades, and a document alone, however well designed, doesn't undo them.


When trainees were handed the passport mock-up, their faces lit up. For many of them, it was the first time an institution had said, "Here is what you did; here is what you can do; and we will put your name on it." That, I realized, wasn't a small thing – because this kind of recognition shows up in how you see your own work, in how you carry yourself, in the relationship you keep with a place long after you've left it.


While the brief was about a credential, the real story underneath it was about who gets to be seen and what it costs when the system might not be built to see you. And it left me with questions like: Who holds the knowledge in a system, and who gets to decide that it counts? Who can advocate for themselves and who gets left out if they can’t? And when we design something meant to help, are we changing the conditions that created the problem, or just making them easier to live with? I don't think a Skills Passport answers all of these, but I think it's pointed at the right ones.

bottom of page