Tag Archives: amazon

How the City of Seattle can improve its relationship with Amazon (and Microsoft, too)


Amazon office buildings and cranes dot the Seattle skyline. (GeekWire Photo / Nat Levy)

Amazon is looking for a second headquarters city, “co-equal” to Seattle. Seattle’s city Leaders suddenly have an immense interest in their relationship with the city’s largest employer, a company which has ignited the largest economic boom here since the Klondike Gold Rush. A meeting of the behemoths (city and Amazon) is apparently set for Feb. 9.

Meeting with Amazon is a good step. But city government leaders should not ignore other companies which contribute to making Seattle a wealthy, world-class city, especially Microsoft.

How do Seattle’s elected officials improve relationships with these companies while, at the same time, improve services and quality of life for Seattle’s residents? Elected officials should not “give away the city” as the State of Washington did in 2013, giving Boeing an $8.7 billion dollar tax break; Boeing then actually reduced employment in the state.

Here are some ideas: (read the rest of the article on GeekWire here).

Leave a comment

Filed under Alexa, amazon, Microsoft

If it is always “Day 1” at Amazon, it is Day 10 in Government

jeff_bezos_headshot11“I’ve been reminding people that it’s Day 1 for a couple of decades. I work in an Amazon building named Day 1, and when I moved buildings, I took the name with me.  [So] what does Day 2 look like?”

“Day 2 is stasis. Followed by irrelevance. Followed by excruciating, painful decline. Followed by death. And that is why it is always Day 1 [at Amazon].”

So says Jeff Bezos, Founder of Amazon, soon to be a trillion dollar company, in his annual letter to Amazon’s stakeholders.

What are the lessons Government can learn from Bezos and Amazon?  But also, how is Government different from Amazon and other entrepreneurial private businesses?

Government is NOT at Day 2

The City of Seattle is at Day 53,830 (incorporated December 2, 1869) and the United States is at Day 87,948.   Governments have been around for dozens, hundreds of years.  They rarely go into “excruciating, painful, decline” and very very rarely die.   Are governments irrelevant?  Try getting a driver’s license or not paying your taxes.

But this longevity also leads to complacency, poor or indifferent customer service, and skepticism or outright hate by some citizens.   And governments are in competition – for industry, business, skilled and educated citizens, revenue and tax dollars.   Poorly operated governments drive away business and smart citizens, and they decline, even if they don’t die.

process-as-king-cartoonProcess as Servant, not King

Every private company and every government has bureaucracy, process, and procedures to do its business.  But in private enterprise or government, process is should not be the goal:  satisfied customers are the goal.

Jeff Bezos wants a customer-obsessed culture where Amazon employees “experiment patiently, accept failures, plant seeds, protect saplings, and double down when you see customer delight”.

Almost always governments – and most large corporations – focus on the process of customer service, not the customer.  We make following procedures and abiding by policy take center stage, no matter what happens to our customers. The ugly episode where United Airlines recently had police drag a customer off a plane is a one example.  But government – and the Veteran’s Administration is a another example – makes process King.

This isn’t because individual employees aren’t committed to the mission – the VA is filled with thousands of dedicated employees (second only to the postal service in total numbers), working hard to take care of veterans.  But it also has bureaucrats for whom process is King, and too often they are in charge.

This lesson of keeping the focus on customers comes in tiny increments. I recently stayed at a Hilton Hotel which had a happy hour with free beer.  I arrived 15 minutes after the end of happy hour.  The bartender asked “were you here for happy hour”?  I honestly replied “no”.  She gave me a complimentary beer anyway.  In doing so, she made me a delighted customer.

In a more substantial example, I needed assistance on a social security and Medicare application.  I went to a local social security office and had to “take a number and wait in line” for more than 30 minutes.  But when I saw a counselor, she did not hurry me, asked me good questions, and gave me wise advice on choices with advantages and disadvantages of each.  Then she executed on my choice – she made it happen.  I walked away delighted by customer service, despite the wait.

We need to empower government employees to do the right thing, just like Amazon, Nordstrom and similar businesses do.

Embrace external trends

