5 ms·
The problem we face at my company is that it's very difficult to get people to use these kind of tools. My team is remote so we use slack and other apps all th
by pier25 9y ago
The problem we face at my company is that it's very difficult to get people to use these kind of tools.
My team is remote so we use slack and other apps all the time, but getting customer service or other depts to use a simple chat is difficult. Implementing something like Asana or Basecamp is impossible.
How did you implement those tools in your company?
- ec109685 9y agoIf the boss says use X, they refuse?
- flukus 9y agoYou aren't wrong, but tools people hate will get used as little as possible. With Basecamp for example, people might create tickets but then all the discussion about them is done via email rather than the ticket itself. It's enough to not get fired but still an overall poor result for the company. A little while ago I wrote some docs for a project, a simple markdown readme basically, but the boss decided that all documentation has to be in sharepoint, so I converted it to a word doc and threw it in sharepoint. My takeaway lesson was not to not document anything though because I hate using sharepoint and Word for. A top down command like "use x or get fired" isn't particularly helpful, making the right thing to do the easiest thing to do generally is though.
- jmiserez 9y agoThey may say yes, but then still use backchannels like email and phone to get things done. Which makes the items on the platform out-of-date, underused, or plain wrong. And items people actually put on the platform won’t get done or updated without also writing emails or calling. It takes time to get everyone on board, but if the platform works well people will change.
- pier25 9y agoNo, they use it the first day, and then progressively less. Since this has happened a few times with different tools management has abandoned hope.
- devopsproject 9y agoI've dealt with this in the past and am dealing with it again with a very simple trello board. "What is the status of issue X?" "What is the IssueID?" "I didn't create one" "Create an new entry in the tracker and we can all track progress of issue X" Repeat as many times as necessary. edit: I also try to create a trigger or other automatic action in the tool. For example, our issue tracker updates the release notes when items are modified or marked as completed. If you can get people to use the triggered tool it will create an incentive.
- TheSisb2 9y agoI once heard a story about a manager who let it be known he would give out 20$ if people used product management tool X. During one meeting, someone pulled up a note on said tool and he handed them a crisp 20$. A few more instances of that and everyone was using it. Or so the story goes...
- solatic 9y ago> How did you implement those tools in your company? You have to remember that tooling isn't valuable for its own sake. A chainsaw is much more powerful than a knife, but it's the wrong tool when you're sitting down to dinner. Getting new tooling adopted in the enterprise is about sitting down with your users, understanding what their goals are, understanding where their current pain points are, and showing them how the tooling will help them achieve their goals and solve their pain points, oftentimes requiring close, high-touch support and adaptation to get that done. If you can't sell the tooling on its own merits to people in your company, you have no business mandating its use.
- pier25 9y ago> If you can't sell the tooling on its own merits to people in your company, you have no business mandating its use. That assumes that a) such dept has the capacity to understand the advantage of using such tool and b) other depts have time to go and try to sell them that. Users always resist change.