Tech Forecasting: Comments on 6 Years of Forecasts (3 of 7)

1-Fullscreen capture 12232015 105118 AM

Perfect forecast = Widespread Uber acceptance

Over six years of prediction shows, when the hosts were right, they were very right.  When they were wrong, it was usually because they were too early or because of a surprise event in the area they were forecasting.  Most of the big misses weren’t really misses – they were simply areas outside of what the show normally covers.  There were four areas that stood out when reviewing past podcast tech forecasting claims.

1. Forecast structure.

This is obvious, but the wording of a prediction / claim matters a lot.  “The iPhone will be big!” is much less quantitative than, “Apple Watch will not meet its 10 million unit forecast.”  Bundling forecasts makes things complex as well – “The Nook will never be more than 5% of the sales of the Kindle” assumes that Kindle will grow, but that the Nook will never achieve parity in market share.

The best predictions / forecasts were well worded.  There is a lot of insight made into things like, “The Internet of Things will have a retail app,” – but perhaps the fact that it is tough to word the forecast indicates that the forecast itself is unlikely to occur.  If it is hard to phrase the prediction, it is unlikely the prediction is ready to be made.

2.  Prediction source.

Who makes good predictions?  Over the course of the show back to 2010 there are some brilliant, highly accurate predictions.  Patrick Beja nails the Apple Watch.  Google Wave, RIM, Palm and many others were appropriately eulogized ahead of their deaths.  I could not interpret any pattern in who makes goods predictions about what field.

It did seem like experts in a field seemed less likely to make a comment about their area of focus.  JR Young – no comment on drones.  Patrick Beja – no comment on gaming.  Tom Merritt held off on Patreon prediction comments – even though he is arguably one of the world’s foremost experts on the platform.

Prediction structure appeared to matter more than the person making the prediction.

3.  Technologies not covered.

SpaceX_BlueOrigin

Predictions outside the area of the show aren’t often made.  As an example – SpaceX and Blue Origin both completed orbital recapture in 2015.

There were so many areas that were not forecast!  These Type II misses (error feels too harsh) – where a trend is occurring but there is no ability to forecast it, seemed very common.  There was never a forecast made around Tesla or electric vehicles (there was a prediction about a ‘big improvement’ in battery technology covering 2011).  No one predicted Uber.  Nothing about SpaceX.  No major predictions have been made about life science or medical technologies.

Forecasts about the start up community that is deeply tied to technology are few and far between. There is no mention of Unicorns.  There is one mention of a bubble – made by Sarah Lane in 2011.

4.  Predicting disruption.

For  the 2015 forecast show, DTNS 2397, that was published on December 31, 2014 there were predictions made about Uber related to their CEO and whether or not it would finally meet ‘general acceptance.’  I give that prediction a 100%, as Uber went from ‘not okay’ at my local RDU airport, to ‘okay’ over the course of the year.  However, Uber does not show up before that forecast.  Neither does the disruptive tethering of app infrastructure to transportation.

The bulk of the predictions made in the past shows are around the point at which technology becomes consumer ready.  This makes sense given that is what the shows cover every day all year long.  Many of the trends being forecast are at the cusp of end consumer adoption – the debate becomes, “is this the year?” or, “will this die before it fully matures?”

The crew correctly forecast all of the building blocks that let an Uber happen – the growth in the app store, the increased market share of the iPhone, even the fact that the iPhone itself would be the winning platform.  These trends were capitalized on by an Uber to pursue a market that is not a historical area of focus for DTNS.

To make use of these prediction shows to anticipate disruption, a few rules could be followed:

  • Assume that they are right about IT, consumer and near-consumer adoption.
  • Certain domains outside the normal coverage of the show are likely outside the area of prediction.
  • Assume that the predictions made about IT will combine with whatever predictions and technology roadmaps exist in areas outside of those predicted on the show.
Posted in Disruption, Industry, Invention, Theory | Tagged , , , , , , , , , | 1 Comment

Tech Forecasting: 6 years of DTNS / Tom Merritt Outlook (2 of 7)

“Whoever checks to see if these are right?” – Tom Merritt, 2014 / DTNS 2396

DTNS = Daily Tech News Show; a top podcast for listening to a recap of current tech news.

