How I Built My First Team (And Every Mistake I Made)

The hiring mistakes I’ve seen — and made — follow a painfully consistent pattern. At the 360 Innovation Lab, we hired a Head of Innovation with impeccable credentials: impressive CV, great references, polished interview. On paper, a perfect hire. In practice, they couldn’t execute. The gap between impressive credentials and actual delivery was enormous, and it cost us months of lost momentum.

We also had an ego-driven employee who spent more energy bashing management than doing the work. The cultural damage spread faster than any individual’s contribution could offset.

These weren’t isolated incidents. They were symptoms of hiring mistakes I kept repeating until I finally understood the underlying patterns.

Every mistake I made building my first team was a version of this fundamental error: treating hiring as a solution to problems that were actually management problems, process problems, or clarity problems. The hire doesn’t fix the mess. You fix the mess, then the hire maintains the fix.

Here’s the complete, unvarnished story of building my first team — every mistake, every lesson, and what I’d do differently.

Mistake #1: Hiring for Relief Instead of for a Role

The motivation behind bad hires is almost always the same: exhaustion. You’re working sixty-hour weeks, drowning in tasks, and desperate for someone — anyone — to take some of the burden. So you hire the first qualified person who says yes, give them a general mandate, and expect relief.

This is the most common hiring mistake among solo founders, and it fails for a specific reason: when you hire for relief, you haven’t defined what the person actually does. You just want less on your plate. But “less on my plate” isn’t a job description. It’s a feeling you want to have.

The fix I learned: never hire a person. Hire a role. Define the role before you look for a person. The role should have: a specific title, three to five core responsibilities (not vague — specific, measurable tasks), clear success criteria (how will you know the person is doing the role well?), and documented processes for each responsibility.

The hires that worked in my experience were always the ones where the role was defined in a one-page document before the job was posted. Specific responsibilities. Clear success criteria. Documented processes. The person wasn’t better — the role definition was better.

Mistake #2: Hiring a Mini-Me

The second mistake was subtler. When hiring, I unconsciously looked for someone who thought, worked, and communicated like me. I wanted a mini-me because managing someone different felt risky. What if their approach was wrong? What if their style didn’t match the brand?

The person I hired was smart and capable but essentially a copy of my own working style. The result: we agreed on everything, we both had the same blind spots, and the team had exactly zero diversity of perspective.

The better approach, which I learned from observing the team dynamics at Startup Burgenland: hire for complementary strengths, not for similarity. If you’re big-picture, hire someone detail-oriented. If you’re fast-moving, hire someone methodical. If you’re externally focused (sales, marketing, client work), hire someone internally focused (operations, systems, quality control).

The discomfort of managing someone who works differently from you is the price of having a team that’s genuinely stronger than you alone. The comfort of managing someone just like you is the price of having a team with all the same weaknesses as you alone.

Mistake #3: Underpaying and Over-Expecting

In my first years of building a team, I hired cheap. I rationalized it as being “budget-conscious” or “bootstrapping.” What I was actually doing was undervaluing the roles I was filling and then being disappointed when the people in those roles delivered at a level commensurate with their compensation.

The brutal math: if you pay 60% of market rate, you get people who are either building their resume (and will leave as soon as they can), desperate (and will take any job, including yours, regardless of fit), or junior enough that the pay is appropriate but the role expectations aren’t.

I learned this the expensive way. When you pay well below market rate, you get people who are good but not committed — because they’re simultaneously looking for better-paying opportunities. When they leave for a significantly higher salary elsewhere, the recruiting cost, training cost, and lost productivity of replacing them exceeds the amount you would have spent just paying market rate from the start.

Now my approach: pay at or slightly above market rate for every role, and be realistic about what that rate commands. If you can’t afford market rate for the role you need, you’re not ready to hire for that role. Either simplify the role until the budget matches, or wait until revenue justifies the investment.

This connects to the profit-first financial system — your operating account tells you what you can actually afford to spend on team, and your profit allocation ensures you’re not hiring at the expense of business sustainability.

Mistake #4: No Onboarding Process

For my first three hires, “onboarding” consisted of: “Here’s your desk. Here’s Slack. Ask me if you have questions.” I assumed smart people would figure things out quickly because that’s what I did when I started. But I started my own business — of course I understood the context. A new employee doesn’t have years of context about the business, the customers, the processes, or the culture.

The absence of onboarding produced a predictable outcome: each new person spent their first two to three weeks confused, unproductive, and increasingly anxious that they were failing. By the time they started to figure things out, the initial anxiety had already damaged their confidence and our working relationship.

