When I introduce myself as a Technical Program Manager or Project Manager, often the first thing that happens is I get tagged as only valuable in a "software" or "technology" context.  While it is true that I do work primarily with software development companies, being a PM is so much more.  For me, the "P" in PM stands for problem. I am a Problem Manager. I manage the sticky wickets for my clients and smooth out the rough edges so they can be successful.  In a traditional technology setting this is often manifests as code vetting, prototyping, developing requirements, managing communication, and typical delivery activities.  In a non-technology setting activities trend towards smoothing friction points in common workflows, organization, creating a system to manage the flow of information.  The great thing about being a consultant is I get to apply my problem solving skills to a variety of contexts both technical and non-technical.  Next time you meet a PM, do not automatically discount their benefit to you just because you are not in a traditional software development industry. This Problem Manager just may deliver the creative solution you are looking for. 

Today's consumers want hyper contextual experiences. They want interactions to follow them as they move through the world, adjust to new conditions, and transfer seamlessly across devices.  In order to execute these experiences, we need to know a lot about a consumer. 

Take this experience for example:

Martha has a meeting on her calendar today.  Her calendar application pops up a notification on her computer at the beginning of the day reminding her of the meeting.  Her calendar has a plugin that recognizes her location, monitors traffic, and notifies her when it is time to leave.  She gets into her vehicle and an app in the head unit launches with turn-by-turn directions to her meeting location.  Based on her buying habits, another app on the head unit recognizes Martha usually needs a caffeine boost this time of day and asks her if she would like to drive through a coffee shop on her route.  She declines and continues on her way.  As she gets close to her meeting location, an app in her head unit provides a list of parking options.  Martha selects one and is navigated to the correct lot.  When she puts her vehicle in park, the head unit app recognizes her stall number, prompts Martha to select a time increment, and then completes the transaction.  She exits her vehicle and begins receiving audio directions on her smartwatch navigating the last few blocks to her meeting.  

Sounds really cool.  To me, it also sounds a bit creepy.  Martha's plans, patterns, location, personal information, payment information, and device details are shared across multiple systems.  Even simple experiences - my refrigerator sends me a notification on my smartwatch to buy milk as I'm walking past my usual grocery store - can trigger that cool/creepy conflicting response in my brain.

GDPR (General Data Protection Requirements), CCPA (California Consumer Protection Act), and other regulations prescribe bottom line protections and provide consumers a way to opt-out and delete their data after the fact. In most cases however, opting out results in the loss of the experience.  Are there ways to use AI and predictive analytics to provide the consumer with a partial experience that still makes sense while limiting their exposure?  How do we balance the desire for new and seamless experiences with privacy?  Can we create engaging and compelling experiences at the cohort level rather than the individual level?  How do we need to adapt as consumers redefine what they consider "private"?

This will be an interesting space to watch with a lot of opportunity to get creative around designing contextual experiences. 

I absolutely loved my Motorola Razr and was heartbroken when the hinges finally gave out and I had to upgrade my phone.  I was more than a little excited when Motorola announced a reboot of the Razr and now Samsung is getting in the game with their Galaxy Z Flip.  The technology is still early and both phones are beyond my price range, but the return to retro is worth a watch.  

Not only do these phones trigger nostalgia, but the enable some interesting opportunities for app design.  Both models support split and full screen modes as well as an external screen when the phone is closed.  This enables state driven design and multi-app interaction beyond the obvious screen/keyboard split borrowed from tablets. 

Maps:

• Full screen - standard map view with navigation queues
• Split screen - map on top and directions on the bottom
• Closed - turn-by-turn navigation queues

Viewing Content with Split Screen:

• Anchor media to the top and allow scrolling through copy on the bottom
• Anchor the original article on top and open content links or share on the bottom

Entertainment:

• Who else thinks this is the perfect Battleship setup? Full screen transitions to an animation of sinking your opponent's Battleship.

I can't wait to see the creative ways designers and engineers capitalize on this opportunity.  I would love to work with others in this space to create a truly engaging experience.

I made a goal this year to write one article a week and admit I am struggling.  It has been difficult to find compelling topics that are interesting, relevant, and not just the standard industry regurgitation.  I've also flip-flopped on acceptable categories; should I keep it strictly industry, are personal interests fair game, what about random current events? 

For those who regularly publish content:

• Where do you find inspiration?
• How do you decide if a topic is appropriate?
• How do you keep yourself motivated to write?

Let me know how you approach connecting with the community through your writing.