Leaving Microsoft meant giving up code reviews, unit tests and perfection
When she leaves Microsoft to build her own company, no one is there to review her code, so she trades extensive unit tests for features customers can try, bugs and all. Katia Gil Guzman, co-founder and CTO of the Paris startup Emera, shows what really changes for anyone weighing a safe job against their own idea: pace, mindset, money and personal time. So how do you know whether the leap is right for you?
Get the questions to ask yourself before trading a corporate job for a startup
Katia Gil Guzman, co-founder and CTO of Paris startup Emera and a former Microsoft software engineer, explains what changes when you move from a corporate job to building your own startup. She argues that founders must unlearn corporate processes and perfectionism, test every assumption with users, and plan honestly for lost personal time and at least a year without a normal income.
“For a startup, however, the most important thing is speed. If something breaks, it's fine because there is merely a pyramid of three cards and you can build it back again in no time.”
“You have to learn to be comfortable with things that are sometimes mediocre, but at least they have the merit of existing.”
What you will learn
Distinguish processes that save time later from processes that only add safety and cost time now.
Accept imperfect work that ships over polished work that never gets done.
Validate features with real users, for example through mockups, before assuming they are wanted.
Plan your finances for at least a year without a normal salary, using savings, benefits, teaching or freelancing.
Assess your risk, motivation and acceptable worst case before leaving a corporate job.
Key takeaways from the speaker
Don't try to replicate processes picked up in a corporate environment, create new ones
Be willing to unlearn everything you thought you knew
Evolving your mindset is not an option, it's a must
Details
Level
Beginner
Format
Talk
Technical depth
Non-technical
For
Founder, Mid-career, Early career
Length
18:57
Published
July 2022
Questions this talk answers
Should an early-stage startup copy corporate processes?
No. She says to create processes that save time in the future, but drop processes kept only for safety when they cost time to complete.
How long should a new founder expect to go without pay?
For most businesses, at least a year without earning a normal living, so plan for it with savings, benefits or side work such as teaching or freelancing.
Does work-life balance suffer when you start a company?
In her experience it deteriorates a lot at the beginning, at least for the first few months, and improves once things are set up and rolling.
Do you need a co-founder?
She recommends having one because there are many topics to cover alone; as the technical co-founder she knew nothing about sales, so a complementary skill set helps.
How do you know you are ready to start a startup?
You can never really be ready. For her, the sign was an urge she could no longer bear to ignore.
About this talk
Do you have this little voice in the back of your head that tells you that maybe you should try and build your own thing? But also this other voice, who reminds you that you cannot give up your comfortable situation to venture into the unknown? After all, you don't know the first thing about building a startup. But that shouldn't stop you. In this talk, we'll discuss what to expect when transitioning from the Corporate to the Startup world, and how the ways of working in those environments are completely different.
The feature she loved that users didn't get (58 s)
Questions to ask before you leap (70 s)
Hi, everyone. Thanks for joining. I'm Katia GIL GUZMAN and I'm the co-founder of an early stage startup called Emera. We're building a SaaS for agencies to manage their projects, teams, and clients. And we're based in Paris. And before that, I was working at Microsoft for three years. And even though I was in a team that kind of looked like a startup environment, Microsoft is still a big team.
It's a big corporation. And as a result, after I left Microsoft, I saw my life change a lot. And from what I've heard from my network, it would have been even worse had I worked in another company who's more traditional. And I'm guessing that if you're here, it's because there's a part of you who's curious about what building your own startup would look like. Maybe you have ideas you'd like to explore. Maybe you're just excited about the idea of being your own boss, or maybe you're just curious without any particular intention.
I'm also guessing that many of you. I'm also guessing that many of you feel like this simply cannot afford to quit the safe, stable corporate job, especially if you don't know what to expect. So in this talk, I'll talk about my experience leaving my corporate job to launch my startup. And I hope this can help you imagine what that would look like for you.
I would talk about what is the difference in working style, how the mindset is different, and also how it can affect your life. I also want to state that it's perfectly okay if you realize that the startup world is not for you, and that you should only do what makes sense for your specific situation. So in a corporate environment, you're by definition working within a specific frame. So the first thing I want to talk about are processes, because you're working with colleagues with direct reports, and/or managers, and you're part of a group. So there are rules to be respected. That means there usually are processes in place that you're supposed to follow. And there's also a certain pace that is set by a larger entity than yourself. The bigger our team or company, and the slower things move, which makes sense.
If you're trying to go from point A to point B, you will be much slower if you're a group of six people holding hands than if you're alone. And if you want to make sure other people follow in your footsteps and make it from point A to point B the same way you did, you will also have to document your every move.
And if you're following in other people's footsteps and want to do exactly what they're expecting of you, you'll have to read their instructions carefully. So that's what processes are meant for. In a big organization, you follow other people's guidelines, and you're expected to produce work in a way that is understandable by your colleagues and compliance with the company's policies.
And it's true for every role in the company. Because for a corporation, the most important thing is that there are no mistakes and that nothing breaks. Imagine a giant house of cards that took a long time to build with one cheeky card at the foundation. Everything could come crumbling down and it would be very bad. Very bad. For a startup, however, the most important thing is speed. If something breaks, it's fine because there is merely a pyramid of three cards and you can build it back again in no time.
That's why in a startup, there are usually no processes. Your goal is always to go as fast as possible. When you're a startup, when you're a startup, you usually don't have a lot of money to begin with and your only advantage compared to your competitors is speed. So that is especially true for startups that are in competitive markets and it's less true for solo partners or people building businesses that don't have a lot of competition.
But your time is always precious. So there's a real trade off between building processes that will help you go faster in working on your actual product or service. When I was working at Microsoft, I was working as an engineer and we had a lot of processes in place for shipping code. So we had to write extensive tests and have a code reviewed by at least two peers before it could be accepted.
Well, when I started working on my startup, I had to learn to let go of all of that because first of all, no one was there to review my code. And also I realized it was more important to develop new features for customers to try out than to spend a lot of time writing unit tests. So sure, it led to some issues and some bugs, but it also allowed me to learn about what customers wanted a lot faster.
So I'm not saying that there should not be any processes in startups, but processes are always changing and having a process just for safety when it actually doesn't save you any time or worse, it takes you time to complete is usually not beneficial. So yes to creating processes that will save you time in the future, but no to having processes would take time away from you. Everything you do in a startup should be in the goal of optimizing time or creating significant value.
So if you're uncomfortable with ambiguity and reluctant to adapting your processes from one day to the next, maybe a startup environment might not be the best environment for you. However, if you thrive in chaos and enjoy an ever changing environment, you'd be like a fish in the water. Also, again, the pace is very different. So when you're part of a group, you can count on others to help you.
And deadlines are usually defined well in advance. I'm not saying that you never have to do the occasional sprints when there's an expected task falling on your lap. We've all been there. And sometimes the stakes are just as high as what you would see in a startup environment. But when you're building your startup, usually it's up to you and a handful of people to do everything.
You cannot rely on your colleague to create the presentation for the client meeting next week. You cannot ask for help to fix that bug that you got two complaints about yesterday. So inevitably, you have to settle for lower quality. You have to ditch perfection. I used to think I could do anything and set the buy bar very high, but I had to learn to let go of things and prioritize because it's impossible even with the best intentions to get everything done.
You have to have to accept that perfection is not an option. You have to learn to be comfortable with things that are sometimes mediocre, but at least they have the merit of existing. So if you're thinking of starting your venture, make sure you're comfortable with that. Even if you're a perfectionist, make sure that you can let go of perfection and be happy with whatever you can get done in the short amount of time you have.
The other thing I learned when creating my startup is that I had misconceptions about a lot of things, especially when it came to what people want. So it's natural to think that whatever you think is great, other people will find it great, too. Well, it's wrong. So that's why when you're building a startup, when building something, you have to always test, fail and learn.
You cannot assume that something you're building is right for your target if you don't test it. And unless you're very lucky, the first few times you test it, there will be something wrong and you will have to iterate until you get it right. I remember one feature I was very proud about in our SaaS. I thought it was great because I could see myself using it and I thought the concept was awesome, but we tested it using mockups and users just didn't get it.
I insisted and I tried to explain to them what I could do for them, why it was awesome, but the reaction said it all. We had to kill this feature. So I had to accept that what I think is best is actually irrelevant and that the only thing I could do is learn from users. So one thing to keep in mind if you're thinking of leaving your corporate job to do your own thing, you have to be open minded and humble.
You have to accept that you don't know everything and be comfortable with doing things that you will probably throw away later just because they allow you to learn even the slightest thing. So when you build your own startups, the stakes are not the same as when you're working at your corporate job. So if you don't do the work, no one will punish you.
No one will hold you accountable. You and only you will be responsible for your success. That has its benefits, but also its drawbacks. You know what is best for you and you don't have to do things just because your boss said so, but also it can sometimes be hard and feel very lonely to be on your own and to motivate yourself.
It really depends on personality. Some people have no issues with disciplining themselves. Others struggle with it. Personally, I always struggle with procrastination, but having short deadlines help me stay motivated and do the work. If I know that someone is expecting something from me, I will do it in time, but I struggle with taking time to do work that only I'm expecting.
So I had to learn how to trick my brain into doing things even though no one is asking me to. So I imagine that for other people, it can be hard as well. So if you're thinking about being your own boss, really ask yourself if you'd be able to motivate yourself or to find people to hold you accountable.
I also wanted to talk about work-life balance because I think it's a really important topic and I imagine this can deter some people from starting the business. And to be honest, I'm not proud of what I'm going to say, but it is true that my work-life balance has deteriorated a lot since I started my company. I see it improving, though, as time goes by.
I think the hardest is at the beginning because you're a very small team and there are a lot of things to do, a lot of things to set in motion. And every moment you're not working on your startup, it feels like you're losing time. So I want to point out that I personally think it's wrong to think like that and that taking time off should be just as important as working on your startup.
But if you're thinking of starting your business, I think you should expect to see your work-life balance decline at the beginning, at least for the first few months. And once everything is set up and you've got the ball rolling, I think it's safe to say that you can go back to normal. But if I'm being honest, I don't see how you can get things started if you don't sacrifice a part of your personal time at the beginning.
So that's definitely something to take into account. If you're thinking about building your startup, you want to do it when the time is right for you. Of course, there's never a right time, but if you have a lot of commitments in the near future and you know you won't have a lot of time to dedicate to your venture, maybe it's best to wait until things cool down a bit.
So as you may know, when you're building a startup, at the beginning, you don't get paid. So depending on what you do, this can happen sooner rather than later. But for most businesses, you have to expect to spend at least a year without earning a normal living. So that's something that you should definitely plan for. I'm lucky enough to be French, and as a result, I get unemployment benefits.
That's actually what most entrepreneurs in France do. They can rely on the state to support them while they don't perceive any salary. However, I know that it's not an option in most countries, and even in France, not everyone can benefit from it. My co-founder, for example, doesn't have unemployment benefits and had to do occasional freelance work to pay the bills.
So depending on your situation, you might want to consider several options. If you can afford to go full time on your project without getting paid, whether because you can get financial help or because you have enough money saved, it's great. However, you might consider setting processes in place to get passive revenue or do occasional work like teaching or freelancing to support yourself during this time.
In any case, you should be prepared to lower your living standards for a while because you definitely have less money than before. So just make sure you're in a situation where that's possible before taking the jump. So I've talked to you about what are the differences you can expect in terms of working style, whether it's the difference in processes or pace, the change in mindset, whether it's learning to be open minded or learning to be your own boss and how it can affect your life, whether it's a decline in work life balance or a strain on finances.
But I also wanted to point out the pros and cons in my opinion to see what makes sense for your situation. So I'm not going to lie. It's hard. But I'm also not going to lie. It's not that hard. But I feel like you can find two types of opinion on the Internet. Those make it seem like building a startup is the obvious choice for anyone.
And you should definitely do it because it's way better than a boring nine to five job. And you have those who make it seem like building a startup is only for people who are ready to grind hard and that they are incredibly hardworking and wake up at 5 a.m. every day to make it work. So I'm exaggerating, of course, but you get what I mean.
And the truth is, it really depends on you and what you want. So building a startup does require you to sacrifice some of your personal time. It's a mental load and a responsibility different than what you would have at a regular job because you're responsible for your own outcomes. There's ambiguity all around, a lot of self-doubt, endless questions.
It can and will probably fail at some point. Statistically speaking, you are much more likely to fail than to succeed. But on the other hand, if it works, you get to be your own boss. You get to set the direction for your work and your life. And you can gain much more than what you would at a corporate job.
And if it doesn't work, you'll still learn a ton. You'll change your perspective and grow as a person. So I guess what you can ask yourself are these questions. What do you have to lose? Is it too risky in your situation? What is your true motivation? Is it just curiosity or is it something you feel like you have to do?
And what happens if you don't try? Will you regret it later? And what happens if it fails? What are your options? What is the worst case scenario you would be comfortable with? So I'll let you ask yourselves the questions. And thank you for your time. I do have time for a few questions. I think we have five minutes.
So if you have any questions, please ask them in the chat. I'll be happy to answer. Thank you, Michelle. Any questions? Don't be shy. You can ask in the chat so that you don't have to put on the mic if you're not comfortable with it. And just to, just out of curiosity, how many of you here are thinking about building a startup or are just, oh, there's a question.
Would you ever consider going back to corporate? Yes, actually, Marie. So that's actually a great question. To be completely honest with you, I applied to this talk when my startup was, I felt like my startup was going great. But in the last couple of weeks, I realized it wasn't going so great. So that's actually a question that I'm asking myself.
And I do see myself going back to the corporate world, even though I couldn't go to any corporation. It would have to be kind of like a startup environment. So I also have a question. Did you test your idea in some way before leaving a corporate job? No, actually, I joined a startup studio. So you go full time and then you test your ideas full time so that it goes much faster.
But that's definitely something you can do. If you don't have any kind of safety net and you want to make sure you do this without with the less risk possible, you can test before you leave your corporate job. How to decide about joining an existing startup regarding financial trade off salary? So for the, yeah, to join an existing startup, it really depends on what they offer.
So you can gain a lot if they give you shares, but it can also fail. It's less risky than building your own startup, but it's still a risk. So it depends. It depends on the project. It depends on what they offer you, really. I have a question about co-founders. I actually have, I had one co-founder and he, I was talking about the startup difficulties recently.
He actually just left the company. So we, I don't have any co-founders now. I definitely recommend having one because it's hard to do it on your own, especially since there are a lot of topics to cover. I'm the technical co-founder, so I didn't know anything about sales. So it definitely helps having someone that completes your skill set.
How do you know if you're ready to start a startup? You can never really be ready, I guess. It depends on a lot of factors. For me, it was just that I couldn't bear not to do it anymore. So I had to try it and that's what motivated me to start, actually. So if you are at this point where you feel this urge and you're not going to be satisfied until you scratch that urge, maybe that means it's the right time for you.
Well, we have one minute left. So thank you everyone for your questions. Please add me on LinkedIn if you have any more questions. My name is written on the, on the slide. There are not a lot of catchphrases, so I think you'll probably find me and I'll be happy to accept your request and to answer any questions left.
So thank you everyone. Bye.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
What really changes when you leave a corporate job to build a startup
Former Microsoft engineer Katia Gil Guzman on unlearning process, letting go of perfection and planning for a year without pay.
In short
Leaving a corporate job to found a startup changes far more than a job title, according to Katia Gil Guzman, who left a software engineering role at Microsoft to co-found the Paris startup Emera. She argues that corporate habits around process, pace and perfection have to be unlearned, that founders must test every assumption with users, and that the real costs show up in personal time and money. Her conclusion is neither cheerleading nor warning: whether to jump depends on your situation and your motivation.
Key takeaways
Don't try to replicate processes picked up in a corporate environment; create new ones.
Be willing to unlearn everything you thought you knew.
Evolving your mindset is not an option, it's a must.
Speed beats safety
Gil Guzman begins with processes. In a large organization you work inside a frame: colleagues, managers, rules and a pace set by an entity bigger than yourself. Processes exist so that others can follow your steps and so that your work stays understandable and compliant. For a corporation, she explains, the priority is that nothing breaks, like a giant house of cards that took years to build.
"For a startup, however, the most important thing is speed. If something breaks, it's fine because there is merely a pyramid of three cards and you can build it back again in no time." (2:47)
At Microsoft, shipping code meant extensive tests and review by at least two peers. At her startup, no one was there to review her code, and she realised that building features customers could try mattered more than writing unit tests. It caused some bugs, but it taught her what customers wanted much faster. She is not against process, only against process that costs more time than it saves: "Everything you do in a startup should be in the goal of optimizing time or creating significant value." (4:30)
Ditching perfection
The pace is different too. In a corporation you can count on colleagues and deadlines are usually set well in advance. In a startup, a handful of people do everything. You cannot hand the client presentation to a colleague or ask someone else to fix the bug that drew two complaints yesterday. Gil Guzman, who describes herself as someone who used to set the bar very high, had to learn to prioritize.
"You have to learn to be comfortable with things that are sometimes mediocre, but at least they have the merit of existing." (6:18)
Her advice to perfectionists considering a venture is to make sure they can let go and be happy with whatever they can finish in the little time they have. People who thrive in chaos and an ever-changing environment, she says, will feel like a fish in water.
Your opinion matters less than your users'
One of her biggest lessons was how wrong her assumptions about what people want could be. She recalls a feature in Emera's SaaS that she was proud of because she could imagine using it herself. When the team tested it with mockups, users simply did not get it, and even her explanations could not change their reaction. The feature was killed.
"So I had to accept that what I think is best is actually irrelevant and that the only thing I could do is learn from users." (7:36)
The mindset this demands is open and humble: accept that you do not know everything and be comfortable building things you will probably throw away, because they teach you something.
Being your own boss, and what it costs
Without a manager, no one punishes you for not doing the work. "No one will hold you accountable. You and only you will be responsible for your success." (8:27) Gil Guzman admits she struggles with procrastination and works best when someone expects something from her, so she has had to learn to trick her brain into doing work no one has asked for. She urges would-be founders to ask whether they can motivate themselves or find people to hold them accountable.
She is equally candid about personal life: "And to be honest, I'm not proud of what I'm going to say, but it is true that my work-life balance has deteriorated a lot since I started my company." (9:33) She believes time off should matter as much as work, yet expects balance to decline for at least the first few months.
Money is the other strain. "But for most businesses, you have to expect to spend at least a year without earning a normal living." (11:06) As a French citizen she receives unemployment benefits, which she says most entrepreneurs in France rely on, while her co-founder took freelance work to pay the bills. Options include savings, passive revenue, teaching or freelancing, along with a willingness to lower living standards for a while.
Hard, but not that hard
Gil Guzman pushes back on two caricatures found online: startups as the obvious escape from a boring nine-to-five, and startups as only for people who grind from 5 a.m. "But I'm also not going to lie. It's not that hard." (12:50) Building a company brings ambiguity, self-doubt and, statistically speaking as she put it, a higher chance of failing than succeeding. But it also lets you set the direction of your work and life, and even failure teaches a great deal.
She closes with questions to ask yourself: What do you have to lose? What is your true motivation? Will you regret not trying? What worst case could you live with?
The Q&A adds rare honesty. She shares that her startup had recently become harder, that her co-founder had just left, and that she could see herself returning to a startup-like corporate environment. She still recommends having a co-founder whose skills complement yours, and on readiness she says: "For me, it was just that I couldn't bear not to do it anymore." (17:47)
Watch the talk
"From the Corporate to the Startup world" by Katia Gil Guzman, about 19 minutes: https://www.womentech.net/video/corporate-startup-world-katia-gil-guzman
About the speaker
Katia Gil Guzman is Chief Technology Officer at Emera, a startup she co-founded in April 2021 to help businesses process their clients' requests effortlessly and collaborate more efficiently. Before that, she worked at Microsoft for three years as a Software Engineer in a customer-facing team, building innovative solutions with cutting-edge cloud technologies.
Questions this talk answers
Should an early-stage startup copy corporate processes?
How long should a new founder expect to go without pay?
Does work-life balance suffer when you start a company?
Do you need a co-founder?
How do you know you are ready to start a startup?
Drafted with AI from the talk transcript. Editor review pending.
Cite this talk
Katia GIL GUZMAN. "From the Corporate to the Startup world." WomenTech Network, 2022. https://www.womentech.net/video/corporate-startup-world-katia-gil-guzman