In Capital Deployment – tell me Paul – who’s the worthiest of them all?

All-Stars

Occasionally in these blog postings I have highlighted contributions from team players who make Capital a pathway to business efficiency for their companies.  

They were … (click blue for link)

  1.  Librarians: Without the underpinning of a complete, comprehensive and accurate electro-mechanical library your automation of engineering processes is diluted.
  2.  Product Managers at Mentor Graphics: Capital software products are architected, designed and realized into the market place by smart and talented people. The success of the software at customers is thanks in very large part to how their vision was nutured all the way out into the marketplace by them.
  3. Information Technology Professionals: They keep the application alive, they feed it with bandwidth and upgrade it and scale it and provide you with all the hardware, security, backup and configuration. Hard work which is often invisible though essential and so well done that to you it seems easy – but just imagine if you had to do it for yourself.
  4. Educators:Teach a person how to fish and they may complain that you were supposed to teach them how to use Capital instead. Every wise person acknowledges the debt they owe to teachers. It is important to go from theoretical knowledge and new immediate use of the software to a practical experience of how to apply new technologies as your company changes important business practices. As roles and relationships adapt to a new corporate direction being prepared to learn puts you in charge of your destiny.

 

 

Indispensiblest of them all.

An important question relating to deploying enterprise-class software like Capital is which one person/role is most important?   I mean pivotal, or the type of individual without whom you are really going to struggle. Who is s(he) and what it is that this person does and why is it more valuable than other contributions? Success is a team acheivement in most business situations.  However I think it is fair to ask are there individuals who are the most valuable players on the Capital team?

Here’s my answer, and I’m inviting a luminary from the Mentor consulting practice team to provide his answer to this question in a guest posting for contrast.

I have thought about this, and thought about various candidates … here are some of the distinguished runners-up.

1)      The manager or executive who signs the purchase order, who leads the team. Yes, a very important and somewhat overlooked role. Without good leadership the consequences can be short term failure or longer term loss of potential good. And no investment means there will never be a return on investment. Let’s simplify and say that in making your software a success your equation is input human endeavor + cash + motivation = yield. Leadership is the big ingredient in that formula. But a leader isn’t unique and irreplaceable, and there are many different styles of managerial and executive, and the advantages of different approaches are sometimes significant and sometimes marginal.

2)      The supplier’s roving technical support people, the restless relentless multi-talented multi-tasking application engineers. They catalyze and energize by formally, informally, creatively and repeatedly resolving problems and working on eliminating issues for the customers. Again, useful and often necessary people and at times doing essential work. But like with leadership, the subject matter experts coming your way from your account team or from consultancy practices come in many shapes and sizes. Some are adept in one part of the system to a very high degree or deep technical depth and shallow on others. Their personalities and predilections vary, and you may see different ones over time, and in different regions of your global business.  Again not unique and irreplaceable.

 

At the intersection of these 3 skillsets comes deep expertise

The key users are your expert users. 

My customer’s expert users I define as people who:

  • Are able to be straddling different domains (e.g. manufacturing and design, OEM and supplier).
  • Can listen to and understand the point of view of co-workers, commands respect for their own experience and achievements in the workgroup, advocate and participate devising and insisting on standards
  • Have the imagination to empathize with others, also the vision to see the larger corporate or process-wide interest beyond a sectional interest, and is assertive in articulating that vision, contextualizing issues. 
  • Possess openness to learning and a strong work ethic, are prepared to build up expertise by growing out of novice and intermediate stages.

 

These are the people on which a Capital implementation pivots from pilot projects to production. If you don’t have these persons staffing your organization in sufficient number and support/empower them and give them free rein and trust them, trouble will follow. 

You can lose your manager, another one will come along and slot into the role and learn the ropes. Your vendor’s application engineer may disappear, but another one can be hired and trained. 

If your expert users are not around to help you, it takes many months to elevate new people to the experience, knowledge and competence you have lost. The risk is big to your project.

Get your best people  – retain them – and keep them focused.

Safely navigate pilot projects.

Post Author

Posted January 16th, 2012, by

Post Tags

, , , , , , , , , ,

