<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Adel Smee on Medium]]></title>
        <description><![CDATA[Stories by Adel Smee on Medium]]></description>
        <link>https://medium.com/@adel.smee?source=rss-bde7d41c5823------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mOK9scAHSFLWcrxy-CJeYw.jpeg</url>
            <title>Stories by Adel Smee on Medium</title>
            <link>https://medium.com/@adel.smee?source=rss-bde7d41c5823------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:27:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adel.smee/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Thinking About Promotion?]]></title>
            <link>https://engineering.ferocia.com.au/thinking-about-promotion-f7e41a7fd7e5?source=rss-bde7d41c5823------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7e41a7fd7e5</guid>
            <category><![CDATA[promotion]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[career-growth]]></category>
            <dc:creator><![CDATA[Adel Smee]]></dc:creator>
            <pubDate>Tue, 27 Jan 2026 04:02:52 GMT</pubDate>
            <atom:updated>2026-01-27T04:02:52.701Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Add these thoughts into the mix.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RKE_Tp2FYkg8onDcljaLww.jpeg" /></figure><p>Getting promoted can mean many different things to us depending on where we are in life and how we are wired when it comes to external validation or status. It also works differently for different companies, industries and cultures, which makes it a tricky thing to write about. I am a Software Engineering leader from Australia and here are some ways of thinking about a promotion that I recommend after many years spent promoting and mentoring people in the tech industry. They are designed to reduce some of the stresses that come with trying to get promoted and increase your sense of agency.</p><p><strong>Note:</strong> this is NOT a How To Get Promoted In Your Current Job At Your Current Company post, on that you should consult your own leaders.</p><h3>💭 You have a lot less control over this than you‘d like to.</h3><p><em>If you keep your head down and do a good job, rewards will come.</em> This is one of the biggest lies that we tell ourselves as good little workers in the capitalist machine. It is sometimes true, but in many, many cases it is not. Here’s a few of those cases:</p><ul><li>You do a great job, your boss wants you to keep doing it, and a promotion would get in the way of that.</li><li>Your boss doesn’t notice you’re doing a good job (more on that later).</li><li>The company is unprofitable/downsizing. It will be harder (not impossible, but harder) for your boss to get you a promotion and a payrise when the company isn’t making enough money to cover costs, or is actively laying people off.</li><li>Your company caps the number of promotions. This means they aren’t merit based, they are finance capped, so even good folks will miss out. This creates a Hunger Games of promotions that is a disincentive to healthy teamwork.</li><li>There’s no room left. If you are a junior looking to get promoted to mid-level this likely isn’t an issue. But if you want a Principal Engineer role at a small company with three Principals already, you might have to wait in line. Some companies will promote anyway and deal with the issues of too many cooks, but you’ll need to confirm that. However if your goal is to be a Head Of Something and there already is one, your only options are to relax and enjoy the journey while letting go of that goal, or to look elsewhere. Carefully think through if you are willing to risk your career ambitions on the choices of not just the existing Head Of, but also company leadership who often take the opportunity of a gap at the top to bring in new, more experienced, replacements.</li><li>You are surrounded by people who are better at the job than you are.</li></ul><p>In each of these instances, there’s only so much you can do to get yourself recognised with a promotion. In some of these cases, the only thing you can do is accept that it is unlikely to happen.</p><h3>💭 If your boss (or their boss and so on) doesn’t want to promote you, you’re not getting promoted</h3><p>Is this fair? Of course not. But it’s how it works. Getting someone promoted often involves a fair amount of effort (the exceptions being very small companies where everyone knows everyone) and if your manager doesn’t like you they simply have to do nothing. I’ve mentored plenty of people who were clearly ready for promotion, but for some reason someone in their chain of command didn’t like them. The only result in every single one of these situations is that promotion or advancement or opportunity only happened after the person had chosen to leave the team or company. If this is the case for you, you can bang your head against that immovable rock wall, or you can give yourself options (see below).</p><p>This is also true if you have a bad reputation amongst the leaders at your company. A lot of promotions, especially senior ones, need sign off from a few key leaders. If one of them doesn’t like the cut of your jib then even if you are in good standing with your boss, they may get overruled.</p><h3>💭 Comparison is the thief of joy.</h3><p>Apparently this was a Theodore Roosevelt quote, but it works well when thinking about promotions. The reason I caution against comparison when thinking about promotion is that I have rarely, if ever, seen folks compare themselves accurately or effectively. There are a number of ways that I see it go regularly wrong:</p><ul><li>The Dunning-Kruger effect in which people who are rather bad at something drastically overestimate their abilities, leading to disappointment and dissatisfaction at promotion time. If this is you, you won’t know it, which makes it even harder to identify and deal with. Evidence can help here — if you are the only one who thinks you are ready for promotion (apart from your work bestie) then maybe you aren’t?</li><li>Selective comparisons. I’ve repeatedly seen people, when comparing themselves to others, pick a single point of comparison in which they are excellent and use it as evidence as to why they should be promoted to group of folks who are equivalently good at that thing. However in software engineering, as in most jobs, promotion is awarded for a number of skills/capabilities/qualities, not just one. Your manager is very likely looking at a much broader set of criteria than you are.</li><li>Out-of-date comparisons. Corporate priorities change as the business grows or evolves. So what might have been a key criteria for promotion two years ago is no longer what the business needs to encourage or reward. This will feel unfair, especially if you put your efforts into something that is no longer valued. This is one of the most consistent parts of the tech industry, it’s always evolving into something else and leaving people behind.</li><li>Comparison builds bitterness. There are plenty of times where promotions will look unfair to you, either for the reasons mentioned above or because someone less capable than you got promoted. Dwelling on this will cause you nothing but grief or stress. It happened, the question is — what are you going to do about it?</li></ul><h3>💭 Maybe you aren’t ready for promotion</h3><p>The last two sections introduced the thoughts that we might not be that good at assessing whether we are ready for promotion and that you’ll need your manager onboard if you want it. If you’re a thoughtful type, you’ll have worked out that promotion is tightly coupled to how you are perceived by your manager, your peers and your company. I encourage you to seek feedback from all three:</p><ul><li>Manager: just ask them.</li><li>Peers: either send out anonymous surveys, or ask them depending on your relationship.</li><li>Company: do a self-assessment against the job description/career criteria. Try and stick to the facts and include evidence from the other two feedback loops.</li></ul><p>If you think you’re ready but feedback from these three areas is telling you otherwise there are two options here:</p><ol><li>You are right and they are all wrong, in which case it might be time to think about moving on (see below).</li><li>You are wrong and they make some decent points.</li></ol><p>If after careful consideration and putting aside your ego and unhealthy comparisons you think Option 2 might be possible, then it is time to focus on getting really good at the job you have. Some people I have worked with are under the impression that they can be kind of okay at the job they have and still get promoted. This is not something that I have found to ever be true. If you are keen on promotion, the first step is always ensuring that you are smashing it out of the park on all elements of your current role. Getting a selection of feedback from the people around you is a good way to realistically assess this. Be careful about how you elicit that feedback, e.g. asking your closest work pal over cocktails if they think you should get promoted is very likely to get you a “hell yeah dude” no matter what they really think.</p><h3>💭 Tell your manager you think you’re ready for promotion</h3><p>If your dream is to get promoted and your manager doesn’t know that, there are two ways this plays out:</p><ol><li>They were going to promote you anyway, yay, lucky coincidence.</li><li>It didn’t even occur to them and you don’t get promoted.</li></ol><p>I like to think I’m a decent manager, but I remember a time when an engineer who worked for me told me he thought he was ready for promotion. I’m embarrassed to say it hadn’t even occurred to me (I was particularly busy at the time, but then again most managers are). When I thought about it and looked into it, it became obvious that he was the strongest candidate for promotion I had that year. Slam dunk promotion when I went up in front of the committee. So let’s add a couple more options to our numbered list after you’ve told your manager you think you’re ready for a promotion:</p><p>3. It didn’t even occur to them, you brought it up, turns out you were right and get promoted.</p><p>4. They think about it, don’t agree with you, work on a plan with you to get you ready for promotion within a reasonable timeframe. Good companies and/or good managers will do this with you, which always makes promotion more achievable.</p><p>5. They brush you off with vague mutterings about it not happening and never get back to you. Either they aren’t interested in promoting you or something is going on at your company that means promotions aren’t likely right now (see <strong>Thought 1</strong>).</p><h3>💭 Yes, you do need to have a personal brand.</h3><p>It’s the worst, I get that. But if people don’t know that you are doing a good job, it dramatically reduces the chances of you getting promoted. This doesn’t mean you need to be bragging about your accomplishments all over the company chat channels. It does mean that at the very least your boss should know what you are doing or adding to various endeavours. The simplest way to do this (without being as cringe as ever writing the phrase “personal brand”) is to just keep a list somewhere of Things I’ve Done. You’ll get extra points if you organise that list by the criteria for promotion, as that’s what your boss is likely to have to do to get you promoted.</p><p>Again, you might think this is unfair, but remember that there are two elements that going into any effort:</p><ol><li>Doing the thing.</li><li>Telling people you did the thing.</li></ol><p>Your boss is busy and won’t always notice, it’s pretty straightforward to hand them a list every couple of months with all the stuff you did that shows how awesome you are. In working out what to put on that list, you’ll also likely become more familiar with what your company and manager prioritise for promotion, making you more likely to direct your efforts in the right ways to achieve promotion.</p><h3>💭 Always be interviewing or networking — give yourself options</h3><p>Okay, that made a pithy thought, but “always” is a bit of an exaggeration. However, there are many, many factors that go into promotion that are out of your control (see <strong>Thought 1</strong>), so when your personal timer runs out and you are done with the current situation, give yourself the opportunity to seek advancement elsewhere instead of just collapsing into resentment. I’ve listened to many people tell me in detail why it was impossible for them to leave their current job, whilst being dissatisfied and bitter about their current lot in life. For some of them, the resentment resulted in poor job performance that made it even more unlikely that they would get promoted. For most they were convinced, without even trying, that an equivalent or better job was impossible to get. That their options were EITHER this horrible situation in which they were being mistreated or passed over, OR long term unemployment. That’s a rough position to put yourself in.</p><p>People who rarely find themselves in this position are those who work on maintaining professional networks they can lean on for advice, mentoring or opportunities. Or folks who regularly work on the skills they need to do well in interviews, like regularly talking about and reflecting on why or how they work the way they do. Even if they are being overlooked in their current role, they’ll know that with a bit of effort they can find something new and hopefully better.</p><p>The only constant in the tech industry is change and eventually even most great companies/bosses/products will grow into something less great. Something that might not suit you as well. If you don’t work to keep your options open, you risk getting trapped.</p><h3>💭 Why do you want to get promoted?</h3><p>Knowing the answer to this question can unlock greater levels of satisfaction and progress in your approach to career development. Here are some of the answers folks have found helpful to recognise and understand in themselves:</p><ul><li>More money. Maybe you’ve got a lot of bills to pay, mouths to feed, financial pressures. This means the need for promotion is clear and obvious and the resultant stress associated with not getting a promotion can be high. This is where the last thought can help take some of the pressure off if it doesn’t happen at your current company. You need to work extra hard on keeping your options open to keep those stress levels down.</li><li>More status or validation. This one is a big one that we all need to a greater or lesser degree. For those of us that really need external markers of progress like promotion in order to feel confident (or at least reduce anxiety) then a promotion knock back feels like a real kick in the face. This can lead to a spiral of self-doubt. Those of you in the neurodivergent community are more likely to relate. So in addition to the other 💭 in this post, if you find yourself reflected here it will become even more important for you to practice the habits and use the tools that you need to in order to support your emotional wellbeing. Remind yourself that a lot of this is outside your control and doesn’t reflect on your intrinsic worth. Look for other avenues to find the validation and support you need.</li><li>To be the boss/big dog. This can be linked to the previous point about status. But maybe you just want to be the one with the final say. If so, you can get creative with this and find other ways to own pieces of work or smaller projects in your day-to-day without the official title. Often that will be a great way to build up experience that then gets you in a better position for promotion next time around. Of course if your company is completely hierarchical, doesn’t have that level of flexibility and doesn’t think you’re ready for promotion, I’ll point you right back to the last thought.</li><li>To get to do More Cool Stuff ™️. Some companies put gates around the bigger, juicier work and restrict it to folks above a certain level. This is a great incentive to promotion but a big disappointment if you don’t get one. Like the last point, I’d recommend looking for opportunities to excel in your current role and take on new challenges even if they aren’t quite as cool as the Cool Stuff™️ so that next promo round you look irresistible. If you’re a manager reading this — why do you restrict Cool Stuff™️ to a certain elite cohort? It just creates in-groups and out-groups and disincentivises large numbers of your employees. It’s an anti-pattern to healthy culture, stop it.</li><li>That’s just what you do. Is it though? There’s a lot written about how to climb the corporate ladder but not a whole lot about finding your niche and sticking there. I’ve reached the point in my career where I think the intersection of what I enjoy, what I’m good at, what a company needs and what there is demand for all overlap. I’m done climbing and am now actively resisting promotion. It’s not the first time. Early in my management career I was offered a role at my current (much higher) level. I knew I hadn’t done nearly enough hands-on work at the team level and so politely declined. Next time that opportunity came round it felt much more appropriate to my skills and experience and I happily accepted. I’ve mentored many people who, often because they were comparing themselves inaccurately to the wrong people, felt like they <em>should</em> be going for promotion but would be hard pressed to explain why. More time reflecting on the emotional triggers that create a need for external validation can lead to greater self-awareness and longer term contentment.</li></ul><p>Wherever you are in your career I hope you find some of these thoughts useful in taking the pressure off yourself, and creating more space for creativity and contentment in your working life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7e41a7fd7e5" width="1" height="1" alt=""><hr><p><a href="https://engineering.ferocia.com.au/thinking-about-promotion-f7e41a7fd7e5">Thinking About Promotion?</a> was originally published in <a href="https://engineering.ferocia.com.au/">Ferocia Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scaling Up Engineering Management]]></title>
            <link>https://engineering.ferocia.com.au/scaling-up-engineering-management-f93c7a18f5b2?source=rss-bde7d41c5823------2</link>
            <guid isPermaLink="false">https://medium.com/p/f93c7a18f5b2</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[banking-technology]]></category>
            <category><![CDATA[scaling]]></category>
            <dc:creator><![CDATA[Adel Smee]]></dc:creator>
            <pubDate>Fri, 30 May 2025 02:57:06 GMT</pubDate>
            <atom:updated>2025-06-02T01:01:08.255Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Scale the Engineering Org by at least 50% this year and don’t break anything.</blockquote><figure><img alt="The logo of Up Bank" src="https://cdn-images-1.medium.com/max/1000/1*al06fO0CjEUU0e5dJ6EWXg.png" /><figcaption>Up Bank</figcaption></figure><p>That was my mission when I took on the Engineering Director role at Ferocia at the start of 2024. We were a small group (just under 40 engineers) who were punching well above our weight, having launched and grown Australia’s most loved digital bank into what would soon be a million customer business. We’d been acquired by the Bendigo &amp; Adelaide Group a couple of years earlier and were increasingly taking on more of the customer-facing apps and websites as well as some internal tooling. The cost of success! It was a great position to be in but also a challenging one. Information sharing, reinforcement of our very high standards and unification of purpose are all much easier when there are fewer folks, and only one product, to consolidate across. What we were now looking at were challenges across technology, people, processes and culture as who “we” were got a much broader definition. There was also the challenge of how to increase the number of teams whilst still having experience in each, and not killing the velocity of the existing teams.</p><p>At the same time I had a relatively new crew of Engineering Managers (EMs) with experience ranging from 0 months up to 2.5 years, the average being much closer to 0. Like a lot of EMs, they had come up as software engineers and then transitioned into management. This meant there was a lot of experience with code, not as much with humans. I was determined not to make the same mistake that is made a lot in our industry and assume that someone who can write performant, secure and maintainable code would also be good at giving tough feedback and optimising delivery processes etc.</p><p>After some pondering, some feeling overwhelmed, and some crystal clear acknowledgment that this was way too much for one person to do without a tonne of support I decided to focus on the EMs as the key to unlocking the next level of growth for Engineering. The thesis was that by supporting and growing the EMs, we could distribute decision making, quality control and maintenance of our healthy culture down to the level of the team. My job would be to make sure the EMs had the awareness of current priorities/direction, potential upcoming changes and knew what we were not going to compromise on as we grew. As effective leaders they would then ensure that their teams could get the job done, or provide clear data to me on what was preventing that.</p><p>Since we had been quite small there were also a lot of key engineering organisation artefacts that we just didn’t have, or had in very early stages, that would need to be rewritten or created if we were to effectively grow. Things like proper and comprehensive onboarding documentation, a more reliable hiring process, an engineering knowledge base, a proper on call roster, an incident management process, proper release management and lots, lots, more. I knew my EMs were a team of nascent superstars, but how best to ensure they could feel supported in doing what they knew was best, and what the company needed them to do?</p><p>For an engineer to successfully make the leap from coder to manager I believe they need two things:</p><ol><li><strong>Peer support.</strong> In order to get good at something, practice and effective feedback are the two essential ingredients. With engineering management, I think peer support is also critical as the job can be a lot more demanding in ways that a technically challenging role is not (technical challenges have different demands). We created a fortnightly session for all of us to come together, check in, share our challenges, discuss topics related to management and get feedback on what we were doing.</li><li><strong>A broad toolkit.</strong> Unlike, for example, the Go programming language, people are almost infinitely variable in what they can do and what they need. Combine that with a wide variety of cultures and contexts in which those people do their thing, and the EM job is one where you can’t just head to Stack Overflow to solve the next problem. A lot of EMs don’t realise that, and become fundamentalists for an approach or a system that they then apply blindly to every person in every situation. In order to ensure that wasn’t the case here, we created a (years long) program of study and learning and knowledge sharing to ensure we all had a toolkit with lots of different tools in it for use in different contexts and with different people.</li></ol><h3>Peer Support Group</h3><p>Every fortnight we get together to talk about what we do. Critically, this meeting is at the end of the workday and we make the point of finishing “work” before we start the meeting — it’s for talking about work but not doing work. There’s no mandate on attendance but we make a point of prioritising it against other meetings, with the CTO also attending most sessions. It’s also a space, explicitly protected by the boss, for reflecting on the work we do as managers in the context of that work. We have rules of conduct (e.g. All discussion is confidential) and over time have grown to trust it is a space in which we can be real or vulnerable without judgement.</p><p>Management training as a separate activity is a good thing, and more companies should focus on it, especially for new managers. However, management training on its own lacks the context and immediacy required for a person to improve a skill. When we learned to code we had immediate feedback from the compiler or test suite to let us know when we got it wrong or right. When we joined software engineering teams we had PR reviews (reading or receiving) that provided daily feedback on what good looks like. For managers there’s rarely any equivalent, beyond whatever feedback mechanisms your company has in place, which will generally be infrequent and can have their own biases. I wanted to create a regular forum for EMs to talk about fresh, relatable challenges with their peers, to get feedback, to crowdsource ideas on how to deal with difficult problems (although we try to refrain from advice giving and focus more on listening and asking questions), or to just have a safe place to let it all out when it gets heavy.</p><p>For each session we go through the following steps:</p><ol><li>Checkin: “How are you <em>really</em>?” is the question we aim to answer.</li><li>Learning Opportunity of the Week (LOotW). This grew up organically as people came to the session with a particularly interesting, troubling or puzzling management challenge. Someone will talk about something that has happened over the last fortnight, and we’ll all get the opportunity to learn from it. Sometimes there’s an outcome (positive or negative) to the situation, and sometimes we just need to sit in the discomfort of not knowing together. One of the biggest differences between coding and managing is that in coding there’s nearly always a tangible outcome (working/not working; shipped/canned), but in management a lot of the time you never get to know if you achieved a clear win. Sharing ambiguity together normalises it and reduces the anxiety it can create.</li><li>Discussion Topics or Skills Sessions — more on that below.</li></ol><h3>Toolkit</h3><p>There are many different mechanisms to access tools for managing effectively. Some of the ways in which we do this include:</p><ul><li><strong>Management training.</strong> We’ve done a session on Difficult Conversations as this kind of workshop works effectively when run by folks outside the team.</li><li><strong>Fortnightly discussion topics.</strong> These form part of the peer support sessions and we currently have a list of over 50 topics that we are working our way through, and that list continues to grow. The topics come from our crowdsourced interests, thoughts, challenges and so on. Examples:</li></ul><blockquote>What is extrinsic vs intrinsic motivation? How can it manifest in a person? In a team? Discuss.</blockquote><blockquote>What implicit signals are you sending your team? Think of at least one positive and one negative one.</blockquote><blockquote>It is my job to make my reports happy and effective. Discuss.</blockquote><blockquote>I feel responsible for things outside my control. Discuss.</blockquote><blockquote>What is psychological safety?</blockquote><blockquote>What are the benefits of letting things break, fall apart or happen badly?</blockquote><ul><li><strong>Skills sessions.</strong> We have run sessions on particular topics like performance management and giving feedback.</li><li><strong>Book club.</strong> The team decided they wanted to form a book club so we meet fortnightly to work through a book related to engineering management. We try and alternate between a book on people, e.g. <a href="https://www.booktopia.com.au/dare-to-lead-bren-brown/book/9781785042140.html">Dare to Lead by Brene Brown</a>; and a book with a more technical focus, e.g. <a href="https://www.booktopia.com.au/the-phoenix-project-gene-kim/book/9781942788294.html">The Phoenix Project by Gene Kim, George Spafford, and Kevin Behr</a>. An academic approach to management just ends up creating detached, fundamentalist managers who can’t connect with the organic, fungible and sometime messy business of managing humans. We relate the books we read back to our real life challenges and try to make them as practical and tangible as possible.</li></ul><h3>Reflections</h3><p>Eighteen months later we are 85% bigger than we were, we’ve just launched our third product and are soon to ship our fourth. We’ve onboarded 35 engineers and EMs and feedback consistently praises our onboarding process, the result of a fantastic group effort from the managers. A lot of the areas mentioned at the start of this post have seen significant love and we’re better organised and aligned today than we were a year ago. The EM team is a cohesive unit that supports each other, produces a lot of high quality work for the engineering organisation, and runs happy and effective teams of their own. While we still face a lot of challenges as we continue to grow and evolve, we are well placed to do so.</p><p>Even with this phenomenal crew of humans, growth has hurt. I’ve been stretched too thin and haven’t always made sure the right information was available at the right times. Sometimes that “right information” didn’t even exist. Without effective leadership at every level, devolving decision making down into the team is less effective. There’s also the drag of constant change — growing, changing teams, shifting priorities. It’s been a successful year but not an easy one.</p><p>It’s also worth mentioning that creating room for learning and reflection for your management team is only part of the picture for effective growth. There’s a lot more on the essential ingredients list including (but not limited to):</p><ul><li>Hiring well. Without this everything else crumbles.</li><li>How you structure and grow your teams.</li><li>How you delegate decision making and information sharing.</li><li>How your funding models are set up (while I try to avoid sweeping generalisations, project based funding models are often setup in such a way as to disincentivise long-term, quality-based outcomes).</li><li>How you align your teams towards a north star.</li><li>Answering the question: When is enough growth enough?</li><li>… and more</li></ul><p>Scale is a challenge as the EM team has continued to grow. Our weekly meetings can now have up to 13 people in attendance which is pushing the boundaries of what an effective group can do. For example, it’s not uncommon for checkin to take half the meeting duration now. During our next growth spurt, we are hiring additional Engineering Directors and will be splitting the management group for the first time. This fills me with pride for what we’ve accomplished and sadness that we’ve outgrown the single team structure and cosiness. We are committed to continuing with the program even as we grow, but will likely split into smaller groups for discussion and feedback sessions. Onward and Upward.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f93c7a18f5b2" width="1" height="1" alt=""><hr><p><a href="https://engineering.ferocia.com.au/scaling-up-engineering-management-f93c7a18f5b2">Scaling Up Engineering Management</a> was originally published in <a href="https://engineering.ferocia.com.au/">Ferocia Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>