почему большие компании так неэффективны
От: Codealot Земля  
Дата: 24.11.20 23:03
Оценка:
По моему, очень хорошее объяснение.

https://workplace.stackexchange.com/questions/164383/how-to-deal-with-colleagues-who-provide-partial-information

I've encountered this kind of behavior enough times that it seems like there's recurring themes at work in these situations. It's especially common for folks in cross-functional roles to experience these kinds of problems.

The first thing you'll want to evaluate is your own questions (see, How to get domain experts to answer questions correctly, completely & concisely). It's common for some people to eschew "open-ended" questions-- even if they're warranted. You might be able to reduce the burden of answering your question by making it specific and narrow enough that the SME (subject matter expert) can provide it to you off the top of their head or refer you to a resource which is hopefully more specific than "google it".

Next, consider that by engaging with you by providing you with information, the SME is effectively putting themselves and their department "on the hook" for what they said. What if they gave you incorrect information? What if you used that incorrect information and it lead to a serious problem? What if you misinterpreted an off-the-cuff statement? Or maybe everything you're told is totally accurate and you understand fully, but now, you created a dependency and the other team isn't free to change things without breaking your stuff. Who's responsible for all these kinds of problems? It's impossible to say, but in some workplaces, "blame-storms" happen and people get in big trouble for seemingly minor things they may have said or suggested. Some places literally require a traceable, versioned, formal document for any communication between groups. Yes, it can be THAT BIG of a deal. In such scenarios, you really have to make your communication with this other department part of a formal workflow. You'll need to engage with management between the two parties.

Finally, and in my experience the most common case, there's an issue of trust. They might not know you well enough to trust you to use the information they give you. Bringing outsiders into the internal workflow of a group, creates the possibility of the outsider exposing problems within the group to the larger organization. You might be seen as a threat to their way of doing things, or even their future employment. The only way around this is patience and taking the time to develop informal rapport with these people. If you can put yourself into a role where you provide something to them, they might be more willing to act reciprocally and "return the favor" by providing you information when you need it-- even if you were just doing your job by helping them earlier.

Ад пуст, все бесы здесь.
Re: почему большие компании так неэффективны
От: baxton_ulf США  
Дата: 24.11.20 23:30
Оценка:
Здравствуйте, Codealot, Вы писали:

C>По ...


немедленно расскажи это Билли ... или нет, сразу Джефу
Re: почему большие компании так неэффективны
От: varenikAA  
Дата: 25.11.20 01:18
Оценка:
Здравствуйте, Codealot, Вы писали:

почему большие маленькие компании так неэффективны?

Тут дело в планировании.
Вот я работал на ПР. основная проблема на мой взгляд — гигантское кол-во услуг(100-200, точно не помню).
Какая тут эффективность.
Не зависит от размера компании.
Чем меньше услуг тем эффективней работа.
С софтом аналогично, если на 1 единицу рабочую 10 проектов, 3 из которых на поддержке/доработке и еще 7 на стадии проектирования.
Отсутствие приоритетов и .т.п.
Да, еще есть понятие горизонт планирования.
Т.е. если управление думает на месяц вперед, то эффект будет соотвествующий.
☭ ✊ В мире нет ничего, кроме движущейся материи.
 
Подождите ...
Wait...
Пока на собственное сообщение не было ответов, его можно удалить.