BradEgeland.com #PMP #PPM #project #Agile #cybersecurity #planning #ai #SAFe #coronavirus #virtual #mindmap #remote #COVID19 #scaledagile #fintech #webdesign
  • Welcome
  • Contact
  • Mentoring Contact Form
  • Expertise
  • Blog
  • Find Local PM Jobs
  • Books / White Papers
  • Software / Service Reviews
  • This Week in PM
  • PM Video Series
  • Awards/Recognition
  • Templates & Downloads
  • Clients
  • Professional Services
  • Past Survey Results

Don't Let Technology Drive the Solution

12/24/2020

0 Comments

 
Picture
Picture
Is that cutting edge Cybersecurity technology making your CSO drool and ready to pay boo coos of internal dollars on a bleeding edge tech project to showcase at the next user conference or Black Hat digital security convention? Is that latest platform recently available to showcase your web apps on recently available and ready for you to use?


Making a project come to life because of the technology that an executive wants to try or wants to say that his division is using is a bad reason to have a project. And I feel it goes against some sort of unwritten code of ethics for project managers but I will get to that in another article, most likely (these ideas have to come from somewhere).


Here's my take... never ever ever ever make the project about the technology. It can be awesome. And it can be disastrous. You can end up being in the latest tech magazine and your stock may soar. Or you may end up on the heaping pile of Ryan Leaf NFL busts in terms of tech failures. You may find that bust lands you with a headline on CNN about a tech startup losing a billion dollars on a failed project to implement a new security solution that ended up in security breeches, identity theft and lawsuits because your tech team wasn't quite ready to handle such a project. But then again, they say “there is no such thing as bad publicity” - there is always tomorrow to fix it or capitalize on it. Unless of course this bad decision put you out of business. Then there is no tomorrow.


So what do you do when it appears that the customer or your senior management wants to jump in head first because of the technology? For me, it comes down to these three things...


The end does not justify the means. Getting there isn't really half the battle. Getting there successfully with the right solution is the whole battle – the whole project. There is no half battle or partial project. It's all or nothing. It's not about the right process or the coolest technology or the headlines... good or bad. It's about the successful solution. I had one organization I was leading a project for where the client company was so excited about our solution we were implementing – the first of it's kind in their industry – that they went ahead and published go-live dates in a major industry publication under assumptions made with and by the account manager in our organization who sold them the project.


Unfortunately, those dates became the hard and fast - or “drop dead” - deliverable and implementation dates that I had to build my project schedule backwards from in order to complete and meet the deadlines. There were no other options and no option for me to put together the realistic schedule that I knew and my team knew we could meet safely and accurately. What happened? My team and I found ourselves working onsite at the customer location for two weeks just before Christmas working through issues to get to go-live on time. Blew through money (beyond budget) faster than Usain Bolt can run 100 meters, but we made it!


The desired technology may not be right. The obvious problem is that the desired technology – this bleeding edge choice for the solution – may not be the right technology. The project team needs to understand business processes, what the “as is” environment is and what the desired “to be” environment should look like and figure out if the customer's perception of the project is the true need or if the project is bigger (or smaller) and the customer request or need is merely a symptom of the real project. Then, and only then, can the project team step back and formulate the real project. Following that, they can – with the customer's input – identify what a technical solution should look like including what the proper technology to implement really is. Still hopefully a cool one, but it may not be what the customer is hoping for. “Backing into” the solution from the technology is the wrong way to go... it's like reading English from right to left... pretty painful... bad outcome... headaches.


The skill set may not be there. Finally, the team may not have the skill set to implement the desired technology. That doesn't mean it can't be done. But it probably can't be done without a change order to get the right resource or resources onboard – at least temporarily and probably expensively – for this specific project. Don't get me wrong, implementing a bleeding edge technology in any industry for the first time is feather in the cap of the delivery organization as well as a gem on the resume of the project manager, the business analyst and the entire project technical team. Win-win-win. And the customer organization comes out looking great, too. So if they want it, and it's the right technology for the project team and the customer is willing to pay for it – or your organization can see the benefits of the end publicity – then go for it. The return on investment (ROI) for all involved to eat some costs will be high.


Summary / call for input


The project is the project. That's what the team needs to focus on. It's like putting blinders on because sometimes the customer or senior management will interject their needs and desires and those may be in direct contrast to what is best for them and for the project – and they don't realize it. Stay focused on the successful end solution while taking all these suggestions along the way, but resist the urge to act upon them. At least not until you've ensured that they are the best roadmap to success.


Readers – have you had customer project scenario where it was all about the technology and the success of a new solution? How did you calm the enthusiasm while you sorted through the need to determine if that was the best path for the project. You can just proceed with the customer request as is, but if you get to the end and implement something that doesn't really solve the need, the onus is on the delivery team, not the customer.

0 Comments



Leave a Reply.

    Author:

    Picture

    Brad Egeland


    Named the "#1 Provider of Project Management Content in the World," Brad Egeland has over 25 years of professional IT experience as a developer, manager, project manager, consultant and author.  He has written more than 7,000 expert online articles, eBooks, white papers and video articles for clients worldwide.  If you want Brad to write for your site, contact him. Want your content on this blog and promoted? Contact him. Looking for advice/menoring? Contact him.

    RSS Feed

    Picture
    Picture
    Picture
    Picture

    Archives

    December 2020
    November 2020
    October 2020
    September 2020
    August 2020
    July 2020
    June 2020
    May 2020
    April 2020
    March 2020
    February 2020
    January 2020
    December 2019
    November 2019
    October 2019
    September 2019
    August 2019
    July 2019
    June 2019
    May 2019
    April 2019
    March 2019
    February 2019
    January 2019
    December 2018
    November 2018
    October 2018
    September 2018
    August 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018
    January 2018
    December 2017
    November 2017
    October 2017
    September 2017
    August 2017
    July 2017
    June 2017
    May 2017
    April 2017
    March 2017
    February 2017
    January 2017
    December 2016
    November 2016
    October 2016
    September 2016
    August 2016
    July 2016
    June 2016
    May 2016
    April 2016
    March 2016
    February 2016
    January 2016
    December 2015
    November 2015
    October 2015
    September 2015
    August 2015
    July 2015
    June 2015
    May 2015
    April 2015
    March 2015
    February 2015
    January 2015
    December 2014
    November 2014
    October 2014
    September 2014
    August 2014
    July 2014
    June 2014
    May 2014
    April 2014
    March 2014
    February 2014
    January 2014
    December 2013
    November 2013
    October 2013
    September 2013
    August 2013
    July 2013
    June 2013
    May 2013
    April 2013
    March 2013
    February 2013
    January 2013
    December 2012
    November 2012
    October 2012
    September 2012
    August 2012
    July 2012
    June 2012
    May 2012
    April 2012
    March 2012
    February 2012
    January 2012
    December 2011
    November 2011
    October 2011
    September 2011
    August 2011
    July 2011
    June 2011
    May 2011
    March 2011
    January 2011
    December 2010
    November 2010
    October 2010
    September 2010
    August 2010
    June 2010
    May 2010
    April 2010
    March 2010
    November 2009

    RSS Feed

Powered by Create your own unique website with customizable templates.