Post Comments

No Comments

About Paul Johnston's Blog

Capital is Mentor Graphics' global market-leading software for electrical system design, electrical analysis, system integration, cabling and wiring design, harness engineering and service documentation. My job title is Senior Application Engineer Consultant - that's a subject matter expert label if you don't want to work out what it means. Here are some of my observations and views - comment on them at your pleasure. Paul Johnston's Blog

Comments

Add Your Comment

Archives

March 2014
  • How to get the best out of your Capital sales person.
  • February 2014
  • The p-word of Capital.
  • November 2013
  • Mentor Communities and IESD – Capital and VeSys
  • March 2013
  • When you should wake up and retire your old software.
  • December 2012
  • All present and correct.
  • November 2012
  • Distance no object – time holds no dread.
  • Who did you see at the exhibition hall?
  • October 2012
  • Alleviating stress, eliminating risk. Because that’s how we roll.
  • January 2012
  • People who plan, prepare and perform.
  • In Capital Deployment – tell me Paul – who’s the worthiest of them all?
  • Keep no Secrets, Inflict no Surprises.
  • December 2011
  • No vacationing during the holidays then.
  • November 2011
  • Strength in diversity, collective effort and the overstretched analogy.
  • April 2011
  • Blunt talking happens at the sharp end.
  • In praise of the trainers.
  • March 2011
  • The things you should “just know” – IESF Detroit and Capital
  • No shock in the new any more.
  • February 2011
  • Listen – IESF 2011 Detroit Date announced as June 2nd 2011.
  • January 2011
  • Secrets no more: Staying or Straying in Programming – Commercially available tools or grow-your-own?
  • Secrets no more: Outsourcing or in-sourcing your electrical systems interconnect software.
  • November 2010
  • Do you have home grown or shop bought electrical interconnect design tools? Part 2:Don’t sit on the sidelines.
  • Build or buy
  • May 2010
  • Two to the power of N = $ saved or spent
  • Under-rated – often under-stated: #348 The Information Systems people
  • April 2010
  • In today’s world of {fill in the blank here} people do business with other people.
  • March 2010
  • IESF Detroit – 10 days from March 18th and counting down.
  • February 2010
  • Latent Hero Series: #277 the Product Manager
  • January 2010
  • Harness Cost Reduction – the movie; appearing now Website remodeled
  • Harness cost calculation: Miseries brought on by false estimates.
  • IESF – A different decade-type milestone. Scoop!
  • Predictions for twenty-teens Part 3: What will be different about wiring harnesses in the next 10 years.
  • Forecast for 2010 to 2020 Part 2: What will be different about business processes in engineering wiring harnesses in the next ten years.
  • Looking ahead in a new decade predictions Part 1: Winners will leverage the best technologies.
  • December 2009
  • More songs – the new Aerospace and Automotive Electrical and Electronic Systems Design Hit Parade
  • DSI – interfacing with design systems afterword.
  • A standard you can keep to. Perhaps longer than you want.
  • Standards are good – simple standards live longer.
  • November 2009
  • The little pieces of knowledge joined with the bigger ones.
  • Latent hero series #514: Getting dewey-eyed about librarians.
  • September 2009
  • International harmony
  • Show and tell
  • August 2009
  • Learn all about it.
  • July 2009
  • In praise of systems engineering.
  • June 2009
  • CHS: What has it to do with community and abiotic environments?
  • Choose wisely and once: Part 5 – Interoperability.
  • Choose wisely and once: Part 4 – CAD outputs.
  • Choose wisely and once – Part 3: Business Benefits
  • Perceptions differ
  • Choose wisely and once – Part 2: A model & it is looking good.
  • Be careful what you ask for. Choose wisely and once – Part 1.
  • Saving time is saving money. The half year review.
  • May 2009
  • Charleston International Airport
  • Zen thought for the day: For CHS customers, change is a constant.
  • The pursuit of perfection: enhancement requests for CHS.
  • The Electrical Systems Design Blog Song Contest – Top 10
  • Integrated Electrical and Electronic Systems Conference – IESF x 2
  • Things move quickly
  • Start with the end in mind