# tech-leadership Published articles for tech-leadership. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## AI-First Mindset: How AI is Reshaping Teams and Leadership DevFeed: [AI-First Mindset: How AI is Reshaping Teams and Leadership]() Original publisher: [Read original article]() Author: Magda Miu Published: 2026-03-23T08:16:40Z Content type: opinion Language: en Sources: [Magda Miu]() Topics: [Artificial Intelligence]() Tags: [ai](), [ai-first-mindset](), [artificial-intelligence](), [co-intelligence](), [leadership](), [leadership-and-ai](), [opinions](), [personal-development](), [tech-leadership](), [technology]() ### AI overview The author describes developing an AI-first mindset influenced by Co-Intelligence by Ethan Mollick. They advocate working with AI as a thinking partner and inviting it into everyday work, leadership, exploration, and decision-making while keeping humans in the loop. ### Source excerpt AI is everywhere right now: new tools, new opinions, new predictions. And most of it sits somewhere between hype and fear. For me, it did not start with a tool. It started with a book. About two years ago, I kept seeing people I follow on X mentioning the same book: Co-Intelligence by Ethan Mollick. Enough times ... Continue reading AI-First Mindset: How AI is Reshaping Teams and Leadership ## EM/PM Relationships Aren't About Luck: 5 Tips for Product/Tech DevFeed: [EM/PM Relationships Aren't About Luck: 5 Tips for Product/Tech]() Original publisher: [Read original article]() Author: Anna J McDougall Published: 2025-05-13T14:53:24Z Content type: opinion Language: en Sources: [Anna J McDougall]() Topics: [Code quality]() Tags: [code-quality](), [compliance](), [engineering-management](), [engineering-manager](), [engineering-mangement](), [identifier](), [improvements](), [iso](), [management](), [product-engineering](), [product-management](), [quality](), [relationships](), [team-lead](), [teams](), [tech-leadership]() ### AI overview An opinion article presents practices for building effective engineering manager and product manager relationships. It emphasizes shared ownership across business, team, and product goals, with quality improvements--including compliance work--as part of an engineering manager's contribution. ### Source excerpt EM/PM Relationships Aren't About Luck: 5 Tips for Product/Tech TeamsHeader image: purple background with the text "EM/PM Relationships Aren't About Luck. 5 Tips for Product/Tech Teams :)" and a photo of Anna and Tanja together.Introduction As my probation period at HelloBetter was coming to an end, my team's Senior Product Manager Tanja Lembcke remarked, "It's great working with an EM who cares so much about product." I could easily have said the same back to her, because it's just as valuable working with a PM who cares deeply about technology, something at which she truly excels. Together, we've become a strong team. Much of that relationship has developed naturally, but I've also noticed a few intentional practices that have helped us along the way. I want to share them here for all the product managers, engineering managers, and whoever else happens to like reading my sporadic blog posts. In the end, Tanja and I didn't just "luck out" working together. There are some tried-and-true strategies we both employ to make the most out of our work and get the results we need. If you prefer LinkedIn, you can view the short-form version of this post as a summary and carousel here. Tip 1: Purposefully be the intersection of business, team, and product As a Team Lead or Engineering Manager, it's important to operate at the intersection of business goals, the engineering team, and product. This means not only using the product but also critiquing it, asking thoughtful questions, and continually returning to the core "Why." It is all too easy to sit back and just wait for features to drop in your lap, estimate them, deliver them, and then dust off your hands with a "job well done" attitude that allows you to add a nice dot-point to your CV about value creation. What is much harder, is to actually focus on quality: that hard-to-measure, hard-to-prove value that is constantly competing with your time. For EMs, we tend to see the word "quality" and jump to the concept of code qu ## 3 main soft skills a Tech Lead needs to develop DevFeed: [3 main soft skills a Tech Lead needs to develop]() Original publisher: [Read original article]() Author: Anemari Fiser Published: 2024-12-18T15:01:56Z Content type: article Language: en Sources: [Level up as a Tech Lead]() Topics: [Tech Lead](), [engineering-leadership](), [Learning]() Tags: [article](), [developer](), [leadership](), [skills](), [tech-lead](), [tech-leadership]() ### AI overview This article argues that Tech Leads need soft skills in addition to technical expertise, focusing on active listening and examples involving conflict resolution, ownership, team growth, and tech debt. ### Source excerpt Become a great Tech Lead by focusing on these 3 main soft skills! ## Unlocking Your Potential: The Mentee's Journey DevFeed: [Unlocking Your Potential: The Mentee's Journey]() Original publisher: [Read original article]() Author: Magda Miu Published: 2024-10-24T05:00:00Z Content type: tutorial Language: en Sources: [Magda Miu]() Topics: [Learning](), [meetings]() Tags: [accountability](), [article](), [best-practices](), [career](), [journey](), [magdamiu](), [mentee](), [mentoring](), [mentorship](), [relationships](), [remote](), [skills](), [tech-leadership]() ### AI overview A guide to being an effective mentee. It covers the benefits of mentorship, choosing a mentor, setting objectives, preparing for meetings, seeking feedback, maintaining a mentoring relationship, and adapting mentorship to remote work. ### Source excerpt Being a mentee is like having a seasoned explorer by your side, offering invaluable insights and tips as you navigate your career journey. It's a chance to learn from the wisdom and experiences of someone who's been there, done that, and is eager to share their knowledge. This article, just like the one about being a ... Continue reading Unlocking Your Potential: The Mentee's Journey ## The Culture Map by Erin Meyer DevFeed: [The Culture Map by Erin Meyer]() Original publisher: [Read original article]() Author: Magda Miu Published: 2024-03-07T06:30:00Z Content type: opinion Language: en Sources: [Magda Miu]() Topics: [communications](), [Framework](), [context]() Tags: [book](), [communications](), [context](), [cultural-differences](), [culture](), [erin-meyer](), [framework](), [global](), [leadership](), [tech-leadership](), [the-culture-map]() ### AI overview A discussion of Erin Meyer's The Culture Map, which presents a framework for understanding business communication challenges across cultures. It explains eight cultural scales and emphasizes cultural relativity, respect for individual differences, and listening before acting. ### Source excerpt "You have two eyes, two ears, but only one mouth. You should use them accordingly." "The Culture Map" by Erin Meyer provides a framework to understand the most common business communications challenges that are present when you are working in a global context, with colleagues or stakeholders from different cultures. By assuming that culture does ... Continue reading The Culture Map by Erin Meyer ## Lessons on Tech Leadership: Autonomy, Collective Decision-Making, and Shared Goals DevFeed: [Lessons on Tech Leadership: Autonomy, Collective Decision-Making, and Shared Goals]() Original publisher: [Read original article]() Author: Polly McEldowney Published: 2024-02-21T12:15:40Z Content type: opinion Language: en Sources: [BBC]() Topics: [Tech Lead](), [engineering-culture](), [Software Engineering]() Tags: [decision-making](), [leadership](), [management](), [management-and-leadership](), [software-engineering](), [team](), [tech-lead](), [tech-leadership](), [technology]() ### AI overview A BBC Sounds Software Engineering Team Lead reflects on tech leadership, arguing that leaders should support autonomy instead of micromanaging, involve the team in decisions, and build shared goals collaboratively. ### Source excerpt I have now been a Software Engineering Team Lead on the BBC Sounds mobile apps team for 4 years. So what have I learned from this once-daunting, now-familiar role? Leadership does not mean telling people what to do.Mother Goose is holding back here and letting the baby gosling stride confidently ahead Before working at the BBC, I thought a tech lead's job was to think of some work to do and command others to do it. It was quite a damaging misconception, because it stopped me considering moving up from a software engineer into management. I don't like telling people what to do. This is because I also don't like being told what to do. As the youngest of four siblings, I have perhaps been overexposed to being bossed around. If someone ever talks to me in the imperative, I have an immediate, instinctive visceral response which vastly reduces the likelihood of my compliance with the request. I suspect I am not unique in this. So I never wanted to be That Guy, who makes other people feel like that. But the excellent news is -- it turns out you don't need to be! The great thing is, grown up people are entirely capable of managing their own workloads. Assigning people specific tasks can often feel like micromanagement to them. If it is clear what tasks need to be done, people will prioritise the tasks into their own work streams and pick them up when they have capacity to do so. Collective decision making is good Another thing I used to think leaders had to do, was go and make up bold, dazzling strategies all by themselves and then tell everyone about their vision. Dictatorially make a swathe of tickets and dump them onto the board, whilst loudly trumpeting about their own self-worth in some public channel. In real life this will get you a lot of side-eye of course. I vastly prefer the approach of talking through what needs to be done with the team and making sure everyone understands why it is important. We can work together to outline the high level goals and then discuss ## How to do Architecture Mapping Workshops in a Remote Setup DevFeed: [How to do Architecture Mapping Workshops in a Remote Setup]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2022-07-23T13:27:00Z Content type: tutorial Language: en Sources: [Tobias Mende]() Topics: [Software](), [Back end](), [sessions]() Tags: [architecture](), [backend](), [collaboration-practices-remote-work-software-development-technical-leadership-software-craft](), [how-to](), [mapping](), [remote](), [teams](), [tech-leadership](), [workshops]() ### AI overview This article describes remote architecture mapping workshops based on experience in BRYTER's tech leadership community. It explains that collaborative mapping can help teams develop a shared understanding of a system and align on an overarching technology vision, while individually drawn or autogenerated diagrams may be poorly understood or inaccurate. ### Source excerpt How to do Architecture Mapping Workshops in a Remote Setup Mapping the architecture of the system that you are building in your company, is a worthwhile activity. The worth does not come so much from the end-result, the map, but much more from the activity itself, if done right. ## Shaping developer experience teams for autonomy DevFeed: [Shaping developer experience teams for autonomy]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2022-03-19T13:08:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [Developer experience](), [code productivity](), [Tooling](), [Back end](), [Front end](), [CI/CD](), [Deployment](), [Monitoring](), [cloud-infrastructure]() Tags: [autonomy](), [backend](), [continuous-integration](), [deployment](), [developer-experience](), [frontend](), [infrastructure](), [monitoring](), [team-topologies-developer-productivity-organizational-design](), [teams](), [tech-leadership](), [tooling]() ### AI overview This article discusses how to structure a developer experience team for autonomy and independence. Drawing on BRYTER's experience, it argues for a cross-functional team that can address frontend, backend, tooling, continuous integration, deployment, and monitoring concerns, with specialists covering different technical areas. ### Source excerpt Shaping developer experience teams for autonomy Once you have decided, that a developer experience team would provide value to your organisation, the question is, how such a team should be set up, how it should be shaped, and how it should interact with other teams.