科技回声

So we are a small coding shop, which has been contracted by a big brand (at least where we live) company to create a new system for some of their business process.a "Good proxy" for what the project is (NDA etc) might be an alert system for some of their IoT devices.The current system is very manual, and there are about 3 stakeholders at various levels, I.T, Finance, Middle Management (they very much against the new system,) etc.For the life of me, We can't get them to provide us the steps or process flow for when to alert who after what time, when xyz happens.Things we tried:- Sending list of confirming questions- Had verbal meetings, to "talk it out"- Send more diagrams and questions to capture the process, before meeting also.The results were:- No response to questions, after follow-up we got a meeting from middle-management (think the issues are here)- Got some new info, but mostly circle-talk- Received very negative feedback, where the middle management and only focussed on the questions or steps that where wrong ??The problem is, C-suite absolutely want this. So questions we have for HN is:- General tips for nailing down requirements ?- Tools or templates that has worked for you in the past ?- How to "win" middle management over ?- Anything else we should know

7 条评论

brudgers超过 1 年前

Anything else we should knowBig organizations operate like big organizations.The C-suite may want a notification system. But they are probably not the people who will receive an SMS at 2am.And if a C-something isn’t sitting in on your design meetings, they don’t want the notification system all that badly…and everyone in the large organization sees that.But also there’s the simple fact that large organizations have a retention bias toward employees who value small differences in status…we call the jockeying for small status differences “politics.”You don’t and can’t know the important details of the politics at play. And you are just hired help. They have long relationships and you don’t.Politics is the important point of your meetings. Opposing the project is a display of power. Criticizing it is one too. Championing it is not.They don’t want it and the c-suite hasn’t sold it to them. You are being paid to impose it upon them.Sure technically it might matter if the project succeeds. But what really matters is that you get paid.Good luck.

评论 #38656865 未加载

Chandraa超过 1 年前

First, get a sense for why the middle managers are against the system. Are they afraid of losing their jobs? Do they believe that it will add more friction to their process? You can do this by getting the stakeholders on a call and asking them to explain the why (which will make them feel included and important). Or if you can, visit them and say you want to shadow them to understand the process and in doing so get into their minds.Once you get that clarity, work with them to design a solution that works for them, and make it look like it's their idea not yours. Make them look brilliant.Much of success in hostile environments boils down to identifying the motivations of people and making new ideas theirs not yours.

codingdave超过 1 年前

Build a functioning UI prototype of the end result, then demo it to them while explaining that the demo matches the understanding you have gained from the answers you have received. They will then see where details are incorrect and give you corrections, which are often far more clear than responses to text and diagrams.Also, be sure to take note of the responses. If that meeting goes poorly, there is such a thing as a bad customer, and these look like they might be one. Drop them like a hot potato, using the results of the meeting to convince your leadership.

bell-cot超过 1 年前

Quick reaction: Start a rumor that C-suite is looking to axe the deadwood in their middle management, and sees "managers not aligned with the company's priorities" as obvious targets.

评论 #38653572 未加载

flappyeagle超过 1 年前

Do you have a project manager dedicated to analyzing and structuring requirement and communicating with the client? Seems like you need itTheir job is to remain in constant contact over email, meetings documents, slide decks, whatever it takes

评论 #38654477 未加载

oops超过 1 年前

Tell the C-suite what you told us and send them a bill for your time?

throwaway318超过 1 年前

> - No response to questions, after follow-up we got a meeting from middle-managementThey're busy running the company paying mortgages while C-suite believe nice sounding words and budgets are all the incentives needed. Welcome to middle management. Some in C-suite will get this.> - Got some new info, but mostly circle-talkYou're speaking different language. Speak company, not generic IT.> - Received very negative feedback, where the middle management and only focussed on the questions or steps that where wrong ??Again, welcome to middle management. It went wrong. There's an error. Fix the error. It's what they do. Again, speak their language.> - General tips for nailing down requirements ?Ask for their existing "provide us the steps or process flow for when to alert who after what time, when xyz happens" flowchart, escalation matrix, escalation tree or whatever it's called in their corporate language. Perhaps it doesn't exist. If they're ISO9001 it should, but perhaps not.Don't ask for meetings on your terms. Go sit in the team, attend operations meetings. Understand them. Corporates are anthropological studies.

7 条评论

brudgers超过 1 年前

评论 #38656865 未加载

Chandraa超过 1 年前

codingdave超过 1 年前

bell-cot超过 1 年前

Quick reaction: Start a rumor that C-suite is looking to axe the deadwood in their middle management, and sees "managers not aligned with the company's priorities" as obvious targets.

评论 #38653572 未加载

flappyeagle超过 1 年前

评论 #38654477 未加载

oops超过 1 年前

Tell the C-suite what you told us and send them a bill for your time?

throwaway318超过 1 年前

Ask HN: Best tips for getting workable user requirements from difficult managers

7 条评论

Ask HN: Best tips for getting workable user requirements from difficult managers

7 条评论