Loading...
Answers
MenuHow do build a empowered and motivated engineering team?
This question has no further details.
Answers
I am assuming your question is more pertaining to empowering and motivating (rather than hiring).
I can outline some of the practices I have seen really result in high motivation and sense of ownership among engineering teams:
* Empathize - Your engineering team will work well and be more motivated if they see you as one of them rather than a person who doesn't understand their function. Show your geeky side to them, and show that you understand their thought process and drivers.
* Pick their brain on big and small decisions (roadmap, usability, whatever it is) - Product teams value being heard. The more you position yourself as someone who is WANTS to listen, is keen to have their inputs, you will be surprised at how involved they can get, and also how you can actually tap into a lot of smart ideas/thoughts from them that you can develop on.
* Take care to explain - show how you arrive at decisions. Share your research, competitive analysis, and even your thought process on arriving at a feature set or list of things for a release. Its stuff you would have worked on anyway - so no harm sharing with more eyes!
* Share customer feedback - nothing motivates your engineers than a positive interaction with a customer. Get them to see customer feedback. Have them sit in and observe some of the usability studies. (B2B - have them see you do some demos or do a successful sales pitch)
* Send out interesting articles, insights, business and tech articles with your comments/highlights to them on a regular basis (maybe twice a week?) - maybe even some analysis you did on competition or customer feedback
* Engineers like working with people they feel are competent and complement the work they are doing to build a great product. So make sure they see how everyone else around them is also doing a good job and adding value and contributing to the success of the product.
* Be transparent about the product/business - Make them feel they are responsible and involved in the business, not just technology. I've seen engineering teams happy about their annual goals having components relating to making revenues, keeping customers happy, or reducing costs. If they are enthused about the business as a whole, they will be more motivated with their engineering efforts
* Have a mix of little experiments, R&D, attending to engineering debt, in addition to bug fixes and new features that each engineer gets to spend some time on (based on their interest)
* Finally get to know each of your engineers personally, and be aware of what their priorities are. Each of us has different motivations in life, so there is no silver bullet to motivate people. When they know you care for them, they are more motivated :).
“A team is a group in which the jobs and skills of each member fit in with those of others as - to take a very mechanical and static analogy - in a jigsaw puzzle, pieces fit together without distortion and together produce some overall pattern.” (B. Babington Smith, as quoted by John Adair)
The drive to be part of a team seems to be instinctive and probably originated when human beings came down from trees to live on the open plains. The challenges early man faced were problems of scale, for example, in facing a threat from a pride of lions, and problems of complexity, primarily in how to handle a range of environmental threats to find food, shelter, warmth, and safety. Leaving everyone to sort things out for themselves had limitations. The answer was to pool resources and co-ordinate what everyone did. The concept of the tribe was born which in due course evolved into the concept of the team.
A successful team is one in which the team members not only achieve something special and worthwhile but feel as if they have participated in something special and worthwhile. Unlike a group, teams:
1. create varying levels of deep and meaningful personal relationships
2. arouse feelings in their members for what the team stands for
3. provide stimulus and motivation to those in them
4. provide various forms of synergy
5. are always developing
6. have purposeful unifying activity
7. feel special to those in them
While groups remain largely static, repeating what they do at a fixed or standardised level of performance, teams can grow and change and work towards an excellent level of performance. This development has 5 stages:
i. Stage the team is just a collection of people with nothing in common other than nominal membership of the organisation
ii. Stage the team is a group of people with loose links, eg sharing a building, meeting occasionally
iii. Stage the team come together on work which has a purpose and a goal that the members all share
iv. Stage the team start to see themselves as a distinct unit with a life of its own.
v. Stage the team consistently achieve things together and evolve.
To build an empowered and motivated team follow these steps:
1. Forming: The forming stage of team development is when people come together for the first time. The atmosphere is wintry, cold, and formal. Suspicion, distrust, caution,
and fear may exist. The main direction of interaction is between individuals and the team leader rather than between individuals themselves. Teams can get stuck at the forming stage if trust is low and there is no impetus for development.
2. Storming: If the group is led to move beyond the forming stage, it enters the storming stage. This is when the group starts to wonder if they can gain something from being in the group. Instinctive feelings may arise about others in the group and there may be differences about exactly how to proceed and whose ideas will dominate. This is the sorting-out stage of the group’s growth and can be characterised by conflict and differences.
3. Norming: If the group is led to move beyond the storming stage, it enters the norming stage with agreement on strategies, systems, and structures. People start to see a purpose bigger than their own and there are the beginnings of putting others’ needs ahead of one’s own within the framework of mutual gain. The norms may include a blueprint for how the team works together.
4. Performing: If the group is led to move beyond the norming stage, the group start to see that, in working together, they can achieve something greater than the sum of their individual efforts. The focus now moves from sorting out their own issues to delivering something for the benefit of others, principally their customers or stakeholders. As the performing stage develops, the team become willing to take risks and face challenges that they would never have contemplated before. The team becomes a highly positive, can-do unit.
5. Disbandment: It is tempting to keep a well-performing team going once it has reached a satisfactory level of performance. After all, this is what it was formed for. However, while some teams manage to prolong their success for some time, it is organisational life for complacency and self-satisfaction to creep in once a team reaches a winning level. Then it becomes important to look to the future by disbanding and starting the growth cycle once more.
The manager of one-off teams can work with the natural process of team development, intervening only to create the right conditions for growth within the team itself.
• forming: emphasise the team’s identity and what binds them. Use “we”. Accept the team as a unit that can look after itself with your support. Build their confidence. Intervene only if the mix of individuals is not right.
• storming: encourage openness. Promote a safe climate. Allow healthy conflict. Avoid rescuing the team.
• norming: focus on what the team has in common. Link ideas. Seek interaction between the team members.
• performing: ensure people have the skills to perform. Provide regular feedback. Celebrate success.
• disbanding: manage change by looking ahead and moving on.
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
Related Questions
-
How do I become a mentor at 500 Startups?
As a 500 Startup mentor I would suggest the following 1) Blog about distribution, design and data. Those are the things that 500 values most and usually the fastest way to get on their radar. 2) Interact with @davemcclure (and all other partners) on Twitter 3) Attend geeks on a plane or other events they host. It's all about relationships and perception, so create opportunities to increase the probability of showing them that you have skills that are relevant to the companies they invest in. Hope that helps.DM
-
What is the best programming language for building multi-platform mobile software that is scalable?
I've been involved in several projects that hinged upon this question (generally start-ups or web+mobile apps), and it's not a clean or easy answer unfortunately! Plus every developer you talk to is going to try to sell you their services, but what you need is simply the truth! I'd suggest that you consider shifting your focus away from finding a best language. That sort of premise can eliminate options that are actually quite valid solutions. Keep in mind that any mobile app will require multiple languages working in harmony - all while used in a commercially consistent and standards-based manner. That's the part that determines your technical scalability! Almost every programming language can achieve this functionality with an experienced developer on your team. The best advice I can give you, is to consult with at least two people on this, and three if your app is os-specific. The most important insight will come from a "full stack" developer. One who's got a variety of enterprise experience, and can code at all levels of the stack. This person needs to have experience in leading a team of other developers, which forces the strategy of which technologies to use and why onto their plates daily. Secondly, you'll want to consult with a "front end" developer, who can tell you what's possible using advanced OOP JavaScript techniques (like Google's angular.js), because in an absurdly fast change over the past 3 years, much of the formerly back-end work has made it's way to the front-end, and is driven by JavaScript, predominantly JSON data, and awesome API's. The game has changed and the front-enders are the poor souls dealing with this rapid shift daily. To do this, they're also fantastic JavaScript programmers, which is a language that runs on all mobile devices and all browsers, too. Love it or hate it JavaScript is the most commonly used language in the world. Finally, if your app is OS-specific, you'll want to consult with a developer who works predominantly with the OS your app is built for. This person lets you know what's possible from the device POV, should know what stacks and JavaScript approaches can and can't be done on that OS, and how to leverage the resources of the device for your app as well as extend it's functionality. BONUS - loop back to the full stack developer to double-check the claims of the front-ender and the mobile developers. Always double check with your most senior programmer ;) All of these consults together in addition to your own research and due diligence will get you comfortable and allow you to navigate on this rather daunting but deeply important journey. There aren't any turn-key options. Instead it's a series of inter-connected modules driven by different languages, and all working in tandem. Every solution will have bugs, and no one group of technologies can do everything without proper developers. If you'd like to go further down the rabbit hole, then we should definitely set-up some time to speak. Otherwise, I wish you great luck in research and encourage you to learn as much as you can! :) It's going to seem hard, and might give you a headache here or there, but learn everything you can about how different technologies "talk" to each other, and then you will be able to build a map for keeping your app and business scalable regardless of the changing tides of technology!MM
-
Can my experience with building "no code" applications be translated into something that will impress hard core coders?
Your skills would be most useful if you were starting your own startup and needed to make an early prototype to show to investors or potential cofounder developers. Your experience in debugging, testing, and agile, could help you get a job as a product manager, and the fact that you have a background in some sort of 'coding' will help too. It's very unlikely that it would help you get an actual dev job though, since you wouldn't be able to translate your programs into actual code that could be taken over/continued by other devs. Even if the programs you mentioned do allow you to export as code, it's unlikely that it would be exported in a way that's very usable by other devs.LV
-
What is the best online training course registration and management software?
I've used a ton of different plugins and services to create and sell online courses, and here's the best combination I've found: WordPress + Gumroad + ProductPress 1. WordPress: You'll use WordPress to host your course content. I typically put each lesson in a new Page. 2. Gumroad: Use Gumroad to sell your course, handle payments, and to communicate with your customers. 3. ProductPress: the ProductPress plugin will allow you to connect your WordPress site and Gumroad account together. As soon as someone buys your course on Gumroad, they'll automatically be emailed login information for your WordPress site. It's only $39 (one-time fee). More information here: http://productpress.meJJ
-
What are the pros/ cons of outsourcing app development vs. building an internal development team? Would this affect the value of the company?
Don't Outsource. Period. While there are big drawbacks with outsourcing related to building internal expertise the real reason I would never outsource at your stage is the need for speed and flexibility. Per your description, you are an early stage start-up with a MVP that is gathering data. Congratulations as that is a big accomplishment! However, you inevitably have a ton to learn about what your prospective customers need most and what customers deserve your attention most. The means you will be tweaking your product constantly for the foreseeable future and having to submit ideas to an outsourced team, make sure they understand what you want, wait for the new feature to be scheduled, etc is just too slow and too expensive. You should have your developers literally sitting next to you and (if you have one besides yourself) your product person so you can quickly and constantly share information. Good luck! You are in for a fun ride...GH
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.