Loading...
Answers
MenuWhats a productive method for changing workplace procedures in small company?
Specifically, a newly acquired small business with a staff of 4.
Answers
Being as collaborative as you can be is a good start. Outside of that, being honest and transparent about why the changes are happening is a good way to build trust with the new team. Keeping a positive attitude and energy around it will also help to soften the blow. Most importantly, continually ask the new team for their feedback along the way. This will help them to understand that while you are implementing new procedures to help things run "your way," you still respect and value their opinion.
Best of luck!
I think the best way to do that would be to sit down with them first to find out what they think is or isn't working and to discuss ways to improve the office. If you can get them involved in the change process you'll get a lot more buy-in. They may even come up with similar or better ideas.
But be sure they understand that while you're allowing it to be a collaborative process, it's you who has to make the decisions and not all decisions will be popular, but they are what's best for everyone in the long run.
First, you need to be crystal clear if the changes to the procedure still supports the policy (or goals) mandated for the organization (ie. Compliance directive, as many HR departments have). If the change impacts this negatively you may want to think twice before moving forward, so as not to put the small business at risk. If ok to move forward, keep in mind procedures are the “recipe for success” that support policy. They are the step-by-step tasks. You don’t mention your level of authority over the acquired small business however the person in charge has every right to direct change. The most simple mentor is to introduce what’s changing, highlight the benefits and say, “effective on such and such a date we will be moving to this new workflow.’ Your procedure should be documented and part of a larger set of documented company assets. It should be easily accessible for all to access. Remembering that change can be difficult for some people you may want to ease into the discussion dropping hints about the benefits of the new method and proposed changes. You’ll also need to ensure training plans are sufficiently in place for a smooth transition. Expect that a smooth transition may take 3 or more weeks depending upon the nature of the change and addition of any tools / additional training req’d. Plan accordingly and be supporting of questions. You can also have some or all of the group pilot a project with the new steps and share feedback. Maybe there’s opportunities to learn from and pick the best of the best between what the staff currently does and what you’re proposing. Be open to learning and sharing for a smoother transition and ‘continuous’ process improvement. Good luck! If you have questions feel free to reach out.
One left-of-centre strategy I've seen is to have employees document one of their work procedures each day in a central, online SOP. Make it really simple & fast to add the procedure.
Next, run a small competition where employees can, with a positive bent, add suggestions for ways that procedures can be streamlined. Have the winner be the person who provides the most, positive, useful feedback that benefits the company.
The best way to change things especially in a new acquired business is to listen and watch. Understanding your team, who they are, and what makes them tick is one of the most influential thing you can do.
Getting their opinion is important, I would construct a model of change and present it as a conversation and get their input. The only way to truly implement your model is to develop a followership before implementing your change strategy.
Related Questions
-
If you could ask each of your employees a question each day, what would you ask?
"What was the best part of you day?" Ideally you could ask in the afternoon .. but it sets a positive intention. I ask this to all my friends + wife everyday when I see them.DM
-
What advice would you give me when I take over a new department with a weak team?
For the first 90 days, listen and plan - but don't do anything. You need to understand why they are under performing and 9/10 it's because the previous Manager was just not a good Manager, could not recognize people's strength's, had them in the wrong roles, tried to do their jobs etc etc Read "First break all the Rules" - get to know your team, get to understand their strengths, get people in the right roles (plan a change if reqd) and then your focus after that is break down the barriers that stop your team being successful and get out of their way. “Now, discover your strengths!” that Swier suggests is also a marvellous book\resource to help you in this task. You are in a very fortunate position - there is nothing more rewarding than turning this situation around and there is only one way to go.... up... and that will get you noticed. It is much harder to take over a high performing team and either keep that going or further improve on it, as it's very unlikely you'll get the chance to really meet the previous Manager and understand why they had success and that team's loyalty will be with the previous Manager - this team will be looking for someone to lead, guide them and help them be successful as no-one goes to work wanting to under perform. Show and help them to achieve that and they will do and achieve remarkable things and you will be so proud of them as you watch them develop, achieve, grow in confidence and keep going. So, give thanks for having landed such a great career opportunity and go enjoy it.MH
-
If an employee receives another job offer and can't make up their mind, what's the best way to force them to make a decision and stick to it?
It's great that this employee has been transparent about the fact another company wants him. The problem is that this employee is ambivalent about his connection to your Company. Really, under 100 employees at least, this is unacceptable. I would first reflect on why you think he's looking elsewhere. Then, I'd ask him that, admitting that you have failed to create an environment in which he has stayed engaged and motivated on what he's working on. If his answers seem reasonable and you can commit to making the changes necessary, then you won't need an employment contract, he'll stay on his own desire, because you listened to him and improved his situation. If his requests seem unreasonable or you know you won't be able to make those changes, fire him *today.* This situation can contaminate your entire company quickly. Yes, swapping someone out will always be a bit of a setback, but you want *everyone* on your team, feeling motivated and excited by what they're doing. It sounds like you're making your decision out of fear (having to find and hire another engineer) versus what's best for the Company, long term. Happy to talk to you in a call. Problems like this are within the sweet spot of my skills and passion.TW
-
What is the best way to evaluate a candidate for product manager?
Some of this is stage dependent and all of it is highly dependent on the team above the product manager. The simplest answer of course is to find PM's from companies who have had exemplary success where the Product Manager candidate either led prior success or was exposed to it in a meaningful way. A simple starting point is to ask them to give you examples of conflicting opinions on a feature and how they evaluated the conflicting opinions and made a decision and tracked the success or failure of that decision. AirBnb actually gives PM's homework as part of the interview process where they have to actually present a unique idea (from scratch) to the interviewing team. Happy to talk to you about best process based on your stage and existing team.TW
-
How can I manage my developers' performance if I don't understand IT?
Whenever you assign them a task, break down the task into small chunks. Make the chunks as small as you can (within reason, and to the extent that your knowledge allows), and tell your devs that if any chunks seem large, that they should further break those chunks down into bite size pieces. For instance, for the overall task of making a new webpage, _you_ might break it down as follows: 1) Set up a database 2) Make a form that takes user email, name, and phone number and adds them to database 3) Have our site send an email to everyone above the age of 50 each week When your devs take a look at it, _they_ might further break down the third step into: A) Set up an email service B) Connect it to the client database C) Figure out how to query the database for certain users D) Have it send emails to users over 50 You can keep using Asana, or you could use something like Trello which might make more sense for a small company, and might be easier to understand and track by yourself. In Trello you'd set up 4 columns titled, "To Do", "Doing", "Ready for Review", "Approved" (or combine the last two into "Done") You might want to tell them to only have tasks in the "Doing" column if they/re actually sitting at their desk working on it. For instance: not to leave a task in "Doing" overnight after work. That way you can actually see what they're working on and how long it takes, but that might be overly micro-manager-y At the end of each day / week when you review the tasks completed, look for ones that took a longer time than average (since, on average, all the tasks should be broken down into sub-tasks of approximately the same difficulty). Ask them about those tasks and why they took longer to do. It may be because they neglected to further break it down into chunks as you had asked (in which case you ask them to do that next time), or it may be that some unexpected snag came up, or it may be a hard task that can't be further broken down. In any case, listen to their explanation and you should be able to tell if it sounds reasonable, and if it sounds fishy, google the problem they say they encountered. You'll be able to get a better feel of their work ethic and honesty by how they answer the question, without worrying as much about what their actual words are. Make sure that when you ask for more details about why a task took longer, you don't do it in a probing way. Make sure they understand that you're doing it for your own learning and to help predict and properly plan future timelines.LV
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.