Technology for customer service innovates quickly.  Traditionally government has moved slowly and has been risk adverse.  This must change.

Computers have automated tasks which could be described with clear rules, if-then statements, and algorithms.  Think of an algorithm as a recipe where the inputs and outputs (ingredients) are described along with the steps (procedure) necessary to make the entree.

Private companies now embrace machine learning and artificial intelligence (AI) to power chatbots, text messaging, frequently-asked-questions and help desks.    IBM is harnessing its artificial intelligence engine Watson to revolutionize law firms, healthcare and help desks.   The City of New York is trying to use Watson to fix its aging 311 system.

Bezos points out several projects in which Amazon uses AI, including Amazon’s Prime Air delivery drones, its new futuristic grocery stores, and its virtual home assistant, Alexa.

Siri-cartoonVirtual digital assistants are proliferating in homes and businesses.  Burger King intentionally created  “TV commercials that cause Google’s voice-activated, artificial intelligence-driven Google Home speaker to start talking about the Whopper sandwich” (USA Today).  Amazon’s Alexa, invoked by its Echo devices in millions of homes, now will start appearing in many other devices including automobiles.

But few governments embrace these leading-edge technologies, preferring to force our customers to “telephone between 8:00 AM and 5:00 PM” including the “our menu options have changed” phone tree, or to physically, actually show up at a government office to do business.

Public safety officers – law enforcement and firefighters – heavily use two-way radio, but are forced to sit at a keyboard to type reports or make routine queries like checking license plate numbers or verifying identities.  These are all tasks which could be automated with natural language processing and speech-to-text capabilities available in Alexa and similar products.

Governments need to adopt these high-value customer service technologies rapidly.

High-Velocity Decision Making

Most governments and large companies make high-quality decisions, but they make high-quality decisions slowly.  In the case of governments, the decisions can be excruciatingly slow.  For some reason government employees love to play “gotcha”, trying to find every risk and every potential problem with a new idea, even if the chances of the issue materializing are one in a million.

When I was the Chief Technology Officer at the City of Seattle, I would gladly take one enthusiastic, “can do”, positive, product manager looking at the “new idea” glass as half full instead of a dozen devil’s advocate employees who always want to see the glass half empty, or an engineer who would say “the glass doesn’t meet our specifications”.

Speed matters.   Many decisions are trivial and inconsequential.  They can be easily reversed.  Make them fast.   But the very worst outcome is to banish a decision to a committee or kick it upstairs for a more senior manager to make.

Governments are Not Businesses

However there are differences between governments and private businesses.

Governments cannot choose their customers – we need to accept all comers.  This includes those with special needs, low income, the senile, the mentally disturbed, the homeless and the technologically challenged.   This often means we will have a “real person” help desk as well as a chatbot.

Governments are in the eye of public scrutiny.  Amazon can hide most of its bad decisions (the very public failure of the Fire Phone is an obvious exception).  Government cannot.  Mistakes such as a $43 million budget overrun for the City of Seattle’s utility billing system make headlines and are featured on the 11:00 PM news.

Does this mean government should avoid big projects?   Not at all:  Governments must embrace modern cloud-based technologies, professional project management and agile development of software systems, delivering incremental value every 6 to 8 weeks.

ChieGovernments don’t fail, private businesses do.   The United State Government has been around since 1776.  The City of Seattle has been operating since 1869.  Governments don’t face the same competitive pressure as private businesses.   Nevertheless, governments do compete for economic development, industry and citizens to locate within their boundaries.   Successful governments boom, unsuccessful ones languish.

Governments are operated by elected officials, not CEOs.    Mayors, City Council members, County Executives, Governors, legislatures and other elected officials run our various governments.   But almost all governments have three branches – executive, legislative and judicial.  These branches check and balance each other, slowing decision making.    Elected officials also … well … need to run for re-election.   That increases their aversion to taking risks.   Amazon and many private businesses, run by a CEO and a relatively uninvolved Board of Directors, can be nimbler.

It is always Day 1 at Amazon.  If Day 2 is stasis and irrelevance, government should try to be at day 1.5.


Filed under Alexa, artificial intelligence, customer service, future of technology