End of year tech podcasts are full of tech forecasts for the coming year.   Looking back at six years of podcasts involving DTNS host Tom Merritt, I listened to a little less than 4 hours of podcasts covering the years from 2010 – 2015.  I started the work following the ‘value-for-value’ ethos of the show; I like tech forecasting and wanted to help make it easy to do a year end wrap-up for 2015.  However, curiosity led me to listen to past shows.  My goal here was to; (1) think of frameworks that could be useful in tech forecasting, (2) see what trends emerge in these specific forecasts and (3) review how much technology has moved since the start of this decade.

d

Six years of tech forecast year-end podcasts.

Method

  1. Listen.  This was easy enough – all of the source shows were available on line.
  2. Listening to an Outlook (Forward) Show.  The first episode I listened to was DTNS 2397, which was recorded in 2014 and forecasting what would occur in 2015.  My notes for this are in a previous blog post.
  3. Listening to a Recap Show. Recap shows are made at the end of a year and discuss how well past forecasts did to anticipate the year’s major events.  For example, DTNS 2396 was broadcast in 2014 and was a recap of forecasts made during Tech News Today 911, which was broadcast originally on December 26, 2013.  DTNS 2396 (2014), TNT 910 (2013), TNT 658 (2012), TNT 401 (2011), and TNT 147 (2010) are all Recap shows. These shows were easier, as at that point the hosts had done some degree of quantification of their past forecast.  (A Google Sheets summary is here.)
  4. Document claims (aka forecasts).  I used the same methods that I’d done in DTNS 2396.  Claims were made in a big bucket list, and if sub-claims were verbalized, I would add them too.
  5. Document sub-claims.  On the tab ‘Claims 2010 – 2015’, I listed everything I could decipher going back to 2010 claims.  For example in 2010 Becky Worley made the very early observation that the megapixel race on cameras was dead – but that it was alive and real for your phone.  Those two claims are separate sub-claims in this document (row 257 and 258).
  6. Who?  Over the years there have been multiple participants – I attempted to document the original source of the claim wherever possible.
  7. Result.  I am by no means capable of quantifying the current state of technology. However, I did my best to state if a claim was true or not in the current year of 2015.

What can we learn?

There were several categories of lessons to take from this review:

  1. Claim Structure Matters.
  2. Accuracy of Claims.
  3. What is not covered?
  4. Disruptive Claims.
Posted in Uncategorized | Tagged , , , , , , , | 1 Comment

DTNS 2397: Tech Forecasting for 2015 (1 of 7)

In the value-for-value world of DTNS, Patreon and Tom Merrit – I might not be the best contributor.  Trying to think of ways to give back, I listened to the 2015 forecast show, DTNS 2397, that was published on December 31, 2014 and took the following notes to make it easier to produce this year’s 2015 Forecast Recap show.  Attached is my Google Sheets summary – hopefully it is useful and saves the team a bit of time in putting together the recap.

1-Fullscreen capture 12202015 15130 PM

My efforts to track the claims, sub-claims, initiators and supporters of the 2014 DTNS forecast show for 2015.

I love this show.  There’s something about the combination of the holidays, the annual nature, the free-flowing dialog, and everyone of the participant’s interactions that make it really interesting. I love podcasts; the medium is very effective and valuable.

My method was simple:

  1. I listened to the show.
  2. I entered what I heard into a Google Sheet. [I did not track when during the show this claim was made, but I left a column open for it in Column E.]
  3. I called a formally made forecast a ‘Claim’.  The primary claim is listed in Column F.  I counted 16 claims for the 2015 outlook.
  4. Once a claim was made, there was usually some secondary discussion – much of which was around trying to quantify or firm up how the claim could be judged to be true.  Column G track sub-claims and Column I attempts to track detail.  I counted 58 total claims.
  5. The person who made the forecast was listed with a ‘1’ in columns K-S.
  6. I tried to indicate who else that was on the show that supported the forecast in columns.  I used a 5 point scale (aka “I totally agree!” = 5/5. )  This got tricky with disagreement; should that be a 0 or a (-5)?  I went with a 0.  So, Patrick Beja’s disagreement that Spiderman would *not* re-enter the MCU was a 0.
  7. I attempted to grade the score from the 2014 forecast for 2015.  This was really an attempt to help out with the show – I am not an expert on these fields of technology so I had to go look things up.  (Yes, I do not use Snapchat.  Yes, I had to go confirm that it was still an independent company.)  The 2015 forecast outcome accuracy is listed in Column AD.
  8. Lastly – Esteemed producer Jenny Josephson judged the 2015 forecasts.  This was measured in two ways; (1) the contents of a DTNS coffee mug, and (2) what % full of the contents were said mug (Columns X & Y).

