IoT Field Notes: Who are you Disrupting?
When introducing IoT ideas to your markets, you may be disrupting more than you think! Some specific examples and caveats ...
Getting people, process, and technology to change can be a challenge. These posts talk about concrete tactics for results, with some “war stories” sprinkled in.
When introducing IoT ideas to your markets, you may be disrupting more than you think! Some specific examples and caveats ...
What is the minimum amount of functionality required to engage with your target audience, and get folks to understand the vision? MVP-thinking focuses your effort on the minimum amount of work required - check out this video for more!
Introducing new ways of thinking about Digital Products; true stories "from the field" of building Proof of Concept systems to get the Voice of the Customer.
Tech folks in your organization may be overcomplicating and/or underestimating some of the aspects of "the Cloud". This enabling technology has some fairly important new features and capabilities that you need to understand more fully.
Product teams that are exploring the possibility of smart, connected products fall into one of five different groups; this article will help you understand how to take the next step with each.
Why aren't we moving faster? This story of a quick, simple back-of-envelope calculation that showed the large potential of a new product idea really got the team to think.
This article describes a powerful risk reduction tactic for large, complex projects - illustrated with a practical example of success.
Focus on a better definition of Success - one that delivers results. Quantifiable change, improved operations, smarter people, profitable top line growth - there is a big difference between deliverables and meaningful results.
It really doesn’t matter which functional area leads your Digital Transformation – as long as they realize that the role needs to understand this critical list of skills and experiences.
How much rigor does any decision really need? One clue might be to look at the number of significant digits you will be presenting. Say you are asked to present the cost impact of IT systems on a major acquisition or merger. Based on the context of the conversation - the macro-financials, the pay-back models, and the YOY growth plan for the next five years, you will probably be delivering a single slide that shows $20M in cost and/or benefits…