Loading...
Answers
MenuWhat questions should we have our employees answer each week in a standard "wrap up" email to management?
Answers
I think that it would be important to answer the following questions.
* Who comes up with the "thoughtful questions"? And are they new every week?
* Who is responsible for the answering of these questions?
* What is the pace of the start-up?
* Will every team's concerns / progress / roadblocks / setbacks be relevant to management?
* How much time should each team spend on developing its response (related to point 2)?
* "...help employees feel heard, ..." - How do you plan to measure this?
* Is a weekly cadence the right pace?
** Can teams align their "wrap-up" with their natural development cycles (this is more relevant if the company is a technology company)?
* Will these wrap-ups be relevant to other teams?
Answering these questions can help develop how relevant these emails are both to employees and to management.
This seems like a good idea initially, but I think you'll find it's incomplete.
Here's the problem: for the employee, sticking their neck out and telling the truth is a potentially career-limiting move.
So they will never tell you the full open truth.
From experience, the best format is to use an impartial intermediary the employees do not report to, and whose stake is not in management's way of doing things.
Then employees can open up.
Why do you think Suggestion Boxes are anonymous?
I have served as advisor to some HR managers and growing startups on these issues, and we have found that the first principle is guaranteed anonymity for any software-initiated polls. While open ended answers give more data, they also open the employee up to identification and pollutes our information.
Best approach is a mix of in person approach and online polling, the personal touch allows for people to share attitudes they didn't even know they had. That of course requires a specifically trained staff, so online methods are preferred by industry.
This polling would be better aligned with events and important dates rather than periodic weekly intervals to prevent a "punch a button" feeling.
I'd be happy to elaborate more on best practices for polling in a call and show how even the in person methods can be introduced to complement them!
I believe this "send to management" idea will create hierarchy issues within your team and will limit your employees providing honest feedback to the "management"
Try this;
Each Friday afternoon work stops for 2 hrs. Everybody gets together, office turned to a social venue. Sandwich, Pizzas, Drinks (arrange as you wish) afternoon tea or even lunch
-First two weeks nobody will speak but its your job to open the conversation, talk and ask questions. They must be comfortable. Answer questions in front of them so they are comfortable approaching you, avoid confrontation reply later in private
-Talk about the past week, figures and plans next week, talk to top performing employees, share their story, tell a funny story from last week, talk about markets, share your opinions
-You can ask to prepare questions submit before the meeting or they can ask you during the meeting
-After a month this becomes a ritual, people will need to brings cakes etc,... team spirit.. ideas will flow and have a great impact on your business
-Be careful, if people asking questions about how to do their job, there is a training problem.
-if you are looking for a online survey, just buy one of from internet..if you are looking for a real-time chat platform buy one of from internet, if you are looking for a mail distribution use your email client
-Your employees is everything to you, make sure you interact with them
I would keep it as simple as possible. The more complex it is, the more likely employees will give up.
My advice; 4 categories;
Positive: what is going well this week/month...?
Negative: what is not going well?
Comments: neither positive or negative but worth mentioning
Actions: what do they want to do or want the management to do?
That's it...
Steven
Some great comments and suggestions here. I am often involved with such things since I Coach Executives and their direct reports. Anonymity is King at the outset. How employees experience almost every aspect of how you set the stage and then conduct this will determine how well it works. Simple is better. Three samples might be...
What is most getting in your way this week?
Who deserves an Award for what they did this week?
What have you been measuring this week?
And by all means somehow publish all the responses you get from whatever method you use
We've been now running Weekdone.com weekly team status updates and reporting service for over 3 years. Here is my experience.
First decide if the information you want to get is task-oriented or more about open-ended feedback questions. First is more item oriented (our standard template is PPP as used in Ebay, Skype et al meaning Plans, Progress, Problems). The second is based on questions to have employees open up. Here is one blog post I did on 10 questions I've seen that work well among our users: https://blog.weekdone.com/10-questions-to-ask-your-employees-today/
The key to get the process working well is by the way feedback and replies from you to employees, based on what they report. If you make it a one-way black hole from employees to managers it rarely works. It has to be 2-way communication. That's where many leaders fail. Without that employees take the attitude that nobody reads the updates and no changes are made by you and other managers.
Related Questions
-
What does your a team look like for a software company of ten or less people? Or, how do you think it should be?
Instead of looking at who does what .. why not look at the things that need to get done for a small techology team. Product: 6 people - 3 full stack engineers - 2 front end developers - 1 designer / product person Marketing & Community, 1 person - Full time hire, or CEO Support & Operations, 1 person - Part time hire, or CEO + Whole team I believe it's important for everyone on the team to help with support. Also, if you have a great product, then support shouldn't be that taxing. Q&A is usually needed when you have a bad development process (no unit testing or continuous integration deployments). Outsource everything else. - Bookeeping - HR stuff - Legal - Government program paperwork Hope that helps. P.S. I would put as many people on product as that's where you'll get the most bang for your buck.DM
-
How to deal with co-founders that aren't pulling their weight?
I feel your pain — I've been there several times in a couple of my companies. Each situation ended up being unique, and had to be handled differently. I think there are a few things to consider before you make your decision: -- 1. What is in your cofounder's way? Is you cofounder being held up by a lack of clarity? Lack of motivation? Lack of autonomy? One of my past cofounders was very good at getting the job done, but didn't naturally have the skill to lay out tasks in a manageable way. To get around this, I worked with the whole team (4 people) to write up process documentation that removed the need to "figure out what to do next" that was tripping up this cofounder. -- 2. What job was your cofounder brought on to complete? And is it being completed? One of my companies brought on a cofounder simply to give us a marketing platform — he had a huge online audience — but he did nothing else. At first, this caused tension; once we had specifically laid out who was on the team and for what purpose, it was easier to identify where responsibilities lay. -- 3. Is your cofounder capable of doing the job? One of the more painful ordeals I've gone through in business is bringing on a good friend, then realizing that — despite his talent and intelligence — he just wasn't able to perform the job I'd hired him for. His skills were better suited for a different job: he needs hands-on management; he works better with repetitive tasks that don't require big-picture thinking; he lacks assertiveness and confidence, which were critical for the management-level role he'd been hired to do. After I tried to clear everything in his way, it became clear the company couldn't survive if he remained on the team. I had to lay him off. -- 4. Do you just simply not like the way this cofounder works? In one of my startups, there was a cofounder who I didn't know all that well, but he had amazing industry contacts and domain knowledge. However, once we started working together it became clear that we had VERY different working styles. He drove me completely nuts with (what seemed to me to be) a very ADHD-style of planning, with projects starting and being dropped and then coming out of nowhere with a call at 21:00 to discuss something critical that would be forgotten tomorrow. I'm sure I drove him nuts, too. So eventually we ended up selling that company — it was that or shutter it — because we knew there wasn't a chance we'd be successful if we continued as we were. -- Working with other people is tricky in general. Our instinct is to assume that we're the best workers on the planet and everyone else is incompetent, an idiot, a slacker, or all of the above. Usually it's a combination of an organizational-level lack of clarity, poor communication, no processes, and (sometimes) plain ol' we-don't-see-eye-to-eye-on-things-ness. Hopefully that helps. Feel free to get in touch if you'd like to hear specifics on my situations, or if you'd like any help devising a strategy for resolving your cofounder trouble. Good luck!JL
-
Need some advice on how to build a team, and determining what kind of talent I need?
A great team looks like this - 2 full stack engineers. They can manage servers, security, build features and code front end JS/interactions. - 1 visual designer focused on product, information architecture, UX and flows. - 1 front end developer who can take designs and built out killer interactions and can wireup any back end code to the UI The CEO can manage product + customer development and everyone on the team does support. That's 5 people and can accomplish a lot!DM
-
There is a person working with you who has great skills but doesn't fit the culture, how far would you go with trying to help this person to change?
Backwards. I'd make sure that person didn't stay in the company. "One dirty fish muddies the whole pond" It's not personal or malicious - they're just not the right fit. A great skill set, while very important is always secondary to cultural fit if you really want your company to flourish.KM
-
From your experience, what are the 'key' rules to building a great team for the long-term?
Your question is very interesting and gives me a feeling you have a real commitment for success because it makes me feel you care for your team. If this question could be fully answered in a couple of lines, you can imagine all managers and executives would lead their teams successfully. The 2 key principles to remember are: 1. Everyone is different: you have to adapt to each individual. It is time consuming but pays off in the long run because everyone has their own learning styles, speed and attitude. Take the time to have 1:1 conversations about them as individuals: likes and dislikes, under what conditions they perform best, how they learn most easily and about their career goals. 2. Create a team spirit. This is the exact opposite of point 1: as much as you recognize everyone as individuals, you have to also build unity and cohesion. There has to be standardized rules of behavior, common values and a shared vision. You have to take time with your team as a whole. This will lead you to create: 1. A personal development plan for each individual in your team, which helps you develop a tailored approach for each person, create reward & recognition systems and monitor people's happiness and performance. This helps you understand your team from a micro-perspective. 2. An organizational development plan for your start-up to give you a more global vision of the talents you need to acquire, retain and grow. This helps you understand your team from a macro-perspective. Team building requires taking time for all the different aspects of bonding: forming, storming, norming, performing, mourning. It's always about balancing two extremes: On one hand you want to take time to work together and alone, to learn & grow, to brainstorm, to create, to plan, to prepare, to research and to measure performance. On the other hand you, you also want to take time away from the office to stop & think, take time to have fun, take time to get to know each other, take time to rest & relax. Do you need any guidance to build individual and organizational development plans that will support growth and team building for your start-up?NK
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.