As an example; Patrick Beja initiates a forecast about the Apple Watch – I call that claim 2.  As the dialog continues, several sub-claims are made, resulting in Tom’s comment that predicts that there will be an article on TechCrunch saying that the watch is now in a drawer.  I call that Claim 2.05 (I used 0.01 increments on sub-claims – ala Dewey Decimal methods).  Since that article actually exists – I give it a 100% in column AD (but that column is really meant for the show participants to update).

Posted in Business, Disruption, Innovation, Invention, Methods, Theory | Tagged , , , , , , , , , , , , | 1 Comment

Methods: To Do List

1-IMG_6998

Activity tracking and note taking improve when they are separated into different activities and methods.

In June of 2015 I was overseas looking for 3″ x 5″ notecards – at the time they were the basis for my task tracking method.  No luck.  None were found.

Finding the store shelves empty of the preferred method – I grabbed a classic reporter’s notebook which was spiral bound at the top.  The methods I’d been using transferred easily to a single page in the notebook:

  • Keep only a single day’s to do list
    • This forces prioritization by limiting the number of items (18 in my current notebook)
  • Indent each item, then make;
    • Hashmarks to indicate progress towards completion
    • X = work is done
    • M = Moved to a future day
    • D = Duplicate item (unfortunately pretty common)
  • Use the back of the list to track a ‘Has Done’ list – this confirms what did get done that was off the list
  • Throw out the list at the end of the day
  • All day long there is a centralized list to:
    • Track must-do items
    • Add newly identified items
    • There is no need to dig through meeting notes to find deliverables
Posted in Methods | Tagged , , , , , , | Comments Off on Methods: To Do List

Methods: Notes in Meetings

1-IMG_6921

Simple 60 page notebooks help me stay organized, track meeting action items and keep our team on task.

In my first job I was handed a typical banker’s notebook and told that taking good notes was part of my job as an analyst.  Exhaustive notes were important.  Through promotions and a career switch to technology, those same notebooks and methods followed me. Simple banker’s notebooks were replaced with basic engineering graph notebooks or composition notebooks.

Briefly after graduate school I tried using Circa.  The notebooks were novel, the product was very nice, but it wasn’t as effective for me as a simple, standard notebook.

4-IMG_6996 2-IMG_6994
Note taking for me is more about active listening and using my notes to make sure that the meetings or events that I’m part of are as effective as possible.  It is less about the analyst assignment of taking exhaustive notes – more about making sure that meetings creative effective decisions and that the right actions follow.

In a typical year I’ll go through 5 – 7 sixty page dot grid notebooks.  Somewhere I picked up the habit of a standard set of initial appendices and conclusion pages.  These notebooks are not used for action items; that is a different method and for that I use disposable reporter’s notebooks and deliberately don’t keep the output.

3-IMG_6995Notebook goals are:

  1. Record events.  Use paper to listen actively while letting the meeting flow and encourage participation.
  2. Plan for meetings, calls and events.
  3. Plan the year, and a rolling 24 month outlook.
  4. Record and distribute action items, strategies and conclusions from meetings.
  5. Make sure the team has balanced participation in meetings.
Posted in Methods | Tagged , , , , , | 1 Comment

RTP Job Search 101: Raleigh, Durham, Chapel Hill, Cary, etc.

RTP is a great place to live and work – the region and economy are growing, work life balance is good and there are many top tier employers.  Through Elmarco‘s work with the NC State University College of Textiles, Nonwovens Institute, RTI, and our broad spread of academic ties in the Southeast, we get a lot of questions from people who are looking to relocate to the area.

