The Tough-Love Talk: Mentoring A, and Why Accountability Is the Real Skill

Some mentees need you to teach them the craft. A already had it. She was a computer science major with a studio art minor, a Spotify engineer, the kind of person who builds an interactive digital horror comic for fun and visualizes music for the joy of it. By the time she landed in my Out in Tech mentorship, it was her third time through the program. Talent was never the question.

The question was follow-through. And that's the part nobody likes to talk about, so I'm going to.

The honest starting point

When A and I first mapped out where she was, she was refreshingly clear-eyed about it. The things she struggled with, in her own words, were writing longer responses, a lack of motivation and energy, not using time wisely, moving through the friction of doubt, and prioritization, knowing where to even start.

Read that list again. None of those are skill gaps. Every one of them is an accountability gap. She could make almost anything. What she couldn't reliably do was decide what to make, commit to it, and carry it across the finish line. She came in not really wanting to commit to working on any one thing, and on a long enough timeline, that's the thing that quietly sinks careers full of talent.

So I didn't start by teaching her a single design method. I started with a tough-love conversation about being organized and accountable for what she shipped.

Write one goal

The first real assignment I gave her wasn't a deliverable. It was a decision. Write one goal for our remaining time together.

Not a vague intention. One concrete, named goal she'd actually be accountable to. I even wrote a model in her voice so she'd know I meant it for real, not as a corporate exercise: a fire portfolio that showcases the work she makes, reflects who she is, and pulls other artists toward collaborating with her.

That sounds small. It isn't. For someone whose core struggle is "I don't want to commit to anything," choosing one goal and putting your name next to it is the entire ballgame. You can't be accountable to a blur. You can only be accountable to a thing you named out loud.

To-do lists are called backlogs for a reason

Once she had a goal, we built the machinery to actually reach it, borrowed straight from how good product teams work.

I told her the thing I tell everyone making this leap: in tech, your to-do list has a name. It's called a backlog. And a backlog isn't a guilt pile of everything you've ever meant to do. It's a prioritized, honest list where each item is either ready to work on or it isn't, and you get to decide which. We talked about what makes a task genuinely "ready," how to sequence work so you're not paralyzed by where to start, and the one that mattered most for her: how to keep a sustainable pace instead of swinging between burnout and guilt.

For someone moving through the friction of doubt, a backlog does something quietly powerful. It takes the giant, terrifying "do everything" and turns it into "do the next ready thing." That's a system you can be accountable to even on a low-energy day.

Meeting her where she actually was

Tough love only works if it comes with real support, not just higher expectations. A's challenges with focus and motivation were real, so the accountability system had to fit the person, not some fantasy of a person who never gets distracted.

So we got practical. We talked about brainstorming methods that fit how her brain actually works, post-its, Trello, ways to externalize her thinking so it wasn't all rattling around in her head at once. We talked about dictation and voice memos for when writing longer things felt like pushing a boulder. The point was never "try harder." The point was "let's build the scaffolding so the work you're capable of can actually get out of you."

That's the distinction I want to be clear about. The tough love wasn't about being hard on her. It was about refusing to pretend the follow-through didn't matter, and then helping her build the structure to deliver on it.

Where it landed

A did the work. She named the goal, ran the backlog, and made the portfolio real instead of theoretical. She went on to grad school and kept building a career as an engineer at Spotify, doing exactly the kind of tech-meets-art work she came in wanting.

I won't claim a single conversation handed her any of that. She had the talent the whole time. What the mentorship added was the part the talent couldn't supply on its own: a way to commit to something, be accountable for it, and finish.

What I took from it

The hardest thing to teach isn't a tool or a framework. You can learn Figma. You can learn personas and flows and prototyping. What's genuinely hard, and what actually separates people, is the ability to choose one thing, put your name on it, and be accountable for delivering it at a pace you can sustain.

When I mentor someone who has obvious talent but won't commit, the kindest thing I can do isn't more encouragement. It's the tough-love talk, followed immediately by the system that makes the accountability survivable. Talent gets you in the room. Accountability is what lets you build a career once you're there.

If you're brilliant at the making and stuck at the finishing, you don't need another skill. You need one named goal, a real backlog, and someone willing to hold you to it without burning you out. That part is coachable. I've watched it happen.