Discover and read the best of Twitter Threads about #engineeringmanagement
Most recents (24)
Episode 75 is out!
@hhariri gives advice on how to deal with information overload within a company.
Check out the full interview:
codingsans.com/blog/how-to-de…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #information #communication
@hhariri gives advice on how to deal with information overload within a company.
Check out the full interview:
codingsans.com/blog/how-to-de…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #information #communication
Here are a few takeaways:
1. Categorize information
Don't push everything on employees. Learn what needs to be communicated proactively, and what information they should be allowed to pull for themselves. This helps you avoid information overload.
1. Categorize information
Don't push everything on employees. Learn what needs to be communicated proactively, and what information they should be allowed to pull for themselves. This helps you avoid information overload.
2. Consider asynchronous standups
Daily standups aren't suitable for every team. As an alternative, you can encourage your team to document their weekly input, and go through each others' logs at the end of the week to see what their peers have been up to.
Daily standups aren't suitable for every team. As an alternative, you can encourage your team to document their weekly input, and go through each others' logs at the end of the week to see what their peers have been up to.
Episode 74 is out!
@rodchile shares valuable advice on creating efficient and engaging processes for your teams.
Check out the full interview:
codingsans.com/blog/process-m…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #processes
@rodchile shares valuable advice on creating efficient and engaging processes for your teams.
Check out the full interview:
codingsans.com/blog/process-m…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #processes
Here are a few takeaways:
1. Focus on the bigger picture
Understand the business goals and the aims of your teams before introducing a new process. If you're not sure how a process would help them, take a step back, and identify what the root of the problem is first.
1. Focus on the bigger picture
Understand the business goals and the aims of your teams before introducing a new process. If you're not sure how a process would help them, take a step back, and identify what the root of the problem is first.
2. Processes aren't the only solutions
New processes can't solve everything. In reality, trying to fix behavior problems by introducing a new process is counterproductive. In these cases, retrospective team meetings and coaching sessions are more helpful.
New processes can't solve everything. In reality, trying to fix behavior problems by introducing a new process is counterproductive. In these cases, retrospective team meetings and coaching sessions are more helpful.
Episode 73 is out!
@jstanier gives valuable advice on how to manage your energy, not your time.
Check out the full interview:
codingsans.com/blog/manage-yo…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #leadership
@jstanier gives valuable advice on how to manage your energy, not your time.
Check out the full interview:
codingsans.com/blog/manage-yo…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #leadership
Here are a few takeaways:
1. Optimize for output
Set realistic goals for yourself at the beginning of each week. Instead of trying to make every second productive, focus on the output you want to achieve, and leave enough breaks and prep time between your activities.
1. Optimize for output
Set realistic goals for yourself at the beginning of each week. Instead of trying to make every second productive, focus on the output you want to achieve, and leave enough breaks and prep time between your activities.
2. Don't overbook yourself
Unexpected changes will inevitably happen. You might need to drop everything to help a colleague or prioritize an urgent task. Fill your calendar 75-80% at max to make sure you leave time for such cases.
Unexpected changes will inevitably happen. You might need to drop everything to help a colleague or prioritize an urgent task. Fill your calendar 75-80% at max to make sure you leave time for such cases.
Episode 72 is out now!
Steven Lopez, VPE at @deem discusses choosing the right tech stack for your business, especially when going through a digital transformation.
Check it out: codingsans.com/blog/how-to-ch…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement
Steven Lopez, VPE at @deem discusses choosing the right tech stack for your business, especially when going through a digital transformation.
Check it out: codingsans.com/blog/how-to-ch…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement
Here are the main aspects you need to consider in a digital transformation:
1. People
Always start with people. The key to digital transformation is getting your people to work with the technology. If you lack the people who can work with your tech stack, you can’t move forward.
1. People
Always start with people. The key to digital transformation is getting your people to work with the technology. If you lack the people who can work with your tech stack, you can’t move forward.
2. Processes
Take account of the processes you have in place. Include the communication, project management, DevOps, QA, etc. Make sure you find every aspect that may be improved upon or changed to better fit your needs going through a digital transformation.
Take account of the processes you have in place. Include the communication, project management, DevOps, QA, etc. Make sure you find every aspect that may be improved upon or changed to better fit your needs going through a digital transformation.
Episode 71 is finally out!
@AlvaroRMoya talks about building and leading high-performance tech teams.
Check out the full interview:
codingsans.com/blog/building-…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #leadership #HighPerformance
@AlvaroRMoya talks about building and leading high-performance tech teams.
Check out the full interview:
codingsans.com/blog/building-…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #leadership #HighPerformance
Here are a few takeaways:
1. Know your metrics
If you want to measure high performance, don't focus exclusively on the delivery. Make sure employee satisfaction is high, and your team understands the business goals, so they know how to plan their tasks effectively.
1. Know your metrics
If you want to measure high performance, don't focus exclusively on the delivery. Make sure employee satisfaction is high, and your team understands the business goals, so they know how to plan their tasks effectively.
2. Do it one step at a time
Building a high-performance team takes time. First, define which areas you want to work on with your team based on your company's key values. Then, set action items with them to improve those areas one by one.
Building a high-performance team takes time. First, define which areas you want to work on with your team based on your company's key values. Then, set action items with them to improve those areas one by one.
Episode 70 is finally out!
@deacix shares valuable advice on how to start a DAO, and talks about creating 1inch Network.
Check out the full interview:
codingsans.com/blog/how-to-st…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #leadership #DAO
@deacix shares valuable advice on how to start a DAO, and talks about creating 1inch Network.
Check out the full interview:
codingsans.com/blog/how-to-st…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #leadership #DAO
1. Keep it safe
Don't release code without auditing it. A lot of hacks can happen if you put code into production without doing a proper audit first. Avoid this mistake, and prioritize security - before the latest release, 1inch had 10 audits to ensure safety.
Don't release code without auditing it. A lot of hacks can happen if you put code into production without doing a proper audit first. Avoid this mistake, and prioritize security - before the latest release, 1inch had 10 audits to ensure safety.
2. Find the right contributors
In a DAO, people have shared access to the company's assets, so make sure you share your work with the right people. If somebody abuses the network for their personal gain, it's time to say goodbye to them.
In a DAO, people have shared access to the company's assets, so make sure you share your work with the right people. If somebody abuses the network for their personal gain, it's time to say goodbye to them.
Ep 5 of the Level-up Engineering Stories is out!
@iolloyd shares how Blockdaemon builds successful teams and products within the blockchain space.
Check out the interview:
codingsans.com/blog/leadershi…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement
@iolloyd shares how Blockdaemon builds successful teams and products within the blockchain space.
Check out the interview:
codingsans.com/blog/leadershi…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement
Here are a few takeaways:
1. Hire for success
The secret of building well-aligned teams is establishing the right hiring strategy. Technical knowledge is important, but focus on finding culturally aligned people who are deeply interested in their field.
1. Hire for success
The secret of building well-aligned teams is establishing the right hiring strategy. Technical knowledge is important, but focus on finding culturally aligned people who are deeply interested in their field.
2. Keep your teams aligned
When you have teams all around the world, you have to find the right balance between autonomy and alignment. Some practices must be standardized among teams so that you're able to run cross-functional programs.
When you have teams all around the world, you have to find the right balance between autonomy and alignment. Some practices must be standardized among teams so that you're able to run cross-functional programs.
I'm going to voice an extremely unpopular opinion.
One that could even get me "cancelled"...
There are quite a few different research firms out there, and we all know the big names.
A thread 🧵
One that could even get me "cancelled"...
There are quite a few different research firms out there, and we all know the big names.
A thread 🧵
When you peel back the curtain, it's typically not real research that goes into it.
It looks like the following at a high level:
- There's a paper that needs to be written based on demand.
- You pick X amount of vendors to go into the paper.
(cont)
It looks like the following at a high level:
- There's a paper that needs to be written based on demand.
- You pick X amount of vendors to go into the paper.
(cont)
- You chat with all of them for about an hour. They show you a PowerPoint presentation/sales pitch about the product.
- You take that and write about it.
- You take that and write about it.
Ep 69 is out!
Somer Esat shares advice on coaching engineers on their career path as an engineering manager.
Check out the full interview:
codingsans.com/blog/engineer-…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #leadership #careerdevelopment
Somer Esat shares advice on coaching engineers on their career path as an engineering manager.
Check out the full interview:
codingsans.com/blog/engineer-…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #leadership #careerdevelopment
Here are a few takeaways:
1. Manage information wisely
As an EM, you talk to ICs, leads and the technical director regularly. Make sure you share helpful information with them while also creating a reporting structure where people can talk about their problems confidentially.
1. Manage information wisely
As an EM, you talk to ICs, leads and the technical director regularly. Make sure you share helpful information with them while also creating a reporting structure where people can talk about their problems confidentially.
2. Coach engineers in their career development
Encourage engineers to evaluate their growth, to pinpoint areas to improve and to ask for help from their lead or seniors on the team. Have career development discussions with them, and discuss the expectations of the next level.
Encourage engineers to evaluate their growth, to pinpoint areas to improve and to ask for help from their lead or seniors on the team. Have career development discussions with them, and discuss the expectations of the next level.
Ep 68 is out!
@beznahej talks about implementing an OKR performance management system to set&track goals in a meaningful way.
Check out the full interview:
codingsans.com/blog/okr-perfo…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #leadership #OKRs
@beznahej talks about implementing an OKR performance management system to set&track goals in a meaningful way.
Check out the full interview:
codingsans.com/blog/okr-perfo…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #leadership #OKRs
Here are a few takeaways:
1. Focus on the bigger picture
When engineers work on a piece of code, they don't see how it contributes to North Star goals. OKRs help them see the bigger picture, so they'll value their own contribution more.
1. Focus on the bigger picture
When engineers work on a piece of code, they don't see how it contributes to North Star goals. OKRs help them see the bigger picture, so they'll value their own contribution more.
2. Customize OKRs
An OKR performance management system works best if you tailor it to your team's needs. Be patient when you introduce OKRs, have discussions to see what works and what needs to be changed, and welcome questions and suggestions from everyone.
An OKR performance management system works best if you tailor it to your team's needs. Be patient when you introduce OKRs, have discussions to see what works and what needs to be changed, and welcome questions and suggestions from everyone.
Ep 67 is out!
@ritendra from @fb_engineering gives advice on improving cross-functional collaboration in software engineering.
Check out the full interview:
codingsans.com/blog/cross-fun…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #leadership
@ritendra from @fb_engineering gives advice on improving cross-functional collaboration in software engineering.
Check out the full interview:
codingsans.com/blog/cross-fun…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #leadership
Here are a few takeaways:
1. Don't overemphasize roles
Cross-functional collaboration works best if you hire well-rounded people who can think outside of their assigned roles. Product managers may have engineering ideas, just like engineers can come up with great product ideas.
1. Don't overemphasize roles
Cross-functional collaboration works best if you hire well-rounded people who can think outside of their assigned roles. Product managers may have engineering ideas, just like engineers can come up with great product ideas.
2. Encourage empathy sessions
Cross-functional collaboration can cause frustration when people don't see the value of other functions. Hold empathy sessions where cross-functional partners explain what's challenging about their role. They'll appreciate each other's work more.
Cross-functional collaboration can cause frustration when people don't see the value of other functions. Hold empathy sessions where cross-functional partners explain what's challenging about their role. They'll appreciate each other's work more.
Ep 66 is out!
@tylerhartley talks about the philosophies, habits and challenges of building truly agile organizations.
Check out the full interview:
codingsans.com/blog/agile-org…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #agile #leadership
@tylerhartley talks about the philosophies, habits and challenges of building truly agile organizations.
Check out the full interview:
codingsans.com/blog/agile-org…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #agile #leadership
Here are a few takeaways:
1. Become an entirely agile organization
Do not limit agile to engineering. When your entire organization adapts to the agile philosophies, you can react to changes easier and faster.
1. Become an entirely agile organization
Do not limit agile to engineering. When your entire organization adapts to the agile philosophies, you can react to changes easier and faster.
2. Strive for "pretty good"
As an agile organization, you’re constantly iterating your product. This means you always leave room for improvement. So, don't try to make everything perfect the first try - strive for "pretty good" and keep iterating!
As an agile organization, you’re constantly iterating your product. This means you always leave room for improvement. So, don't try to make everything perfect the first try - strive for "pretty good" and keep iterating!
Ep 65 is out!
@SteveTauber talks about productive IT audit sessions from preparation through execution to follow-up actions.
Check out the full interview:
codingsans.com/blog/it-audit
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #audit #leadership
@SteveTauber talks about productive IT audit sessions from preparation through execution to follow-up actions.
Check out the full interview:
codingsans.com/blog/it-audit
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #audit #leadership
Here are a few takeaways:
1. Provide psychological safety
The number one trait of high-performance teams is psychological safety. If you can establish that within your company, it's easier for everyone to work together and build a high quality engineering product.
1. Provide psychological safety
The number one trait of high-performance teams is psychological safety. If you can establish that within your company, it's easier for everyone to work together and build a high quality engineering product.
2. Evaluate objectively
It's hard to pinpoint what's going wrong in your company. Reflecting on how your teams operate, why they follow certain rituals and how they interact with each other is a good way to start.
It's hard to pinpoint what's going wrong in your company. Reflecting on how your teams operate, why they follow certain rituals and how they interact with each other is a good way to start.
Ep 62 is out now!
We talk to @Davidmeirsiegel, CEO @Meetup about motivating and retaining talent during the Great Resignation.
Check out the full interview:
codingsans.com/blog/how-to-im…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #EmployeeRetention
We talk to @Davidmeirsiegel, CEO @Meetup about motivating and retaining talent during the Great Resignation.
Check out the full interview:
codingsans.com/blog/how-to-im…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #EmployeeRetention
Here are a few key takeaways from the interview:
1. Build a community
The biggest takeaway from the pandemic is that people stick around at a company for the community. Your best bet to improve retention is to work on building a community.
1. Build a community
The biggest takeaway from the pandemic is that people stick around at a company for the community. Your best bet to improve retention is to work on building a community.
2. Utilize hybrid teams
Take advantage of the time you spend in the office by prioritizing collaborative work. This makes collaboration more efficient and supports everyone in building relationships, strengthening your community. You can maximize focus time in the home office.
Take advantage of the time you spend in the office by prioritizing collaborative work. This makes collaboration more efficient and supports everyone in building relationships, strengthening your community. You can maximize focus time in the home office.
How to improve decision making across your company?
Get inspired from the story of restructuring @Foursquare by Ankit Patel from finding the issues to getting everyone onboard.
codingsans.com/blog/organizat…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement
Get inspired from the story of restructuring @Foursquare by Ankit Patel from finding the issues to getting everyone onboard.
codingsans.com/blog/organizat…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement
Here are some key takeaways:
1. Prioritize the customer
You’d think this goes without saying, but teams and companies often fall into the mindset of adjusting the work to their own preferences over the customer’s. Always keep your customer in mind.
1. Prioritize the customer
You’d think this goes without saying, but teams and companies often fall into the mindset of adjusting the work to their own preferences over the customer’s. Always keep your customer in mind.
2. Drive decision making down
The people in the frontline are closer to the customer than executive leadership, so they can often make better decisions regarding the frontline work. Empower them to do so, minimize executive involvement and watch productivity go way up.
The people in the frontline are closer to the customer than executive leadership, so they can often make better decisions regarding the frontline work. Empower them to do so, minimize executive involvement and watch productivity go way up.
Looking to put customer obsession into action? We bring you a case study from @minarets, VPE at @Mailchimp about doing just that via an engineering event.
Enjoy!
codingsans.com/blog/customer-…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #CustomerObsessed
Enjoy!
codingsans.com/blog/customer-…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement #CustomerObsessed
Here are some key takeaways:
1. Customer obsession
Amazon made this a well-known company value. The idea is simple: prioritize the customer’s needs and experience, then work your way backwards through the product and the teams, all the way to yourself.
1. Customer obsession
Amazon made this a well-known company value. The idea is simple: prioritize the customer’s needs and experience, then work your way backwards through the product and the teams, all the way to yourself.
2. Getting buy-in from leadership
Selling your initiatives internally is a key part of a leadership job. When you’re planning a customer obsession event, the first people you need to involve are your cross-functional peers. Make sure they understand the goals.
Selling your initiatives internally is a key part of a leadership job. When you’re planning a customer obsession event, the first people you need to involve are your cross-functional peers. Make sure they understand the goals.
How to navigate the transition of becoming a director? @mseavers from Epic Games shares his experience in our latest episode!
Here's the interview: codingsans.com/blog/managing-…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement
Here's the interview: codingsans.com/blog/managing-…
Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement
Here are some takeaways:
1. High failure rate
A director's job is very different from a frontline manager. Many fail the transition, and it can take years to master the role even for those who succeed. Prepare by learning about the expectations and count on a bumpy journey.
1. High failure rate
A director's job is very different from a frontline manager. Many fail the transition, and it can take years to master the role even for those who succeed. Prepare by learning about the expectations and count on a bumpy journey.
2. Examine your motivations
Be honest with yourself about your motivation for getting this promotion. Chasing a paycheck or more control aren’t bad things, but they can lead to a negative mindset. However, the best motivation is looking to unlock more of your team’s potential.
Be honest with yourself about your motivation for getting this promotion. Chasing a paycheck or more control aren’t bad things, but they can lead to a negative mindset. However, the best motivation is looking to unlock more of your team’s potential.
Let's start the New Year with a new episode:
Tips to prepare your team for rapid growth from @josephgefroh, Eng Director, @healthsherpas.
Check out the interview: codingsans.com/blog/scale-team
Hosted by @FancyKarolina, powered by @codingsans.
#EngineeringManagement #HyperGrowth
Tips to prepare your team for rapid growth from @josephgefroh, Eng Director, @healthsherpas.
Check out the interview: codingsans.com/blog/scale-team
Hosted by @FancyKarolina, powered by @codingsans.
#EngineeringManagement #HyperGrowth
Here’s a taste of Joseph’s priority list about standardizing processes:
1. Deployment process
Make sure that your deployment is repeatable and consistent regardless of which developer is doing it. Document it first, and when it’s done, you can automate it in large parts.
1. Deployment process
Make sure that your deployment is repeatable and consistent regardless of which developer is doing it. Document it first, and when it’s done, you can automate it in large parts.
2. Monitoring
Monitoring gives your engineers metrics about the code’s performance in production. There are great tools out there that are easy to set up, and save you a lot of time and energy in the long run. Make sure to have it send your team a message when something breaks.
Monitoring gives your engineers metrics about the code’s performance in production. There are great tools out there that are easy to set up, and save you a lot of time and energy in the long run. Make sure to have it send your team a message when something breaks.
Do virtual offsites work? Definitely.
How do you make them work? That’s tricky.
So we bring you tips and stories from @allie_p at @GitHubEng.
Check out the interview: codingsans.com/blog/virtual-o…
Hosted by @FancyKarolina, powered by @codingsans.
#EngineeringManagement
How do you make them work? That’s tricky.
So we bring you tips and stories from @allie_p at @GitHubEng.
Check out the interview: codingsans.com/blog/virtual-o…
Hosted by @FancyKarolina, powered by @codingsans.
#EngineeringManagement
Here are some key takeaways:
1. You can set the same goals virtually
A virtual offsite event can fulfill the same function as its in-person counterpart. You can do team building, unpack your values, align your team or hold a game day. It works.
1. You can set the same goals virtually
A virtual offsite event can fulfill the same function as its in-person counterpart. You can do team building, unpack your values, align your team or hold a game day. It works.
2. Don’t even try the same activities
A virtual event often holds more potential distractions for the participants than an in-person one. So you need to make an effort to make the online activities engaging. A series of frontal presentations is sure to lose everybodys’ interest.
A virtual event often holds more potential distractions for the participants than an in-person one. So you need to make an effort to make the online activities engaging. A series of frontal presentations is sure to lose everybodys’ interest.
Here’s a new the Stories spinoff episode with @joseroca, VP of Product and Engineering at @prezi about handling the dual leadership role and more.
Check out the interview: LINK
Hosted by @FancyKarolina, powered by @codingsans.
#EngineeringManagement
🧵👇
Check out the interview: LINK
Hosted by @FancyKarolina, powered by @codingsans.
#EngineeringManagement
🧵👇
1. It’s all about balanced attention
In a dual leadership role, give equal attention to both your teams. Neglecting to put out fires on one team can be just as harmful, as paying too close attention to the other, and not giving your team room to grow.
In a dual leadership role, give equal attention to both your teams. Neglecting to put out fires on one team can be just as harmful, as paying too close attention to the other, and not giving your team room to grow.
2. Give space to your teams
Giving space to your teams to do their jobs isn’t just going to help them grow, but you as well. When you’re not busy with getting involved in the frontline work, you have more capacity to focus on your leadership role, and get better at it.
Giving space to your teams to do their jobs isn’t just going to help them grow, but you as well. When you’re not busy with getting involved in the frontline work, you have more capacity to focus on your leadership role, and get better at it.
Tips and tricks to building a platform team and creating healthy coordination with product teams from @skamille at @twosigma.
Check it out: codingsans.com/blog/managing-…
Hosted by @FancyKarolina, powered by @codingsans.
#EngineeringManagement #PlatformEngineering
Check it out: codingsans.com/blog/managing-…
Hosted by @FancyKarolina, powered by @codingsans.
#EngineeringManagement #PlatformEngineering
Here are some takeaways about communication channels:
1. Coordinate planning
You want to start coordination as early as possible. Send a platform engineer to join the planning sessions of product teams, and see if they have requests or advise them on currently available options
1. Coordinate planning
You want to start coordination as early as possible. Send a platform engineer to join the planning sessions of product teams, and see if they have requests or advise them on currently available options
2. Use product managers
Using product managers in platform teams is an unconventional but useful idea. They can help with communication on every level, make it smoother and take some load off management - but definitely can’t replace them.
Using product managers in platform teams is an unconventional but useful idea. They can help with communication on every level, make it smoother and take some load off management - but definitely can’t replace them.
Why writing is important in #EngineeringManagement and how to improve it? Tips from Erica Greene at @Etsy @codeascraft to improve your team’s and your own writing skills.
Check out the interview: codingsans.com/blog/importanc…
Hosted by @FancyKarolina, powered by @codingsans.
Check out the interview: codingsans.com/blog/importanc…
Hosted by @FancyKarolina, powered by @codingsans.
Key takeaways about supporting your team:
1. Define the different documents
Make sure everyone in your team has a clear understanding of the different types of documents you regularly work with. This puts you all on the same page.
1. Define the different documents
Make sure everyone in your team has a clear understanding of the different types of documents you regularly work with. This puts you all on the same page.
2. Provide templates
Provide templates for the different documents you expect your team members to write. A high level overview of the necessary contents, and a clear structure to follow can fit on just one page. Use it as a learning material and a reference point for your team.
Provide templates for the different documents you expect your team members to write. A high level overview of the necessary contents, and a clear structure to follow can fit on just one page. Use it as a learning material and a reference point for your team.
@ProductHunt’s unbelievable journey shared by the one and only @rstankov who has been successfully scaling teams and products since the very beginning🤙🤙
Hosted by @FancyKarolina, powered by @codingsans
Check it out at: codingsans.com/blog/leadershi…
#EngineeringManagement
Hosted by @FancyKarolina, powered by @codingsans
Check it out at: codingsans.com/blog/leadershi…
#EngineeringManagement
Here are some key takeaways:
Management is a different career
When you make the switch to management, you need to start from scratch. It’s a new career, and you need to use all your previous experiences in a new context. Rado tells some of his stories about facing this problem.
Management is a different career
When you make the switch to management, you need to start from scratch. It’s a new career, and you need to use all your previous experiences in a new context. Rado tells some of his stories about facing this problem.
Write a journal to track your progress
You can write a manager journal to track your effectiveness as a leader. Note all your thoughts and important events. You can go through it weekly, as you plan the next week, and review it monthly, to see if there are recurring problems.
You can write a manager journal to track your effectiveness as a leader. Note all your thoughts and important events. You can go through it weekly, as you plan the next week, and review it monthly, to see if there are recurring problems.
We go deep into integrating remote engineers to a distributed team with @g_the_engineer from @HudlEngineering.
Check out the interview: codingsans.com/blog/how-to-en…
Hosted by @FancyKarolina, powered by @codingsans.
#EngineeringManagement #RemoteManagement #DistributedTeam
Check out the interview: codingsans.com/blog/how-to-en…
Hosted by @FancyKarolina, powered by @codingsans.
#EngineeringManagement #RemoteManagement #DistributedTeam
Here’s the problem:
Remote engineers are cut off from their team. It’s even worse when the rest of the team is in an office together. The remote person misses out on a lot of interactions, and the team isn’t motivated to include them because they have each other at hand.
Remote engineers are cut off from their team. It’s even worse when the rest of the team is in an office together. The remote person misses out on a lot of interactions, and the team isn’t motivated to include them because they have each other at hand.
Here are some takeaways from the interview:
1. Move conversations to Slack
You might think, “Sounds great, but GL pulling it off.” There is a way, but you need to be very intentional about it. Start by moving professional conversations to Slack, and go from there.
1. Move conversations to Slack
You might think, “Sounds great, but GL pulling it off.” There is a way, but you need to be very intentional about it. Start by moving professional conversations to Slack, and go from there.