Finding a job here is really no different than finding one anywhere else...Many of those inquiries start with, “What is the best way to do a search for positions in RTP?”  Here’s the advice we pulled together.  Most of this works for any kind of prospecting activity, regardless of location.

  1. Have a target.  A mentor of mine once said, “There are three things that matter – what you do with your life, where you do it, and who you are with.  Figuring out your own order is as important as the answers.”  If you are networking here, have some kind of target – either an industry, a company or part of the region (it is very big) that you can focus on.
  2. Be here.  A good local networker will find something faster than the greatest recently minted Harvard or Stanford MBA with a sterling work history.
  3. Connect with the connectors.  Startup Factory has regular events in central Durham.  There are many startup and entrepreneurial events from Raleigh all the way to Greensboro (technically the Piedmont Triad, not RTP).  Many of those are a waste of time.  However, at those events are the investors, accountants and lawyers who know what businesses are growing and in need of talent.  Find those people who are naturally screening many opportunities through their daily business.
  4. Be flexible.  The balance to #1 above is to recognize if you are achieving your target.  If you aren’t, or if no one can help you find a relevant business that fits your ideal, then it is time to re-prioritize.  During my previous work in private equity we would methodically explore a thesis and categorize everyone who is in the space – we would sometimes encounter people looking for something that did not exist, but didn’t realize that their search could not be fulfilled.
  5. Be patient.  Time is part of being successful in any kind of search – the more you have, the more likely you are to find the right match.  I’ve watched many people who have relocated to the area take something quickly, then shape their life, commute and family around a position that wasn’t optimal.
  6. Persist.  Similar to #5; if you quit after 6 weeks then you will simply be joining the long list of itinerant looky-loos who knock on a few doors but are just exploring the area.  There’s nothing wrong with that, but beginning this search without the right frame of mind won’t result in success.
Posted in Uncategorized | Comments Off on RTP Job Search 101: Raleigh, Durham, Chapel Hill, Cary, etc.

Vendor Selection: What Works

The Bay Bridge’s Newest Section

The California DOT’s selection of a partnership with Fluor and Shanghai Zhenhua Heavy Industry Co., Ltd. (“ZPMC”) to build the new section of the Bay Bridge hasn’t gone well.  It isn’t easy to chose the right partner for a unique project, there are some standard steps CDOT likely followed prior to picking the Fluor-ZPMC partnership.

Site Visits

I assume that CDOT personnel spent plenty of time in Shanghai with ZPMC and their partners, Fluor.  Getting to know a business at their site, reviewing their quality systems and developing relationships with their people are the best way to understand if they could really deliver what was needed for the bridge.

Partnership Audit

How long have Fluor and CDOT worked together?  Who are the key personnel?  How well do they know each other?  Do they have personal relationships outside of the office?  These are tough things to understand and this would usually be considered outside of the boundary of a standard investigation of a vendor, but with a project like this and a partnership with the dynamics of Fluor and ZPMC, it would be essential to understand what the dynamics really are when buying from this group.

Most Favored Nations Clause

A most-favored nations clause usually states that, “what we agree to here will be the best type of terms we agree to with any customer; and if not, we will offer any better terms that are offered.”  For most customers, this is a concern about price – they don’t want to pay top dollar for a system that they find out was sold to someone else for less.  However, this can be extended to items like service response times, quality yields, etc.  Even if it isn’t agreed to, by asking for it CDOT would trigger serious conversations from their vendor – the kinds of terms that Fluor and ZPMC granted to Greater Gabbard on their wind farm would have gone a long way to making CDOT whole for the pain of the faulty welding.

Capability Review

weldsZPMC wasn’t capable of performing the welding needed by CDOT in the volume that was required by the project.  A basic capability review of the vendor would likely have uncovered this.  Further, the welds were to have been tracked in quality systems that weren’t up to par.  A systematic review of the methods needed would have uncovered the weaknesses experienced by both the wind farm and bridge construction projects.  Asking someone, “can you do this welding with the right quality?” will get the answer that passes the question.  Spending several weeks on site and reviewing their current welding and quality recording projects would get a real understanding of what they are currently doing.

A Second Project

Neither the wind farm group nor CDOT will likely work with ZPMC ever again – and in this situation they lose a lot of their leverage.  The potential for a second project would bring ZPMC and Fluor back to the table to address the problems that they’ve had so far.  In fact, it may be the possibility of future wind farm projects that keeps the North Shore engagement on fairer economic terms (these projects may be fundamentally a better fit for ZPMC’s capabilities).  Fluor likely has more incentive since they are most likely to be looking at additional, similar projects.

Conclusion

There are many ways to understand if a vendor’s capabilities will really deliver what you need.  The true costs of bad vendor selection for these kinds of custom projects are far beyond the costs of more diligence on the part of the buyer.  CDOT will spend money for decades repairing this work when it would have been much cheaper to choose the vendor more carefully in the first place.

