Who Do You Think You Are?

dating sites for professionals in usa Engineering management is a distinct discipline, one that demands new ways of thinking. This can be challenging as we tend to derive feelings of satisfaction and accomplishment from the code and solutions we push out. The key to making the transition is to stay flexible and observant.

donde conocer gente santiago  

conocer gente ingles traduccion Whether you are new to management or have been doing it for some time, it’s important to understand exactly what your role and activities should be in relation to the people you manage.

free online dating michigan Of course this will vary depending on the exact nature of the organization you work for. Smaller teams with limited budgets require people to double up on roles. This means you may be serving as both individual contributor and manager at the same time. This can be a very tricky situation – and one that works best if you have an open communication channel to your senior leadership team. Managing people is a separate discipline from managing code or technical architecture. While it is possible to do both simultaneously, expectations need to be carefully set – both with your leadership team, and the people you manage.

site de rencontre sа“ТЉrieux jeune gratuit

rencontre femme chatain In larger teams, the engineering manager does little if any code writing and direct implementation at all. Their primary role in the organization is to ensure that information and institutional knowledge are being gathered, streamlined and shared as efficiently as possible. If you find yourself getting bogged down writing code, something is wrong. Either you have been given unrealistic deadlines and are short developers to execute the work in time, or you have other systemic issues that should be addressed. Many times managers find themselves stepping in to fix things reflexively, without even knowing it.

speed dating hochschule pforzheim This is a real problem – and one you need to respond to as quickly as possible.

Stop Fixing Things, and Why It Matters

http://strensa.com/visilnica/1922 You may be asking yourself “We’re in trouble. Things are behind schedule. What difference does it really make if I chip in a few hours per week here and there to get the team over the hump and keep the drama down so we can all get back to normal working conditions?”

les fille cherche mariage There are a few reasons why this is a destructive way of thinking. Firstly, you’ve somehow managed to divide the work into “crisis” and “normal”. Once this kind of thinking becomes habitual it tends to spread across the organization – and will erode everyone’s effectiveness in the long run. Crisis management isn’t management at all – it’s hastily considered reaction using blunt tools which may feel right in the moment – but cut off your available options. Crisis thinking also clouds your team’s ability to put in place adaptive routines and policies.

Another problem with this way of thinking is it protects your team from feeling pain – which means they’re probably not learning and thinking through better ways of addressing workflow problems.

For example, has everyone half-heartedly agreed to use a certain framework or build process, but no one’s actually taken the time to learn the thing deeply? Or has the team clung onto an old way of building and deploying which is error prone and inconsistent, thus eating up time needed to get the code written, reviewed and fixed? In either case, if you’ve let this happen you have failed as a manager. Stepping in as a contributor is not going to fix any of these scenarios. In fact, they will just exacerbate the friction and uncertainty. Your job is to help the team grapple with the underlying problems and do what they need to in order to remedy things.

Your Side of The Street

The things femme hermaphrodite rencontre you are responsible for as manager include constant education and awareness about the product being delivered, the tools and methodologies used by the team, and the business cycle keeping the company on track. At the same time you must always stay focused on the people behind the decisions and delivery commitments. What they say and how they feel really matter. Unhappy people leave companies and take extremely valuable knowledge with them. Often times problems with engineers can be prevented if caught early, and communication channels are already well established.

Great managers set the pace and tone of the engineering team. This does not mean managing every decision or even commenting on them. It means showing up in a reliable way and doing the things you say you’re going to do. It means holding regular one on ones with your direct reports and providing a consistent forum where they can be heard. Sometimes it means putting your neck out to advocate for your team with upper management and take some heat. Conversely, you may need to pass the pressure down to your team in as unvarnished a way as possible in order to level set expectations and understand what is or isn’t possible.

If you’ve been managing a team for awhile and haven’t ventured into this kind of practice I recommend seriously considering it. This said, be very careful putting these kinds of things in place. Making large proclamations and setting up new managerial systems without a transition plan will likely leave you worse off than having done nothing at all. I will address transitioning team culture from formally dysfunctional to new and improved in a later post – it’s a huge topic.

Some Management Basics to Consider:
  1. Be an information conduit: gather, condense, extract, filter and deliver
  2. Credibility: do what you say you’re going to do, as frequently as you can. Don’t make promises you think you can’t keep
  3. Set the tone and rhythm for your team
  4. Learn your weaknesses, and delegate accordingly
  5. Constantly reacting usually means you don’t have a plan. Stop doing this!
  6. Educate yourself about your team in an ongoing basis. This includes both the tools and processes, but also how each person ticks and what they want.
  7. Mentoring: make yourself available to mentor and coach people on your team – but don’t step into this relationship lightly. Make sure the other party actually wants this from you.
  8. Communicate effectively – both up and down the stack. Sometimes this means saying as little as possible and endorsing someone else’s passion or plans. Other times it can mean raising a hand and saying the uncomfortable thing which needs to be said.

 

Leave a comment

Your email address will not be published. Required fields are marked *