Latest / KAJ Business & Money LIVE / Vygandas Pliasas Shares 3 CRUCIAL Tips for Building Winning Tech Teams
Transcript
- 0:25Speaker 1: Welcome to this very special edition of the Cage A
- 0:28Speaker 1: masterclass live the show which ensures that you profit from
- 0:31Speaker 1: your time spent year with experts, either through their industry
- 0:34Speaker 1: in sites information or simply learning from them.
- 0:39Speaker 2: And today we have.
- 0:41Speaker 1: Begun this plus US season Fractional CTO and software development
- 0:45Speaker 1: executive eighteen years of experience, specializes in scaling startups, building
- 0:51Speaker 1: dedicated remote teams, and driving technical innovation.
- 0:55Speaker 2: Welcome to the show, Wigan US.
- 0:58Speaker 3: Hello everybody, Thank you very much.
- 1:01Speaker 2: You're welcome.
- 1:02Speaker 1: Welcome to the show began thus, Welcome to India in
- 1:05Speaker 1: this online form and I'm sure not just in India,
- 1:08Speaker 1: but a lot of people across the globe will benefit
- 1:11Speaker 1: from what we are going to talk right now. We'll
- 1:13Speaker 1: learn from you about scaling text teams or startup success.
- 1:18Speaker 2: We'll learn all that about from you.
- 1:20Speaker 1: But before that begun, thus, if you can tell us
- 1:23Speaker 1: about a bit about your journey, your background, so that
- 1:26Speaker 1: people know who they are listening to.
- 1:29Speaker 3: Okay, of course, thank you, good to be here. So
- 1:34Speaker 3: my whole technical journey started when I was thirteen years old.
- 1:40Speaker 3: I've been spending money playing games and the owner of
- 1:42Speaker 3: the play is basically suggested to learn programming, and that's
- 1:46Speaker 3: how it started. So we've been doing later quite serious
- 1:51Speaker 3: projects for money when I was like before eighteen years old,
- 1:56Speaker 3: and basically that's how it started. And then they went
- 2:00Speaker 3: to university, finished masters in engineering in software engineering, and
- 2:09Speaker 3: basically that's how my journey started. So being hands on
- 2:12Speaker 3: developer and then became team lead, then became R and
- 2:19Speaker 3: D manager, then became you know, engineering manager, head of
- 2:24Speaker 3: engineering fractional CTO, and that's how my whole career focus
- 2:31Speaker 3: shifted towards executive and consulting fractional CTO and helping companies
- 2:37Speaker 3: figure out and like fixing processes in the startups, in
- 2:43Speaker 3: the organizations. I think that part of it is basically
- 2:47Speaker 3: because I've quite seen quite a lot of organizational structures,
- 2:52Speaker 3: what works, what doesn't work, you know, how people interact
- 2:56Speaker 3: with everything each other, project managers and more or less.
- 3:01Speaker 3: I think that's my journey to the point where I am.
- 3:05Speaker 2: Now absolutely absolutely begin that. So, as a CTO.
- 3:13Speaker 1: Sitting in today's the sixteenth day of twenty twenty five,
- 3:18Speaker 1: where do you see this role of CEO?
- 3:21Speaker 2: Is it expanding, is it contracting?
- 3:25Speaker 1: Will the CDO position be there with a lot of
- 3:28Speaker 1: you know bots and AI coming in.
- 3:30Speaker 2: How do you see the role of a CDO today.
- 3:34Speaker 3: Well, depends about which kind of CITO you're talking about.
- 3:39Speaker 3: There are two. One is technical which is basically very
- 3:45Speaker 3: cool developer went to leading teams and basically figuring out
- 3:50Speaker 3: all the technical stuff. And there's managerial CTO, which is
- 3:54Speaker 3: more about strategy like high level picture direction and reporting
- 3:58Speaker 3: back to the boat. So I think both will stay
- 4:04Speaker 3: because at least from how much I tried developing with
- 4:10Speaker 3: an AI myself, it still needs a lot of guidance,
- 4:14Speaker 3: direction and you really need to understand what you're doing
- 4:18Speaker 3: with it because it will it will trick you into
- 4:22Speaker 3: something that will burn all your time in development. And
- 4:26Speaker 3: from strategic point of view, it well for at this
- 4:32Speaker 3: day at least it gives you more or less very
- 4:35Speaker 3: default strategies, very like boiler plate, and it's very generic
- 4:40Speaker 3: and to figure out new things, competitive approaches and basically
- 4:46Speaker 3: solving existing problems. I don't see how it would replace
- 4:52Speaker 3: that kind of level of you know, work and execution.
- 4:57Speaker 3: So at least this year we should be safe.
- 5:02Speaker 2: You should be safe.
- 5:02Speaker 1: But in terms of work, how should we understand what
- 5:06Speaker 1: the work of a CDO is today? What is the
- 5:09Speaker 1: work that you are generally, you know, engaging with your clients.
- 5:14Speaker 1: Is it again turning into you know, you talked about
- 5:17Speaker 1: fractional CDEO.
- 5:19Speaker 2: If that role itself.
- 5:21Speaker 1: Is becoming much more, much more constricted, then do you
- 5:26Speaker 1: think it will be only about fractional CEOs in the
- 5:29Speaker 1: future and the people or organizations will not look for
- 5:33Speaker 1: having a proper CITO in their organizations itself. I want
- 5:38Speaker 1: to understand this whole changing landscape. How is it happening
- 5:42Speaker 1: in Lithuania in your country?
- 5:45Speaker 3: Wow? Funny that I'm working mostly with the UK and
- 5:50Speaker 3: the United States myself, I have like one client in Lithania,
- 5:56Speaker 3: so it's kind of hard to tell us. I can
- 5:58Speaker 3: talk more about approach, how it's going to how it
- 6:02Speaker 3: is happening and well. There are also a couple of
- 6:08Speaker 3: differences from CTO and fractional CTO. The main difference is
- 6:14Speaker 3: that not fractional CTO focus on long term see conversions
- 6:25Speaker 3: and change management within the team. So basically, the implement
- 6:30Speaker 3: big plans. Let's see the how two hundred three hundred
- 6:34Speaker 3: developers including leads and managers and directors, Let's say, and
- 6:39Speaker 3: then they do that change. Let's see they need to
- 6:42Speaker 3: change how the structure is made, who's who's boss, you know,
- 6:49Speaker 3: and and they implement that. So it's multiple years. That's
- 6:52Speaker 3: a long term position. A fractional CTO, on the other hand,
- 6:56Speaker 3: is small, like a consultant. Fractional CITO comes in and
- 7:01Speaker 3: figures out what's wrong, what should be the correct approach,
- 7:05Speaker 3: what to do, gives a huge report on the findings.
- 7:11Speaker 3: So what doesn't work, how people feel, what they think
- 7:14Speaker 3: is broken, well they think is not broken. What's the
- 7:17Speaker 3: current process, the software life cycle, product development life cycle,
- 7:24Speaker 3: where's the communication may be broken, and all the impediments,
- 7:28Speaker 3: all of these things. All of that is collected and
- 7:31Speaker 3: then work again with the people to figure out what
- 7:34Speaker 3: could be the correct approach to solve it, iterating talking
- 7:40Speaker 3: with them. Let's say I give the initial report on
- 7:44Speaker 3: how I see the problem. Then all the heads VP's
- 7:49Speaker 3: high level managers reads it and tell us, okay, I
- 7:52Speaker 3: agree with this part, I don't agree with this part,
- 7:54Speaker 3: and then okay, tell me how do you see it
- 7:58Speaker 3: if you do not agree with it? And that way
- 8:01Speaker 3: we figure out what is the actual problem, where the
- 8:05Speaker 3: roots are, and then come up with proper strategy on
- 8:11Speaker 3: how to approach it, and that strategy is long term
- 8:16Speaker 3: and usually is executed by not fractional people like maybe CEO,
- 8:21Speaker 3: maybe had maybe VP of engineering, maybe you know somebody else,
- 8:25Speaker 3: but it's a different approach. So they invite fractional when
- 8:29Speaker 3: they want like a second opinion, or they don't have
- 8:32Speaker 3: enough time to go and figure out all of those things.
- 8:37Speaker 1: Right, So it's it's it's a world of startups now
- 8:40Speaker 1: a lot of work. So is it is it that
- 8:42Speaker 1: you are getting a lot of work in terms of startups?
- 8:45Speaker 1: Space will come to the team building part, but is
- 8:48Speaker 1: it I want to gauge that what's happening in the
- 8:50Speaker 1: industry or is it less of work?
- 8:53Speaker 2: I want to understand your challenges.
- 8:56Speaker 1: Either in lead generation, either in doing your work in
- 9:00Speaker 1: terms of you know, the practical things that you want
- 9:03Speaker 1: to do on the ground, or are you being called
- 9:05Speaker 1: only when situation is very very.
- 9:08Speaker 2: You know bad.
- 9:09Speaker 3: When it's bad, you basically a cleaner fixer. Nobody calls
- 9:17Speaker 3: me when it's good.
- 9:20Speaker 2: That's why I asked the challenges beginners.
- 9:23Speaker 3: Yes, yes, it's basically you get dropped into the fire
- 9:26Speaker 3: and then you know, good luck figure it out. That's
- 9:29Speaker 3: the job. Basically, it's never never been that easy. Overall,
- 9:37Speaker 3: twenty twenty four were down with all those mass layoffs
- 9:41Speaker 3: and everything, so it was very calm. Now I see movement,
- 9:46Speaker 3: people more getting more interested, and it seems to getting
- 9:50Speaker 3: back on track.
- 9:50Speaker 2: Butad like.
- 9:52Speaker 3: Twenty four was resting time.
- 9:56Speaker 1: Let's say, right right now, let's look at this whole
- 10:02Speaker 1: situation about teams in case you are a CEO, but
- 10:07Speaker 1: you must you know about the ins and outs of
- 10:09Speaker 1: any organization that in terms of team building and you know,
- 10:14Speaker 1: building teams or scaling tech teams for startups? Are they
- 10:21Speaker 1: happening very well? Because startups firstly have a lot of challenges.
- 10:24Speaker 1: They do not have much time to experiment. They want
- 10:28Speaker 1: teams to immediately perform. Whereas you may only hire team
- 10:33Speaker 1: in terms of you know, by their name or their
- 10:36Speaker 1: past record. They must be working in big companies very
- 10:39Speaker 1: small companies. You have to hit the ground running, you know,
- 10:43Speaker 1: and perform as a CTO.
- 10:46Speaker 2: How do you see this? Is it a challenge for
- 10:49Speaker 2: a lot of startups.
- 10:50Speaker 1: How do you get that sort of a team, you know,
- 10:54Speaker 1: especially a tech team, and get your startup to scale up?
- 10:59Speaker 2: How do they do?
- 11:00Speaker 1: Because you have all that, you have the market to
- 11:02Speaker 1: take care of your got other aspects to take care of.
- 11:06Speaker 1: And yeah, you have a team beat you do not
- 11:08Speaker 1: know about, they do not know about. They may be good,
- 11:10Speaker 1: but it takes time to you know, gel into the
- 11:13Speaker 1: scheme of things. I want to understand your perspective from
- 11:16Speaker 1: a CTU and as trefractural cito, how do you get
- 11:20Speaker 1: things done from a team like that?
- 11:24Speaker 3: Okay, so everybody says they want a change and we
- 11:29Speaker 3: want to make it better, but it doesn't mean that
- 11:31Speaker 3: they want to change themselves. I think I didn't see
- 11:34Speaker 3: the meme about that on LinkedIn somewhere the other day.
- 11:39Speaker 3: So the very beginning, how the team appears in the company,
- 11:45Speaker 3: I'd say it's more or less similar in a high level.
- 11:51Speaker 3: So initially you have an idea and then you get
- 11:56Speaker 3: done somehow. Maybe it's a freelanswer. Maybe it's an agent,
- 12:00Speaker 3: see yeah, more or less something like that. Maybe you
- 12:03Speaker 3: had a developer, and then there is that happy moment
- 12:08Speaker 3: where you see that there is a market fit something
- 12:12Speaker 3: like that, like a good indicator, and then you need
- 12:15Speaker 3: to scale. But at that moment you already get clients
- 12:19Speaker 3: who are waiting, so everything is on fire, you know,
- 12:23Speaker 3: like you need to fix this fix that. The other
- 12:26Speaker 3: clients will join only if you implement that feature X.
- 12:30Speaker 3: Let's say nobody wants to wait, so you just put
- 12:34Speaker 3: in more freelancers, more people, like get it done somehow,
- 12:38Speaker 3: let's ship it. Let's get more clients, you know. And
- 12:41Speaker 3: then when it starts to stabilize that there's a budget
- 12:48Speaker 3: to make it right. But it's a mess in the team.
- 12:53Speaker 3: There's no proper communication, Like CEO is landing all the
- 12:56Speaker 3: ideas to developers. They shift their attention. They take whatever
- 13:01Speaker 3: CEO says to do, like this is important. So the
- 13:05Speaker 3: body fult drop everything else and take the new thing.
- 13:09Speaker 3: And then after a couple of weeks, let's say, see
- 13:11Speaker 3: how it comes back and says that where's that other
- 13:14Speaker 3: thing from the past that you were working on?
- 13:16Speaker 4: And everybody's like, well, you told us to drop it,
- 13:19Speaker 4: you know kind of and and and then they start
- 13:22Speaker 4: to realize that probably something should be better than it
- 13:28Speaker 4: is now. And you know, the question is, so how
- 13:31Speaker 4: the other organizations with like hundreds of people managed to
- 13:35Speaker 4: deal with it if we, like a small team cannot
- 13:38Speaker 4: deal with it properly, you know. And then they keep
- 13:42Speaker 4: growing and and then eventually they hire some fractional CEOs
- 13:47Speaker 4: like okay, make it right, put everybody into correct roles,
- 13:51Speaker 4: define what they're supposed to be doing.
- 13:53Speaker 3: You know, work with the people. Working with the people,
- 13:57Speaker 3: you know, it depends. Sometimes there might be a change
- 14:02Speaker 3: in their role and what they will be doing. So
- 14:05Speaker 3: you know, maybe they won't tell you directly, but it's
- 14:09Speaker 3: like when you tell how you will need to write
- 14:11Speaker 3: much more documentation into those requirements for features and as
- 14:16Speaker 3: that look, you know, you see that they don't like
- 14:20Speaker 3: that idea that there's more work, but you try to
- 14:25Speaker 3: figure out how to make it not too painful. So
- 14:29Speaker 3: overall the ideas to make life easier for everybody, not
- 14:33Speaker 3: like just put more work, you know, and hope for
- 14:36Speaker 3: the best that it will not happen if it's like
- 14:39Speaker 3: it's if it's very hard and doesn't make sense for people,
- 14:41Speaker 3: they will just not do it when you leave. So,
- 14:44Speaker 3: you know, that's the complexity of work. You work with people.
- 14:48Speaker 3: You need to understand the emotion, the motivation. You need
- 14:53Speaker 3: to understand the team culture, what is it you know,
- 14:57Speaker 3: what will be acceptable, how the intern act with each other.
- 15:01Speaker 3: You know, so it is kind of dangerous. I think
- 15:05Speaker 3: you cannot rush with decisions. You cannot do stupid things.
- 15:10Speaker 3: Its really takes time to think about it. How to make.
- 15:15Speaker 1: Right absolutely absolutely, and tell me this scenario. See when
- 15:21Speaker 1: you talk about your team. Till now we are talking
- 15:24Speaker 1: about humans. But very soon in twenty twenty five, already
- 15:28Speaker 1: some firms have started talking about you'd have you know,
- 15:32Speaker 1: AI as your team member, legitimate team member, as a CTO.
- 15:38Speaker 2: How do you prepare for such a.
- 15:40Speaker 1: Situation, you know, a human cito taking care of the
- 15:45Speaker 1: human part of the team and the AI part of
- 15:48Speaker 1: the team.
- 15:49Speaker 2: And look at this scenario, it's not very far.
- 15:53Speaker 3: Oh yes, definitely. Well, I my own view is a
- 15:58Speaker 3: bit more conservative, and so I you know, in my job,
- 16:04Speaker 3: you cannot rush in new things if it's not tested
- 16:08Speaker 3: and if it has a lot of like scope, it
- 16:11Speaker 3: would replace something, you know, because you never know how
- 16:15Speaker 3: it will turn out. So I look a bit more carefully.
- 16:20Speaker 3: And what I do I always push people like use it.
- 16:26Speaker 3: But it's a tool. It's not replacement of your head.
- 16:31Speaker 3: You are the head. It is a tool and you
- 16:35Speaker 3: need to use it as a tool, like ask it
- 16:38Speaker 3: for help, give it context, show code, show situation. It
- 16:42Speaker 3: will give you ideas, but it will not give you
- 16:46Speaker 3: the context to what it is missing, so you won't know.
- 16:49Speaker 3: It will give you an answer, but it will not
- 16:52Speaker 3: tell you Okay, here's the idea, but I do not
- 16:55Speaker 3: talk about this, this and that thing that could go wrong. Yes,
- 17:00Speaker 3: so people still are like managers of that tool developers.
- 17:06Speaker 3: There are tools like that can look into Jira that
- 17:09Speaker 3: you can look what you forgot to write down for
- 17:12Speaker 3: the you know, stories, epics, portfolio items, but still you
- 17:17Speaker 3: are the person who writes it down. It cannot think
- 17:21Speaker 3: on your behalf because AI doesn't know the big picture,
- 17:25Speaker 3: the market, the direction where you're going. It always has
- 17:29Speaker 3: like a year old data in it something like that.
- 17:32Speaker 3: For there was also the I even try like to
- 17:36Speaker 3: make a complex worker in Java that would be synchronized
- 17:40Speaker 3: across multiple servers and it would have grouped jobs like
- 17:44Speaker 3: one worker can do only one group and it's throttled,
- 17:48Speaker 3: so all that stuff. It's a nightmare to do it
- 17:50Speaker 3: with an AI, and I've like spent hours and hours
- 17:54Speaker 3: and they started thinking, well, I probably would have done
- 17:56Speaker 3: it already because get into the loop. Because it's huge
- 18:00Speaker 3: complexity and it doesn't remember all of the things, so
- 18:04Speaker 3: you still need to use it properly, it won't replace
- 18:09Speaker 3: you at least I don't see it how it would
- 18:11Speaker 3: happen yet.
- 18:14Speaker 1: Right, let's look at another's especially for startups having remote teams.
- 18:19Speaker 2: And now it's a thing.
- 18:21Speaker 1: Because you're either remote teams can be you know in
- 18:24Speaker 1: terms of cost effectiveness, and either because they might be
- 18:27Speaker 1: good people who are in some other part of the
- 18:29Speaker 1: world and you want to make the best of that situation.
- 18:33Speaker 1: How do you see you know, the maximum benefit best
- 18:38Speaker 1: way to build a remote team?
- 18:40Speaker 2: How do you do that?
- 18:41Speaker 1: Especially for the startup, How do you lure them because
- 18:44Speaker 1: you either do not have money or you have lots
- 18:46Speaker 1: of investor money, but whatever way it is, how you
- 18:49Speaker 1: get the right team and dedicate a team for that?
- 18:52Speaker 1: How do you manage that? What's your advice to start
- 18:55Speaker 1: up from this?
- 18:57Speaker 3: Well, with the remote team, you either can say or
- 19:00Speaker 3: you can get stronger talent for the same budget. Then
- 19:04Speaker 3: you could find it locally, so it has its advantage.
- 19:09Speaker 3: The difference is you need to be careful with the
- 19:14Speaker 3: mindset how you're going to manage it because it's very
- 19:18Speaker 3: different from on site approach. If the stakeholders decide to
- 19:24Speaker 3: go remote approach, everything should be planned around it. Hybrid
- 19:29Speaker 3: approach is even worse in my opinion, especially if we
- 19:33Speaker 3: are talking about people in different countries. Let's say you
- 19:37Speaker 3: have an office in London, you have somebody like me
- 19:40Speaker 3: in Lithuania. You have somebody in Germany, Sweden, India, Brazil
- 19:46Speaker 3: for example, maybe some sales in the United States, something
- 19:50Speaker 3: like that. You cannot try to hybrid it and like
- 19:54Speaker 3: only talk with your colleagues in one office and then
- 19:58Speaker 3: drop everybody else. I think before even building this is
- 20:04Speaker 3: the theme I start talking about, like what is your
- 20:08Speaker 3: as a stakeholder or like a like executive opinion on it?
- 20:14Speaker 3: Will you be able to pull it off? You know,
- 20:17Speaker 3: are you willing to switch to the new model? And
- 20:20Speaker 3: then well that I have like really great colleagues from India.
- 20:27Speaker 3: It's like it is really great approach to work remotely.
- 20:33Speaker 1: And then.
- 20:36Speaker 3: So it's not the best idea to hire a bunch
- 20:40Speaker 3: of people immediately. You need to iterate one by one.
- 20:44Speaker 3: You find one person who would be potentially a lead,
- 20:50Speaker 3: let's say in development of product management. So they start working.
- 20:54Speaker 3: You need somebody to be like a champion and understand
- 20:57Speaker 3: the product. Usually they already freelancers or agency doing something.
- 21:03Speaker 3: It's not like zero and playing field. You know there
- 21:06Speaker 3: is something going on. So you introduce those new people
- 21:10Speaker 3: who you already consider that they will be like a
- 21:13Speaker 3: full time key roles in the organization. And they learn,
- 21:17Speaker 3: they figured all out, they understand they can work with
- 21:21Speaker 3: the product. You know how to deploy. Oh, one more
- 21:25Speaker 3: small thing all practically every time. Need to make sure
- 21:30Speaker 3: that all the assets, code, documentation and everything is owned
- 21:35Speaker 3: by the company, not by some random person somewhere. You know,
- 21:39Speaker 3: get Hub for example, account is paid by company, it's protected,
- 21:44Speaker 3: you know, the proper restrictions and all that stuff. And
- 21:47Speaker 3: then those people learn, and then you increase the team.
- 21:52Speaker 3: You introduced another person, they learn again, and you introduced
- 21:58Speaker 3: one more. And then there is the moment when you
- 22:01Speaker 3: reach about half of the agency's personnel. You reduce the
- 22:06Speaker 3: tasks given to the outside outsiders or those who had issues. Basically,
- 22:12Speaker 3: you know, if it was good, I wouldn't be there,
- 22:15Speaker 3: so it means you kind of need to replace somebody.
- 22:21Speaker 3: And then you reduce all those tasks a bit by bit,
- 22:24Speaker 3: and you keep building the new key teams. And you know,
- 22:31Speaker 3: if you start like this, it gets easier. You introduce
- 22:35Speaker 3: when you plan for the product, who is involved when
- 22:38Speaker 3: you plan for development, who is also involved? Who signs
- 22:41Speaker 3: off all the ideas? Who is the designer let's say,
- 22:45Speaker 3: who is the product manager, project manager, all the budgets,
- 22:48Speaker 3: all of these things. You put all of these people
- 22:51Speaker 3: in there and it works right.
- 22:54Speaker 1: What about technical innovation, whether it's a remote team, especially
- 22:59Speaker 1: with the remote team and local team obviously, how do
- 23:02Speaker 1: you ensure for a startup? It's about the day to
- 23:05Speaker 1: day you know, firefighting and also growing. So who does
- 23:09Speaker 1: the innovation? But does a CTO come in, tracttional CITO
- 23:12Speaker 1: come in and gets the innovation done?
- 23:15Speaker 2: Is it possible that way?
- 23:17Speaker 1: How should startups look at, you know, innovation while scaling up?
- 23:22Speaker 3: So usually CTO has to track all the new innovative things.
- 23:29Speaker 3: But I would advice for the other CTOs who tracks it.
- 23:37Speaker 3: Be aware, fit, have knowledge, understand it, but try to
- 23:44Speaker 3: put the ball into your team's side. Let them be
- 23:50Speaker 3: those innovators and you come up with the more specific ideas.
- 23:57Speaker 3: So you can say, okay, there's an AI can figure
- 24:00Speaker 3: it out. You can test what it can do, because
- 24:03Speaker 3: in the end of the day you will be signing
- 24:05Speaker 3: it off and it will be your fault if it
- 24:07Speaker 3: messes up. So you're still accountable and responsible for allow this.
- 24:14Speaker 3: So you need to know what can be done what
- 24:17Speaker 3: cannot be done. But if you will be the guy
- 24:22Speaker 3: who does it hands on and Russias, it will demotivate
- 24:26Speaker 3: the team. It will not be interesting. You know, there
- 24:29Speaker 3: are plenty of new things and there's one guy who
- 24:31Speaker 3: does it all and we all clean up the bugs.
- 24:35Speaker 3: It's not cool at all.
- 24:38Speaker 1: Absolutely, absolutely this much to learn about all these things,
- 24:42Speaker 1: you know.
- 24:43Speaker 2: So when does Wigan dust come into the picture? Means?
- 24:47Speaker 2: Is it about?
- 24:48Speaker 1: You know, when things are very bad from the beginning,
- 24:52Speaker 1: how does it work for you best?
- 24:56Speaker 3: Well, it's like, you know, if a company sees that
- 24:59Speaker 3: he will need to scale. Let's say they got investment,
- 25:03Speaker 3: let's say ten million, and they want to just make
- 25:07Speaker 3: it right. So I could help get the blueprints. Let's
- 25:12Speaker 3: say what is the team structure? How who will be managing?
- 25:16Speaker 3: What would be the dynamics, and then could start implementing
- 25:20Speaker 3: it and when it starts working, they will know, Okay,
- 25:24Speaker 3: if we hire twenty more people, it will be three
- 25:28Speaker 3: more teams. These people will be needed to lead it
- 25:32Speaker 3: and like the higher manager will be able to handle
- 25:35Speaker 3: everything else. But you need like a plan how it
- 25:39Speaker 3: will work, and you have already the dynamics of information flow,
- 25:43Speaker 3: knowledge sharing, everything to be in place. Otherwise it will
- 25:48Speaker 3: be complete chaos. Nobody will know what those new people
- 25:51Speaker 3: even supposed to be doing the company. It will be
- 25:54Speaker 3: very awkward. So for me, so that would be probably
- 26:02Speaker 3: easier way because it's you know, it's not that terrible.
- 26:06Speaker 3: It's more like a second opinion or like helping to
- 26:09Speaker 3: prepare preparations. It is very responsible job it. You know,
- 26:17Speaker 3: a lot of things depends on how you put it.
- 26:21Speaker 3: But also you know, let's see, they have hired a
- 26:24Speaker 3: lot of people and there's a mess. They think it's
- 26:28Speaker 3: not really that effective. Let's see how I don't know,
- 26:32Speaker 3: two hundred devs you grew in a year. So in
- 26:36Speaker 3: a year, growing that fast means there's a lot of chaos.
- 26:42Speaker 3: You know, people might not be that much effective. There's
- 26:47Speaker 3: probably no career planning, no one on one calls done properly.
- 26:52Speaker 3: It's just you know, faster, faster, fast to it so
- 26:57Speaker 3: that I can come in and streamline all of it.
- 27:00Speaker 3: You know, how the team leads should work with its team.
- 27:04Speaker 3: Who would be the manager or like a helping person
- 27:08Speaker 3: to grow for that team lead engineering manager what they
- 27:12Speaker 3: supposed to be doing, Because in different companies, engineering managers
- 27:17Speaker 3: are taking different roles. It could be like a team lead.
- 27:22Speaker 3: It could be developer, also like a team lead, but
- 27:27Speaker 3: talking with its like people. It could be like a
- 27:32Speaker 3: product owner plus manager and they would figure out the roadmap.
- 27:38Speaker 3: You know, they could estimate. They could estimate together with
- 27:42Speaker 3: the team, but they work with product a lot, so
- 27:44Speaker 3: they don't write any code and so on. So who
- 27:50Speaker 3: would be a director if there are more engineering managers?
- 27:53Speaker 3: What other responsibilities are they supposed to you know, make
- 27:57Speaker 3: sure they work with people right, doing what once right.
- 28:00Speaker 3: They are basically signing off on the roadmap items and
- 28:04Speaker 3: all of these things, so they are responsible for delivery effectiveness.
- 28:08Speaker 3: Also need to make sure that there is no churn
- 28:10Speaker 3: of people, like if they're a lot like half of
- 28:14Speaker 3: newcomers leaving after trial period, you know, there's definitely red
- 28:19Speaker 3: flag somewhere, so they need to figure that out how
- 28:22Speaker 3: to work with it. So a lot of moving parts.
- 28:27Speaker 3: It takes time, but it is optimizable.
- 28:31Speaker 1: I say, absolutely, there's much to learn about all these
- 28:35Speaker 1: things from you beginners, and I'm sure a lot of
- 28:37Speaker 1: people would want to connect with you. A lot of
- 28:39Speaker 1: companies would want to connect with you. What's the best
- 28:42Speaker 1: way for them to do so.
- 28:45Speaker 3: I have a website Quarter dot com. There's my email,
- 28:48Speaker 3: my phone number, so you can drop me a message there. So.
- 28:54Speaker 3: Also I have LinkedIn you can reach out to me there,
- 28:58Speaker 3: so I will probably respond very quickly.
- 29:02Speaker 1: Wonderful with this, it's a wrap on this very special
- 29:06Speaker 1: edition of the kJ Masterclass Live. Thank you so much
- 29:09Speaker 1: indeed for joining us.
- 29:11Speaker 3: Thank you very much, real pleasure to be here.