Future Legacy: A Perspective on Your Present Self #2 #cong24 #legacy

Synopsis:

You can not control your legacy because your legacy does not come into being until you are no longer in the society.

Total Words

831

Reading Time in Minutes

3

Key Takeaways:

  1. Your legacy comes to life as you go out of it.
  2. Great acts lead to longer living legacies.
  3. You have no say in your legacy.
  4. Time heals all wounds and erases all legacies.

About Claude Warren

Claude Warren is a Senior Software Engineer with over 30 years experience. He is currently lives in Ireland . He spends his time working on open source projects and with open source foundations. When not slinging code, he spends his time composing and playing guitar. He has presented talks on cross cultural teams, supporting open source, and innovation. He tries to mentor new developers.

He is a founding member of the Denver Mad Scientists Club and winner of the original Critter Crunch competition.

This biography outlines the bits he hopes will be his legacy.

Contacting Claude Warren:

You can contact Claude by email.

By Claude Warren

Legacy is how we view the past. All history is legacy. What you know about your favourite author, footballer, musician, or poet is their current legacy. But legacy changes over time.

For example, Thomas Midgley Jr. was thought to be an inventive genius. He developed a method to make high compression internal combustion engines stop knocking, making the modern automobile possible. He then went on to invent a way to replace the noxious, flammable gasses used in refrigeration, making the systems much safer. The Society of Chemical Industry awarded Midgley the Perkin Medal in 1937. In 1941, the American Chemical Society gave Midgley its highest award, the Priestley Medal. This was followed by the Willard Gibbs Award in 1942. He also held two honorary degrees and was elected to the United States National Academy of Sciences. In 1944, he was elected president and chairman of the American Chemical Society. When he died, later that year, he was considered one of the greatest inventors of all time.

Fast forward to today and it is now said of him that “Midgley had a more adverse impact on the atmosphere than any other single organism in Earth’s history”, and that he possessed “an instinct for the regrettable that was almost uncanny”. Midgley was also seen as a “one-man environmental disaster”. How did he fall so far so fast? Midgley was the man who invented leaded gasoline and freon.

Midgley’s legacy, though not as he had hoped, is probably now secure, or at least as secure as it can be. At some point people will forget that Midgley ever existed. Leaded gasoline has never been seen by today’s younger drivers, and freon has been banned for several decades.

It is impossible to secure a legacy. At some point all great works are lost to the sands of time and all names as well. Legacies fade. Midgley is not as well known as he was in the 1940s or 1970s; eventually he will fade away. I am fairly certain that the guy who designed the great pyramids was well known in his day and celebrated in death, and probably spoken about for many years thereafter. He had a legacy, but today we know nothing about him.

As a software engineer, legacy is the old stuff. Legacy software is the old code that keeps the world spinning; without it, your bank probably wouldn’t work. Software developers tend to want to work on the new shiny stuff, but as soon as they finish the code and it goes out into the world it is legacy. It is, for better or worse, their legacy. They have no control over how the legacy is viewed. Nobody has control over their legacy, because legacy is what people in the present think of you in the past.

Everything is legacy. The new shiny stuff is just future legacy. I find it interesting that it becomes legacy at a specific instant in time. I think that this is true for all legacies. I believe that upon death, or withdrawal from society, a person’s legacy comes into being.

In Buddhism there is the concept of three types of lives:

  • * life with no beginning and no end – eternal life
  • * life with a beginning and an end – mortal life.
  • * Life with a beginning and no end – the life of a teacher.

Your legacy survives as long as someone remembers you or your teachings. Your core values will outlast your name and may outlast your genetics as an identifiable person. Your actions, teachings, and values will be twisted and molded to fit the particular circumstances of those that remember you.

Your legacy is not your creation, it is the creation of those that come after. Your legacy cannot be corrupted, it simply is or is not. And eventually it will fade into the background noise of history.

Champion or Underperformer #16 #cong18

Synopsis:

Ideas are worthless unless they can be delivered on time, to budget and achieving the anticipated benefits.
Delivery is usually by means of a project, programme or change activity but success in doing so is variable.
This blog describes an assurance process that significantly increases the likelihood of success and has been well proven in many other countries and businesses.

4 Key Takeaways:

  1. Independent peer review, a critical friend
  2. Supportive to the idea owner and delivery team
  3. A snapshot in the lifecycle of an idea
  4. Virtuous spiral of improvement

About Paul Passemard:

I am an engineer by background with 25 years experience in the oil industry in operations and major project and programme delivery. At the height of the UK’s North Sea Oil development I managed an oil industry consortium aimed at improving the performance of suppliers to the offshore industry
In 1989 I formed a management consultancy focussing on quality assurance and high performance team working. Through assignments with the UK’s HM Treasury I played a key role in developing the Gateway Process and rolling it out across central government departments and local authorities.
I am an experienced Gateway Reviewer and have led major project and programme reviews across the UK.

Contacting Paul Passemard:

You can contact Paul by eMail.

By Paul Passemard

Are you and your business a Champion or an Underperformer when it comes to taking ideas and delivering them as projects to a successful conclusion?
In 2013 50% of businesses surveyed by the Project Management Institute (PMI based in the UK) experienced an IT project failure. In 2014 it fell to 32% but rose again in 2016 to 55%.
Last year (2017) PMI used a slightly different approach and it separated respondents to the survey into Champions and Underperformers
Champions are those organisations that see 80% or more of ideas / projects being completed on-time, on-budget and meeting original goals and business intent, and that have high benefits realization maturity. In other words, their ideas / projects deliver the promised business outcomes.
Underperformers are those organisations that see 60% or fewer ideas / projects completed on-time, on-budget and meeting original goals and business intent, and with low benefits realisation maturity.
The research showed that within these categories, only 6% of Champions experienced ideas / projects deemed failures, compared to 24% of Underperformers. Overall, all organisations reduced the average amount of money wasted on progressing ideas. projects and programmes by 20% compared to the previous year.
Some reasons for the improvement:-
• maturing project management techniques – use of a project management office
• skilled project managers
• focus on benefits realisation
• peer engagement and assurance techniques.

