The main point is that it’s worth trying to predict technology triggers and asking what those triggers mean. There is value in answering the question so what? A secondary argument is that questions beginning with what if? can be very interesting, but far less reliable than so what? What is a Technology Trigger? The term Technology Trigger is from Gartner’s Hype Cycle. They defined it as: A potential technology breakthrough kicks things off. Early proof-of-concept stories and media interest trigger significant publicity. Often no usable products exist and commercial viability is unproven. Gartner Research The term has been deprecated in favour of the term innovation trigger. However, as an owner of the hardcover book Managing The Hype Cycle (2008), I[…]

There are at least two systems of achieving productivity growth: path dependence and disruption. What if there is a third way? This post unpacks that paragraph and explores ways through. It will start with explaining lock in and path dependence. We’ll cover the application narrow machine intelligence in a very narrow industry. It will end with a small scenario and a few what ifs. Lock In Consider banner advertising. This is a relatively old industry. Its roots predate the Internet by at least a couple hundred years. It may have started thousands of years ago. It starts out with a person with a problem. They need to get the word out about their product or service. Reframed, they need to[…]

What if code is an artifact of the culture that creates it? What would your interpretation of the code suggest to you about the culture? What would different layers of code tell you about how people lived in the past? Culture Code is instructions to be run by machines and interpreted by the humans that take care of it. So much code is managed by people. And groups of people get to together and create language, standards, rituals, traditions, meanings, arguments, rhetoric, procedures, regulations, obligations, agreements, memoranda of understanding, specifications, memes, stories, and values. Cultures evolve. For instance, as a startup goes from 2 people to 5, then 5 to 11, (11 to 23, 23 to 47, and so on)[…]

The inspiration for this post is John Cutler‘s excellent twitter thread on prioritization. It’s well worth the read. This post builds on that inspiration using Roger Martin’s concept of the The Knowledge Funnel. One big takeaway of John Cutler’s thread is when deciding the sequence of what to do in product management, consider the big picture and think of the impact of what you will do next on what you will know next. What I like about Roger Martin’s concept on knowledge funnels: consider the big picture and think of what you know about value. Product management and data science is all about managing the knowledge funnel. Your ability to manage this funnel is predictive your ability, and those you[…]

There are many calls to break up tech. Break up what, exactly? Regulate tech? Regulate what? There’s a lot of polarization about what to do about Facebook, Amazon, Apple, and Google. That polarization is in part driven by anger. Dig a bit deeper and see fear. Maybe you’re feeling it. Here’s how I see it. The Assumptions People are heterogenous. Peoples’ beliefs are heterogenous. Peoples’ willingness to believe are heterogenous. Peoples’ inventiveness and imagination are heterogenous. Peoples’ willingness to tell or repeat stories are heterogenous. Peoples’ susceptibility to stories, and to storytellers, are heterogenous. Peoples’ need to belong are heterogenous. People form networks because they need to belong. Information (Gossip, facts, stories) is transmitted along those networks. These variables (information,[…]

Suppose the following scenario: Series A or B; A data science firm (narrow machine intelligence, applied machine intelligence, general machine intelligence, predictive or prescriptive analytics, software or hardware); Technical CEO / Co-Founder; Chief Marketing Officer (CMO) just hired; What might the CEO-CMO relationship look like? The relationship could be great. If there’s one stereotype about data science CEO’s, it’s that they like incentives to be aligned. The CMO would likely be brought on to focus on growth. If revenue grows, valuation grows, and collective comp would grow. There might be points of friction. From the CMO’s Perspective: Why is the CEO constantly at me about metrics all the time? Why is the CEO always on about non-working dollars? (Why don’t[…]

What do you think causes the demand curve? Mechanically, it’s pretty easy to describe the laws of demand. The way pretty lines shift to the right or the left from shocks. It’s possible to deduce the real, rough, shape of the demand curve for a product (It just takes a lot of courage!). We can import all the knowledge about demand, segmentation and price discrimination. We can describe a demand curve just fine. Why does it exist? What causes it to exist? If intelligence didn’t exist, demand wouldn’t exist. It’s fun to think of a machine generating it’s own preferences, independent any human input. Most of human trainers of such machines seem to keep them on a short leash. Monkeys,[…]

It seems like a lot of people value certainty. People buy a lot of products and stories for certainty. Insurance. Investment advice. Forecasts. Indulgences.Many entrepreneurs, in particular those in data science, sell certainty. What else is an F1 score other than a measure of certainty on some level? Given some inputs, our machine transforms them some way, which produces some statement about the past, present, or future, with some quantifiable amount of certainty, so that you can do something with confidence (or feel more secure). We sell certainty. And yet isn’t it curious about how much insecurity we’re creating while we do so? It has always been easier to sample data from the past, pull a heuristic from it, and[…]

Teams, in software engineering, form because of success. Without success, the firm wouldn’t be cursed with the problem of having so much talent to have to organize in some way. A founder can easily reduce the complexity in their human organization, and their lives, by simply not hiring any more than seven technologists to work with them on their mission. For some, this is viable. For others, this is not. Teams emerge in response to scale. They are either formed as by product of centralized hierarchical command structure, or they emerge as a product of network cohesion/polarization. To the extent that either formation is aligned with the vision, goal, mission, or purpose of the organizational chrome is a function of[…]

Imagine with me: what if novels were written like software. Sometimes it’s useful to approach absurdity and look inside. There might be treasure there. I’ll define software as an executable, a set of instructions, that are interpreted by a machine for some reason. As a data scientist, I think of software as a product, and I think, constantly, of turning data into product. I think of data as inertia and all the code around it as flexible. I worry a lot about the people that use the software (if anybody) and think of them as heterogenous segments. I think of a novel as an executable, a set of instructions, that are interpreted by a human brain for some reason. As[…]