The onboarding process I eventually built:

Day 1: Business overview (what we do, who we serve, how we make money), role overview (what they specifically do), tools and access setup (everything they need to do their job).

Week 1: Shadowing. New hires spend the first week observing me or a senior team member doing the work they’ll eventually take over. They watch, ask questions, and take notes. No independent work yet.

Week 2: Guided work. They perform their tasks with me available for questions. Every task has a documented process they can reference. I review their work at the end of each day and provide specific feedback.

Week 3: Independent work with check-ins. They work independently but we meet for thirty minutes daily to address questions and review output. This gradually decreases to weekly check-ins by month two.

This three-week onboarding process costs time upfront but saves weeks of confusion, reduces early turnover, and gets new team members to productive independence faster than the “figure it out” approach.

Mistake #5: Avoiding Difficult Conversations

I’m naturally conflict-averse. When a team member wasn’t performing well, my instinct was to work around the problem rather than address it directly. I’d take back tasks they were struggling with rather than coaching them. I’d lower my expectations quietly rather than communicating the gap clearly. I’d tell myself “it’s not that bad” until it was that bad.

This avoidance was unfair to everyone. The underperforming team member didn’t know they were underperforming because I hadn’t told them. The rest of the team saw the underperformance being tolerated and adjusted their own standards downward. And I was absorbing extra work that should have been addressed through management, not heroics.

The breakthrough came from a mentor who said: “The conversation you’re avoiding is exactly the conversation that would fix the problem.” She was right. Every time I finally had the difficult conversation — “Here’s what I’m seeing. Here’s the standard. Here’s the gap. How can we close it?” — the problem either got fixed or it became clear that the person wasn’t right for the role. Both outcomes were better than indefinite avoidance.

Now I follow a rule: if a performance issue persists for more than two weeks, it gets a direct conversation. Not a vague hint. Not a passive-aggressive email. A direct, kind, specific conversation about the gap between expectation and reality.

Mistake #6: No Culture by Design

For my first two years of team building, “culture” was an accident. It was whatever happened to emerge from the personalities in the room. Sometimes that produced a great working environment. Sometimes it didn’t. The randomness was the problem — culture should be designed, not discovered.

The culture I eventually built was based on three explicit values that I communicated to every team member:

Value 1: Ship over perfect. We ship on time, even when the work isn’t perfect, because imperfect work in front of customers generates feedback that perfect-but-delayed work never will. This aligned with the ship it ugly philosophy that I’d already adopted for my own work.

Value 2: Own the problem. If you notice something wrong, you own it until it’s fixed or explicitly handed off. Nobody says “that’s not my job.” Everybody says “I’ll take care of it” or “I’ll make sure the right person knows.”

Value 3: Honest over comfortable. If you disagree, say so. If you made a mistake, say so. If you don’t understand, say so. The social cost of honesty should be zero. The social cost of politeness that hides problems should be high.

These values aren’t aspirational posters. They’re behavioral expectations that I reinforce daily through my own behavior (if I expect honesty, I must model honesty about my own mistakes) and through specific feedback when behavior aligns or doesn’t align with the values.

What I’d Do If I Were Starting Over

If I could rebuild my first team from scratch, knowing what I know now:

1. Don’t hire until you have documented processes. If you can’t write down exactly what the person will do, you’re not ready to hire them.
2. Hire for the role, not for relief. Define responsibilities and success criteria before you post the job.
3. Pay market rate or wait. Underpaying costs more in turnover than overpaying costs in salary.
4. Build a real onboarding process. Three weeks of structured onboarding saves months of confusion.
5. Have difficult conversations within two weeks of noticing problems. Every delay makes the conversation harder and the problem worse.
6. Define culture explicitly. Three to five values, communicated constantly, reinforced through behavior.

The velocity principle applies to team building too: move fast, but move deliberately. A fast hire without preparation wastes more time than a deliberate hire with proper setup.

Takeaways

1. Never hire a person — hire a defined role with specific responsibilities, success criteria, and documented processes. If you can’t define the role in one page, you’re not ready to hire.
2. Hire for complementary strengths, not similarity. The discomfort of managing someone who works differently from you is worth the benefit of a team without your blind spots.
3. Pay market rate. Below-market hires leave, underperform, or both — and the replacement cost exceeds the salary savings every time.
4. Invest three weeks in structured onboarding: week one shadowing, week two guided work with daily review, week three independent work with daily check-ins tapering to weekly.
5. Address performance problems within two weeks through direct, kind, specific conversations. Avoidance is unfair to the underperformer, demoralizing to the rest of the team, and expensive for you.