Much has already been written about project (and programme) management techniques but I would like to describe an assurance process that has been effectively used in the public and private sectors to significantly increase the likelihood of delivering ideas, projects, programmes and other change activities on time, to budget and achieving the expected benefits. The process has been adopted across the public sectors in many developed countries in the western world. Sadly, although it is widely used across the public sector in Northern Ireland, the Republic has so far not adopted it.
Private sector businesses and industries have used the process for many years and have developed their own variations.
It is called the Gateway process and is a series of independent peer reviews at key stages of a project’s lifecycle, aimed at ensuring its successful delivery.
The process provides an objective view of the ability of a project to deliver on time and to budget.
It is not part of the project management process but runs in parallel with it and dips in at key decision stages..
The review is top down, evidence-based and involves interviews with key stakeholders culminating in a report, delivered to the project owner (the Senior Responsible Owner, SRO in government speak) on the final day of the review. This report is confidential to the SRO, containing recommendations based on the review team’s findings. In light of the recommendations, a Delivery Confidence Assessment (DCA) is awarded, indicating the potential for successful delivery.
The confidentiality aspect is important as the review is not seen as punitive or blaming anyone and project teams regard them as helpful and supportive.
A Gateway review is not an audit or a forensic examination of what has happened to date. It will only look backwards sufficiently to understand the current status and position of the project. The focus then is on the future and aims to identify risks that could derail or adversely affect the delivery of the idea / project.
Review teams are made up of independent, experienced practitioners who bring their prior knowledge and skills to bear to identify the key issues that need to be addressed for the project to succeed.
Interviews with key members of the project team may sound a bit intimidating but in reality they are more like fireside discussions. The ground rules are that project team members are interviewed individually so they can be open and honest, what they say is unattributable, they are not named in the report and if they identify an issue the review team will triangulate and test with other interviewees to establish that it is an issue perceived by more than one person and not just an individual having a personal gripe.
The Gateway process may sound a bit cumbersome and require too much effort for simpler ideas and smaller projects. The process can however be scaled to suit the size and complexity of the project and it is usual to set a de minimis cut off point.
Gateway reviews can be carried out at any time in the life of an idea / project.
Typically the key decision points are:-

  • strategic assessment
  • business justification
  • delivery strategy
  • investment decision
  • readiness for service
  • operations review and benefits realisation.

But the process is flexible and if a project owner senses that all is not well they can call in a Gateway review.
One question that is often asked is – do the reviewers need special knowledge about a particular project or programme? This aspect is often covered by having one member on the review team who has some expertise in the area concerned. However it is not essential as the issues that emerge are almost never to do with the technology of the project: they are invariably about the management, organisation and resources allocated to the activity.
There is good documentation of the areas that a review team should probe but it is not a strait jacket and experienced reviewers quickly home in on the real issues.
From an analysis of past reviews the following are some of the main causes of ideas / project and programme failure:-

  • Poorly defined scope
  • Inadequate risk management and failure to identify key assumptions
  • Programme and project managers who lack experience and training
  • No use of formal methods and strategies
  • Lack of effective governance (decision making) and communication at all levels

Brain Storming, Machine Learning, Humor and the Origin of Ideas #15 #cong18

Synopsis:

Brainstorming, machine learning, and humor follow similar paths to divergent results. In this talk I explore how such similar paths can lead to such dissimilar outcomes and what we can infer about the nature of ideas from them.

4 Key Takeaways:

  1. Ideas are built by following a logical progression of understanding about the nature of things.
  2. Humor is a twist in the tail of that progression.
  3. Brainstorming is equivalent to taking the humor result and finding a way back to the reasonable.
  4. Machine learning is the artificial development of the logical progression.

About Claude Warren:

I am Claude Warren the lead innovator at Wipro Galway. I have a deep interest in innovation, ideas and where they come from and how to promote their development. I first presented at Congregation last year when I spoke about the environment that is necessary to promote innovation. Here I take that presentation further and explore the nexus from which ideas spring.

Contacting Claude Warren:

You can contact Claude by eMail.

By Claude Warren

A group of mad scientists sitting around the lab. An event is about to start. The rules are simple: no idea is too far fetched, no idea is stupid. Reasonable ideas start the conversation but the concepts grow wilder and wilder as the suggestions come thick and fast. Until someone says: “You know you could do that if we did this.”

Software reviews thousands of points of data, analyzing each and understanding how they fit together by understanding when they occur at togeter at a nexus. The program moves step by step through the possibilities picking out the most likely path. Machine learning, discovering and following paths.

All three evolve from the ability to create and follow a logical progression. The comedian takes the logical progression and at the comedic break brings the listener up short and exposes a foible in the assumptions of the progression. The sudden shift that is still logically achievable is the base of humor.

The mad scientists brainstorming take the logical progression beyond reasonable and then bring it back again with a shift in the assumptions of the progression. Suddenly there is insight into the problem.

Software simply attempts to deduce the expected outcome, but could it be “taught” to make the unexpected leap to a different interpretation of the logical progression? If so could that be humor, or perhaps more frighteningly, could that be like the result of a brainstorm an autonomous idea?