Skip to main content

A comment on "5 Trends In Government Technology We'll See In 2017"

(Here's the original post:

This is an important post but I am not sure I agree with its premise or all of its points.

For one thing, per #3, it appears the assumption is that Hillary Clinton will win. Why does the post assume this? To strategize means to play out both scenarios. Trump vs. Clinton will bring us two dramatically different approaches to government technology. Under Trump, expect his team to take out their calculators and basically slash and burn everything that isn't immediately and obviously justifiable from a *business* (not a government) point of view. Under Clinton, expect an incremental approach to change and a willingness to continue spending even on technology initiatives whose worth is not yet immediately clear.

Regarding #5, I think the private sector is well ahead of the public sector in understanding what outcome-based engagement is. This relates to point #1, data. My sense (although I cannot prove it) is that state and local governments are ahead of the federal government in terms of using data to drive decision-making about outreach. In contrast, I am hard-pressed to think of examples in the federal government where outreach strategies were developed based on integrated, mission-critical desired outcomes, assessed for performance based on data, and modified according to the results of that data. Even when they want to obtain this data -- and they do, because data is a way to justify leadership decisionmaking -- there is red tape surrounding surveying the public for feedback. Whoever wins the election, I really hope that the feedback process opens up and becomes easy so that we can immediately pulse people as to whether our initiatives make sense and are working.

As far as cybersecurity and FEDRAMP (#4), it seems to me a no-brainer that the government should continue to establish and market secure cloud spaces within which federal agencies can do their business without a lot of hassle. It should be extremely easy for agencies to determine what type of service they need; look up what type of platform will support the service (e.g. a cloud-based environment with the right level of security); and order it through an interagency agreement, with a customer service representative walking them through the entire process and available to answer questions and troubleshoot. This is not so much a matter of growth in utilization of FEDRAMP but an internal customer service issue from government to government. Again, regardless of who wins the election it will be up to the feds themselves to create clarity among the service offerings available and educate the incoming political appointees about what is on offer. This requires not only an understanding of technology, but also an understanding of contracting, government funding mechanisms, mission and infrastructure within and across agencies, and the mechanics of establishing points of contact within agencies effectively. Too often, there is a lot of good stuff going on but the right hand does not know what the left hand is doing.

One last point I think Steve could have included here is the growth of internal collaboration, workflow management and social networking within agencies, which I would expect to explode by 2018 if not 2017. As the government becomes more familiar with the way millennials work (millennials being the future of government even if they hate how it works right now), there will be a recognition that constant contact and collaboration, including honest discussion, is simply required for productivity and it is not going to go away. Steve's 2009 brainchild, GovLoop, was revolutionary in that it created a space for government employees to have those conversations with one another, albeit in a public space.

As the government grows more and more savvy about this, such conversations will be encouraged and they will be linked with document collaboration, review and approval in a way that's very easy to manage, very secure, and very easy to track in terms of who approved (or altered, or commented on), which text. At the same time, the government will need to establish a set of standard operating procedures in conformance with the law that enable free flowing conversation while also ensuring preservation of documents and discussions for later examination by the public (e.g. FOIA).

If vendors could come up with a way to increase productivity and reduce duplication of effort through a combination of internal social networking, document management, and potentially even the integration of external customer service (such that I can answer your inquiry on Twitter in a manner trackable to an internal discussion, with a ticket number, referencing a public law or guidance document), I think it would literally transform the way government does business forever.

Of course all opinions are always my own. Thank you for the opportunity to comment.

Popular posts from this blog

What is the difference between "brand positioning," "brand mantra," and "brand tagline?"

Brand positioning statement: This is a 1–2 sentence description of what makes the brand different from its competitors (or different in its space), and compelling. Typically the positioning combines elements of the conceptual (e.g., “innovative design,” something that would be in your imagination) with the literal and physical (e.g., “the outside of the car is made of the thinnest, strongest metal on earth”). The audience for this statement is internal. It’s intended to get everybody on the same page before going out with any communication products.Brand mantra: This is a very short phrase that is used predominantly by people inside the organization, but also by those outside it, in order to understand the “essence” or the “soul” of the brand and to sell it to employees. An example would be Google’s “Don’t be evil.” You wouldn’t really see it in an ad, but you might see it mentioned or discussed in an article about the company intended to represent it to investors, influencers, etc.Br…

Nitro Cold Brew and the Oncoming Crash of Starbucks

A long time ago (January 7, 2008), the Wall Street Journal ran an article about McDonald's competing against Starbucks.
At the time the issue was that the former planned to pit its own deluxe coffees head to head with the latter.
At the time I wrote that while Starbucks could be confident in its brand-loyal consumers, the company, my personal favorite brand of all time,  "...needs to see this as a major warning signal. As I have said before, it is time to reinvent the brand — now.  "Starbucks should consider killing its own brand and resurrecting it as something even better — the ultimate, uncopyable 'third space' that is suited for the way we live now.  "There is no growth left for Starbucks as it stands anymore — it has saturated the market. It is time to do something daring, different, and better — astounding and delighting the millions (billions?) of dedicated Starbucks fans out there who are rooting for the brand to survive and succeed." Today as …

Should I Add My Beer-Focused Instagram Account To My LinkedIn profile?

This is my response to a question originally posed on Quora.

The answer, like lawyers tend to say, is: “It depends.”

Not knowing what you do for a living, let’s assume that your LinkedIn profile is typical, meaning that it reflects the image of a corporate professional.

Would your boss, or a prospective employer, think badly of you for promoting your passion for beer?

Traditional product branding says that you should focus on your unique selling proposition fairly single-mindedly. Your goal is to create a space in the customer’s mind dedicated to your brand so that when they want to purchase something like it, they shortcut all alternatives and go straight to you.

So from a product branding point of view, putting a personal beer account on your professional profile is distracting. It tells an employer that you’re not totally focused on the encyclopedic and ever-evolving knowledge, skills and abilities required to do your valuable type of job.

However, people are not products, and appl…