Posted in Industry, Marketing, Theory | Tagged , , , , , , | Comments Off on Vendor Selection: What Works

Vendor Selection: The Bay Bridge

Choosing the right vendor is never easy.  The California Department of Transportation’s recent woes with the $2 Bn updated suspension span segment that was overseen by the US construction firm Fluor and physically built by Shanghai Zhenhua Heavy Industry Co., Ltd. (“ZPMC”) illustrate some of the challenges in choosing your partner in long term projects.

It is not easy to figure out who to work with in these situations:

  • How do I know who can do this project if it has never been done before?
  • How do we contract with each other in the case we encounter unforeseen problems?
  • How does a customer run the vendor evaluation process to get the right outcome?

There aren’t any perfect answers.  In a perfect world, CDOT would circulate an RFP and there would be 50 companies who had built identical bridges with long track records that are easily audited.  The competition under this scenario would be dictated by price.  Unfortunately, classical economics don’t work here.  CDOT has a unique site with unique time and other needs.

To choose the right vendor they needed time to develop trust in the vendor.  With enough time and exposure, they would understand what the vendor can and cannot do.

Time would allow ZPMC to fully understand what CDOT’s needs really are and whether or not a relationship with Fluor could help them achieve their goals.  From ZPMC’s standpoint, signing up for a project where they can’t deliver doesn’t help their interests – it only creates an installation that can’t be supported.

Unfortunately, it doesn’t sound like there was enough time for all of the parties to truly understand what they were getting.  ZPMC hasn’t met the quality and reporting needs of the bridge.  Welding methods that were needed weren’t followed correctly.  CDOT may have gotten a deal on the bridge, but the service and maintenance costs will be far beyond their initial estimates.

Posted in Uncategorized | Comments Off on Vendor Selection: The Bay Bridge

Building the Right Team

In our management meetings the other week, we talked about what we want our teams to look like.  Running our commercial organization, my ideal team needs to reflect the needs of the market and be able to help our customers win using our technology.

The heavy industrial technology we sell:

  • Is complex
  • Takes time for customers to understand
  • Has global demand
  • Is very valuable once proven
  • Enables our customers next generation products (often their highest margin SKUs)

That means that individually, my team members need:

  • Good judgment to tell if an opportunity is real (and to get rid of ones that aren’t)
  • Persistence to pursue big opportunities that may take time to develop
  • Excellent inter-cultural and interpersonal skills to deal with the diversity of our own team and those at our customers
  • Discipline and poise to deal with situations that can be high stress with significant capital on the line
  • The right amount of attention to detail to map our capabilities to our customers needs and also master the intricacies of our legal and commercial agreements

As a team, I need them to be able to:

  • Address three core industrial applications
  • Be able to field unconventional / opportunistic inquiries beyond those three focused fields
  • Be able to cover the following languages fluently: English, Czech, German, Russian and Mandarin (and get by in several others including Spanish, Portugeuse and Italian)

Lastly, since we’re in materials science, we face a long adoption curve.  We must be both aggressive and patient, covering all of these areas with minimal costs and maximum impact.  Building the right team in such an environment makes our own business and that of our customers successful.

Posted in Industry, Theory | Tagged , , , , , , | Comments Off on Building the Right Team

Organizations Want to Live

Any organization, once it is created, takes on a life of its own.  It wants to live.  Just as Kevin Kelly describes ‘technology’ as a seventh kingdom of life, in many ways the individual organizations encountered every day also behave like an organism or population.

It can be tough to kill an organization, even when it is clear it won’t last.

We’ve had competitors where (i) the economics don’t make sense, (ii) there aren’t enough customers for their product, and (iii) even management recognizes that their outlook is dramatically different than what was originally believed.  But the environment around them – investors, employees and potential customers, manages to keep the entity around and kicking.

Twice I’ve helped in the creation, and eventual dismantling, of nonprofits.  Both were worthy causes which had early successes – only to find that the giving environment for what they did was less robust than hoped.  Too small to support full time staff, it made sense to shut them down rather than let them die.  One has been closed for several years – and still there are glimmers from time to time that maybe it could survive – it wants to live.

Once created, an organization wants to exist.  The individuals who created it, who maintain it and who are impacted by it, prefer inertia to the unknown -and in doing so they keep it alive, even if that is not the best option.

Posted in Theory, Uncategorized | Tagged , , , , , , | Comments Off on Organizations Want to Live