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
-
How do build a empowered and motivated engineering team?
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 :).SG
-
How can I open a US bank account for an LLC without traveling to the USA?
I am based in Canada and ended up opening a US bank account with Harris Bank in Chicago without physically visiting their office. This was about 4 years ago. So maybe contact them and see if they could help you.AC
-
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
-
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
-
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
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.