Project Management

Please login or join to subscribe to this thread

7 rules to score with Tech People, what’s yours?

linkedin twitter facebook   Estimating   Information Technology   Requirements Management   Strategy  
avatar
Suzi MS United Kingdom
1. Be humble
2. Don’t tell the technical people how to do it.
3. Prioritise reusable effort if possible.
4. Always be clear on the objectives before meeting starts.
5. Don’t be dismissive and underestimate the effort.
6. Be generous with giving credit.
7. Always end with giving a deadline.

Courtesy from write up via PM Port, originally from https://hackernoon.com/to-all-project-mana...le-4a152b8005b0

Share your score here! Comprehensive list right? Wrong? Let’s hear from you!
Sort By:
< 1 2 >
avatar
SHADAV MOHAMMAD ANSARI PMO| ITC INFOTECH INDIA PVT. Ltd. New Delhi, Delhi, India
i would like to add short breaks and training .
...
1 reply by Suzi MS
Apr 13, 2019 6:17 AM
Suzi MS
...
Thank you Shadav for your views!
avatar
Suzi MS United Kingdom
Apr 10, 2019 9:25 PM
Replying to Deepesh Rammoorthy
...
If your Technical Person is good , encourage them to be better . Use them as your trusted friend , philosopher and guide .

Get out of their way and make them run and toil because they will revel in their sphere of excellence and will be more than happy to work harder if given the responsibility. They will be your workhorse and will remove the technical blockers in your project .

Be firm on your expectations from them - deadlines , scope, budget, quality but let them be flexible on the delivery and methodology within established tolerances.

Make sure that they understand that you are the enabler and offer to remove roadblocks from their way and shield them from project management politics.

Be humble and try to learn as much as possible from them regarding the high level technical stuff. As you keep insisting that they summarize the technical details in a non-technical way , They will also learn the art of tailoring their technical speak with non technical people , which is another valuable skill for them to develop.
Thank you Deepesh for your views!
avatar
Suzi MS United Kingdom
Apr 10, 2019 10:52 PM
Replying to Rangarajan TM
...
Great points to avoid burning the bridges between Tech & Non tech groups.Instead foster a powerful peer relationship that clearly brings the positive impact of ‘Unity is Strength’.It’s easy to say this but very difficult to put in practice.Not impossible though !!!
Thank you Rangarajan for your views!
avatar
Suzi MS United Kingdom
Apr 11, 2019 12:34 AM
Replying to SHADAV MOHAMMAD ANSARI
...
i would like to add short breaks and training .
Thank you Shadav for your views!
avatar
Adrian Carlogea Australia
Apr 10, 2019 5:37 AM
Replying to Sergio Luis Conte
...
Do not talk with them, They always talk with the computer only.....jejeje
Best advice ever. :P

Now realistically as a PM you have to talk with the "technical" people but if you don't come from the same line of work as they do it is better to keep at minimum the discussions as you may annoy some of them very quickly.

Before talking to a tech guy think it very well and try to avoid the discussion if it is not really needed.

I have met such grumpy technical people especially in IT Infrastructure as we were afraid to talk to them. Software developers are better but still some of them, usually among the best, are very grumpy too.
...
1 reply by Suzi MS
Apr 21, 2019 4:11 AM
Suzi MS
...
Thanks Adrian for your valuable comments! I have certainly dealt with one or two who don’t do jokes at all ;-)
avatar
Adrian Carlogea Australia
1. Be humble
- This is always good.

2. Don’t tell the technical people how to do it.
- You can't do this anyway unless you come from the same line of work as they do.

3. Prioritise reusable effort if possible.

4. Always be clear on the objectives before meeting starts.
- Usually they know better what they have to do.

5. Don’t be dismissive and underestimate the effort.
- The tech people and not the PM estimate the effort so even if you underestimate they will not finish faster.

6. Be generous with giving credit.

7. Always end with giving a deadline.
- How can you give a dead-line if you are not a expert in that line of work? They give estimates and based on their estimates the dead-line is set. If the dead-line set from the estimates is not acceptable then you go back to the stakeholders you don't change the estimate.
avatar
Suzi MS United Kingdom
Apr 14, 2019 5:28 PM
Replying to Adrian Carlogea
...
Best advice ever. :P

Now realistically as a PM you have to talk with the "technical" people but if you don't come from the same line of work as they do it is better to keep at minimum the discussions as you may annoy some of them very quickly.

Before talking to a tech guy think it very well and try to avoid the discussion if it is not really needed.

I have met such grumpy technical people especially in IT Infrastructure as we were afraid to talk to them. Software developers are better but still some of them, usually among the best, are very grumpy too.
Thanks Adrian for your valuable comments! I have certainly dealt with one or two who don’t do jokes at all ;-)
avatar
Alyne Padilla Lynch Sr Business Process Analyst| Communications and Finance Industry Sacramento, Ca, United States
Great talking point! I relate on many point, but specifically appreciate - "Don’t be dismissive and underestimate the effort." In relation to this, I'd say make an effort to understand their process by analyzing their tasks and/or IT specific area. For example, building virtual servers may involve the collaboration of other teams that your primary tech contact doesn't have control over. Other teams can include InfoSec for security reviews. That department may have their own extensive process that directly impacts your tech contacts timeline and tasks. Understanding what the process involves (not how to build or all the steps to build, but rather a high-level understanding of what is involved) will help in aspects like trust, appreciation, understanding and team work.
...
1 reply by Suzi MS
Apr 23, 2019 8:59 AM
Suzi MS
...
Absolutely prep ownself is definitely crucial to be able to ask the right questions at the right time with the right terms and tones. The more complex the case is, the more prep to be done like the scenario you’ve mentioned! Thanks for your valuable comments Alyne!
avatar
Suzi MS United Kingdom
Apr 22, 2019 6:46 PM
Replying to Alyne Padilla Lynch
...
Great talking point! I relate on many point, but specifically appreciate - "Don’t be dismissive and underestimate the effort." In relation to this, I'd say make an effort to understand their process by analyzing their tasks and/or IT specific area. For example, building virtual servers may involve the collaboration of other teams that your primary tech contact doesn't have control over. Other teams can include InfoSec for security reviews. That department may have their own extensive process that directly impacts your tech contacts timeline and tasks. Understanding what the process involves (not how to build or all the steps to build, but rather a high-level understanding of what is involved) will help in aspects like trust, appreciation, understanding and team work.
Absolutely prep ownself is definitely crucial to be able to ask the right questions at the right time with the right terms and tones. The more complex the case is, the more prep to be done like the scenario you’ve mentioned! Thanks for your valuable comments Alyne!
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS
ADVERTISEMENT

Sponsors