After a jam packed AWS re:Invent 2018, I've been thinking about how to deliver information to an audience. One of the challenges is delivering that information with enough context that it makes sense to that audience.
When you are trying to get a message out to a lot of people, it's not realistic to try and get them all back to you digital properties. So what do you do? How do you manage trying to hold the same conversations in multiple places? How do you monitor what's working?
The "secret" to most success is being prepared. Taking a few minutes or hours to map out what you want to happen is far better than trying to figure it out when you're up against the clock.
Before any big shifts there are always small signals that hint at what's coming. We're seeing more and more companies start to make a play for data. Whether it's as a broker, niche analysis, or in data aggregation. There is risk here if this rapidly growing area is left unchecked.
We build services and solutions using parts provided by other companies. That's the only way to move forward effectively. When a security or privacy breach happens, how do you handle those parts out of your direct control? Especially considering your customer may not have any idea they exist?
You know you have to master your tools but are you selecting or building the right tools? A lot of teams over or under engineer their tools. This results in either a failure to return the value invested or lost productivity. Are you hitting the sweet spot?
Cyberattack attribution is HARD. But time and time again, we're seeing attributions—who carried out the attack—made publicly with little to no evidence presented. Worse, these attributions are having real world impacts...
Knowing what the tools in your kit are capable of is critical to success. But can you actually use those features? Do you really understand the implications of the more advanced features of those tools? Sometimes simple is better...and in any case, you better master those tools!
Your product/solution/service has a goal and you've probably gotten good at articulating that goal...but is that message resonating with the audience you're in front of right now? Are you adequately customizing the message for each audience?
"Don't do work you don't have to." It's a solid rule and one that you can leverage more often than you think. There are opportunities to automate our work all around us, but do you have the skills to take advantage?
Working deeply on any one problem for too long narrows your perspective. That's just human nature. Are you taking steps to refresh that perspective? To empathize with teams around you?
Nothing is built in isolation. Each technology builds on layers and layers of technology before it. But are those layers worth building on? Can they support the weight of new ideas? How do you account for issues in layers you don' t control? We're seeing the negative consequences more a