This job announcement from Twitter just went live. The salient bits are here:

Twitter is looking for an experienced, entreprenurial person to make Twitter better for policymakers, political organizations and government officials and agencies. You’ll be our first D.C. -based employee and the closest point of contact with a variety of important people and organizations looking to get the most out of Twitter on both strategic and highly tactical levels. You’ll help Twitter understand what we can do to better serve candidates and policymakers across party and geographical lines. You’ll support policymakers use of Twitter to help them communicate and interact with their constituents and the world. You’ll work with nearly every group at the company and at every level to pursue your vision for how Twitter ought to be. You’ll help set the culture and approach of a fledgling public policy department and be an important part of our very small company.

Image courtesy of zoominfo

I could totally do this. It’s actually the one thing that sounds insanely fun about working in DC: showing government folks how they can use Twitter for AWESOME purposes. Connecting legislators to their constituents (and each other). Connecting soldiers with families. Connecting. CONNECTING.

Even though I’m already gainfully employed and stretched thinner than Plastic Man in a God-sized tug-o-war… I am really giving some serious thought to applying for this gig.

What do y’all think??? Should I go for it?

Enhanced by Zemanta

As regular readers of this blog know by now, I had quite a journey getting to present at the Gov 2.0 Expo this year. I’ve spent enough time talking about that preso. Now it’s time to talk about the Expo itself.

There have been metric shitloads of wrap-ups, reviews, commentaries, and think pieces following the Expo. I’ll try to sum up my experience there without repeating too much. (See links below to some of the better wrap-ups.)

First and foremost, I have to give Laurel Ruma, J.B. Wheatley and the rest of the O’Reilly staff huge props for hooking it up for me. Laurel greeted me with a great big hug when I arrived, and her enthusiasm never wavered. The speakers’ lounge gang was a delight as well, providing a great place to meet new connections like David Hale from the National Institute of Health and longtime Twitter pals like Chris Rasmussen.

I expected a lot of cogitation, pontification, and general assholery from this conference… par for the course of most govvie conferences in DC. However, I was pleasantly surprised that the gov in Gov 2.0 was better represented by hyperlocal government (cities, counties, townships) than the federal monstrosity here in DC. While we eventually got to see presos from Price Floyd (Defense Department) and Alec Ross (State Department), their remarks were not near as inspiring as the things coming from local yokels like Joshua Robin (Massachusetts Department of Transportation), Steve Corbett (iStrategy Labs), and Melissa Jordan (Bay Area Rapid Transit). It was really AWESOME and inspiring seeing these representatives and enthusiasts of city and township government speak about crowdsourced apps, programs and ideas that are revolutionizing the way their local governments are engaging with and supporting citizens.

These combined perspectives on citizen engagement of local government really speak to me given my work with Sister Cities International. If it’s one thing my mom taught me (she’s the president of Fort Worth Sister Cities) it’s that the relationships that matter most to government change are those between citizens. And it’s important to remember, government employees are citizens too. People at the Gov 2.0 Expo showed me how true and effective that can be, especially when you activate those citizens’ AWESOME and let them come up with some really badass shi’ to help their local communities and governments.

There were some really great presos that I won’t go into too much detail here, but you should check as many of them out as you can on the Expo’s YouTube channel. I particularly enjoyed the mashup of marketing, Maslow, and media sciences that Dan Zarrella used to scientifically study social media. Kathy Sierra’s talk about passion (and call for a LOLcat Translation Project for the Federal Acquisition Regulation) was much more fun than I’d expected, and surprisingly cooler than Gary Vaynerchuk’s keynote.

Finally, the Expo’s social events were great places for me to connect with people I’d only engaged with online. It was AWESOME drinking beers and shooting the shit with Steve Radick, Chris Ramussen, Steve Ressler, Andrew Krzmarzick, and Steve Lunceford; and meeting new friends like Chris Bennett, Chris McCroskey (hmmm, AWESOME Gov 2.0 peeps seem to go by the names Chris and Steve….), Jacque Brown, David Hale, and the boys from Palantir. As a social animal myself, it was pretty rad to hang out with these cats and others that felt like “fellow travelers” in our particular, individual quests for AWESOME government.

In closing, the source of inspiration for any good Gov 2.0 discussion… TENACIOUS D.

Enhanced by Zemanta

The Gov 2.0 Expo has been a pretty amazing experience, speaking aside. I’ve met some really great people working at hyperlocal levels of government on extremely cool, forward-thinking means of connecting with their citizens. Sometimes you have to really have to embed at these events to get a good understanding of their value, and this one delivered.

I’ll write up a more in-depth analysis of the event once I’ve had some time to think on things. But in the meantime, here’s video of my 5-minute presentation from Tuesday’s Keynote Kickoff. (Thanks to the fine people at O’Reilly Media for recording, livestreaming and promoting this!)

Enhanced by Zemanta

Just hit SEND on the final “Instituting a Culture of AWESOME in Government” preso to be delivered at the Gov 2.0 Expo this week. I’m up at 5:55pm on Tuesday at the Washington Convention Center. If you happen to be in town and catch me, shoot me a holler on Twitter so we can connect later. There’s a social or some shit like that after the keynote Tuesday, and I’d love to hear how AWESOME my delivery was. ;)

I’m a complete stranger to Ignite-style briefing: 20 slides, 5 minutes, 15 seconds per slide. It’s either gonna be a fun exercise in bullshittery or a complete shit-show. HOWF!

For folks who aren’t going to make it to the Expo, I’ve uploaded the preso here for your viewing pleasure. Please feel free to leave a comment below and tell me what you think. I’m going to try and get video of the actual Day-Of, so be on the lookout for that in subsequent posts.

Enhanced by Zemanta

I’m using this post as a testing ground of sorts with which to work out the design of my 5-minute Gov 2.0 Expo talk on May 25th, 2010. As a result what you are about to read may seem random and disjointed at first. Fair warning.

I think what I’ll probably do is develop the case study as a full-on post for Must. Be. AWESOME!!! so that interested folks from the expo can come here and read through the entire narrative. What I’ll need to do then is make the 5-minute preso more of a pitch for people to come back and get the full effect. Plus, it’ll be a great place to start a conversation about the Tech Team, share experiences, continue analyzing, etc.

Original Pitch

“Instituting a Culture of AWESOME in Government: The Case of the IED Task Force Tech Team”

  • Purpose 1: Demonstrate how gov entities can exude AWESOME
  • Purpose 2: Extract lessons (positive & negative) from case study
  • Contraints: 45-min preso time shortened to 5 minutes — warrants major curtailing in presentation of findings

Major Themes in Research/Interviews

  • Righteous mission: helping to save soldiers’ lives
  • Brotherhood: team exceptionally loyal to one another, inside & outside of work
  • Fellowship: people & job were fun – weekly happy hours & grill-outs
  • Leadership: BG Votel  and LTC Jost took risks, backed up his people every time

Lessons Learned

  • The right mix of personalities will enable AWESOME in any enterprise.
  • AWESOME activity creates swarm of “antibodies” (naysayers, can’t-do’s, etc).
  • People will give 18hrs/day if the activity is AWESOME.
  • Small, super-empowered teams can change everything if given the chance.
  • Cults of personality and rabid positivity will engender loyalty between all echelons.
  • Middle management worked for team members, not vice versa.
  • The business of AWESOME is inherently and unavoidably social.
  • Ad hoc, task force structure engendered agility, effectiveness, & ownership.
  • Permanizing the organization destroyed team cohesion & introduced stagnation & irrelevance.

Unanswered Questions

  • How transferrable is this case to other parts of government?
  • If JIEDDO was borne of the Tech Team / JIEDDTF, then wasn’t the organization a failure? (because JIEDDO pretty much sucks today)

The IED Task Force Tech Team (circa 2004)

A note on formatting: I’m also currently fooling around with Prezi, a new web-based system of designing presentations that purports to help design better presentations by forcing you to think creatively, visually, and using mind-mapping techniques. The videos make it seem pretty cool, and I was considering using this for my Gov 2.0 preso. However, I’m concerned that the Gov 2.0 staff isn’t ready for the newness of Prezi (I’m not even sure of the file formats supported), and I’ve only got a few weeks to play around with it. Further, despite the New York Times‘ recent story on how tired of PowerPoint everyone in the Defense establishment is, everyone’s still using it and everyone’s used to seeing it.

In 5 minutes’ time, I’m not even sure the benefits of Prezi would be worth it. Still, I may do a longer version of the talk in Prezi to post here on the blog at a later date. We’ll have to see what the future demand looks like for this case study.

Enhanced by Zemanta

A wrench got thrown into my Gov 2.0 Expo preso planning while I was picking myself up a bride Down South. It actually made me question whether I wanted to go through with it at all. However, after some hard thinking, I’m putting on the smiley face and taking my cheek-splitters like a man.

Let me explain.

The Gov 2.0 organizers contacted me about my presentation, “Instituting a Culture of AWESOME in Government: The Case of the IED Task Force Tech Team,” a couple weeks ago. They told me that they were altering the format of the conference and that my presentation was being shortened from the originally proposed 50 minutes to FIVE minutes. Apparently, they thought it would be so much cooler if they bunched in a ton of 5 minute “rapid fire” presos around the keynote address. There were a lot of platitudes about how great my proposal was and how AWESOME it would be condensed to 5 minutes.

How do you “condense” a case study, which by definition is the result of an analysis? It’s like saying, “Hey, dude, I love your book! Can you give me a pamphlet version?” Considering how much effort I’ve already put into researching this topic, a FIVE MINUTE presentation does the material – especially this material – a disservice.

I wrote the organizers back expressing my discontent but also offering an alternative: how about I come up with something else related to creating AWESOME culture in government that I could adequately fit in the time limit? Apparently, the organizers really wanted the IED Task Force Tech Team case study but felt it wasn’t topical enough to warrant a full panel. They adamantly demanded I present the same topic as originally proposed. Basically, do it or hit the road, jack.

Now this all sounds like inside baseball and dirty laundry, but I’m recounting it to demonstrate something. Despite the sheer shittiness of the situation, it forced me to sit down and think hard about what I was being asked to do. Is it worth taking a stand against this tomfoolery? Should I risk standing behind my material if it means getting kicked off the ticket? Is it even possible to give a good presentation on my original topic under these new circumstances? Am I betraying my AWESOME if I cave to these new demands? In this case, can you still be AWESOME living on a compromise?

At the end of the day, I accepted… and here’s why:

  • I can’t trade the exposure I’ll get at this conference at this stage of my career.
  • It will be an even more challenging exercise boiling my preso down to something entertaining and valuable.
  • I think I can still deliver an AWESOME preso.
  • Who knows what I can get away with on the day of?

Don’t be mistaken though: I’m not compromising on this. I’m acceding to the organizers’ demands. I think that’s an important distinction.

All that said, though, I’m still gonna fucking ROCK this expo. Fifty minutes, five minutes, whatever. It’s just less time into which I gotta pack a more concentrated dose of AWESOME.

So bring a spare pair of panties– IT’S ON.

Enhanced by Zemanta

A couple months ago, I told y’all about submitting a proposal to the Gov 2.0 Expo occurring in May. It is with glad jazz hands that I can tell you my proposal, “Instituting a Culture of AWESOME in Government,” was accepted by the Expo committee! I’m now listed as a speaker alongside some pretty frickin’ AWESOME company (like Gary V!).

As promised, I’m going to blog about this experience. It’s really the first time I’ve ever had the chance to analyze and put forth a case that’s totally unique (at least in my opinion), so I’m really excited about the opportunity. I am deep into collecting data for the case study, and one method I’m using to do this has been reaching out to former members of the IED Task Force Tech Team for stories, pictures, and other info that may help my analysis. It’s been a BLAST reconnecting with these guys. We had a lot of fun back in the Tech Team days, which is one cornerstone of that experience’s AWESOMEness.

I have gotten a crap-ton of fun stuff so far, a lot of which I hope makes it into the final preso. But to give you a tease, here is the first logo one of our Tech Team brethren, Shane Gilmore, cooked up back when we first went joint.

JIEDTF2

Enhanced by Zemanta

Within my community of business owners, contract wranglers, and salespeople in DC, I’ve seen a lot of long faces lately. Since the economy crashed and the new administration took office, business development people have had a harder and harder time selling their wares to federal clients and closing new contracts. Most of what the government does award these days often looks a lot like continuation rollovers, wherein some asshole COTR (that’s contracting officer’s technical representative for you neophytes) finds it easier to perform minimal competition compliance just to ensure he or she doesn’t have to deal with the added headache of transitioning between incumbent contractors and new winners.

Despite the reasons for the recent slowdown in federal business, the bottom line is that many companies are finding it harder and harder to deal with their onetime great clients. Contracting officers (COs) and COTRs have become outright hostile to some companies, turning required program management into offensive, often farcical dehumanization of the performer(s). Folks I work with vent often and loudly about how the typical government contracting churn in Washington has gotten even worse.

Also, as hard as it’s become to acquire a contract nowadays, there’s developed the added insanity of dealing with a growing crop of dickheaded contract administrators. I cannot tell you how many times I’ve heard from businesspeople in DC complaining about how unmovable, boorish, and downright inappropriate some government agencies can act towards their performers. Some government officials who administrate such contracts blatantly tell their contractors that part of the gig is to take shit from them, from simple incompetent management on down to the most revolting of behaviors toward gender and racial lines. There seems to be this attitude that, goddammit, the government knows best and since I’m the government’s representative on this contract, you better listen to me. This behavior is not just unprofessional, it’s insulting, repulsive, and deserving of public punishment.

This situation – Our Great Client Crisis – is not new and is not AWESOME. In fact, it’s pretty fucking lame.

I have one piece of advice for these folks, and it’s advice that’s applicable to any business, company, consultancy, or individual:

If your client treats you like shit, then kick ‘em to the curb.

Subjecting oneself, one’s company, and one’s people to abusive treatment by a client just because they’re paying you money is ridiculous. Despite how many millions of dollars you’re making or could stand to make, it is simply not worth the emotional loss your business will take when scads of your people begin feeling The Mighty Fed in their poop chutes. Furthermore, the added frustration of trying to secure such work from people who may be willing to pay for your service but not understand it (“Let’s get some social media on this advertising plan!”) will only serve to waste more of your time that could be better spent with AWESOME clients.

Image courtesy of She's Unapologetic.com

So, if you’re in such an abusive relationship, what can YOU do about it? Here are a couple ideas that may help:

  • Call ‘em on it: The next time one of your clients purposely demeans you in public, call ‘em out on it. Publicly. Federal workers particularly are often not willing to duel over degrees of impropriety in public. Making the behavior public will often cause them to back down. That said, be ready for the dick move of having your contract terminated for no reason afterwards.
  • Make ‘em smarter: In a lot of cases, your clients aren’t acting like assholes because they want to. They just don’t know any better. So defuse the situation by offering to help them out. Tell them about other clients you’ve had who have expressed the same educational roadblocks in whatever specialty you happen to deal. You may even make a friend out of them. And friends give friends work in the future.
  • Call Fraud, Waste & Abuse: Each government agency has a hotline set up to report instances of fraud, waste and abuse amongst its employees. Use it. It may take time for your complaint to get addressed, so be prepared to go on the record, which can speed things up. Google your department of choice and be sure you’re calling a number at a high enough level that it warrants attention from that agency’s Inspector General.
  • Lodge a protest: Federal contractors in particular have clauses in their contracts providing for their right to raise protest against their COTRs for impropriety. Exercise this with caution however: these protests go in your company’s permanent record and may taint evaluators’ opinions of you during future competitions.
  • Find new clients: This is my favorite suggestion. You don’t like who you’re doing business with? Get out. Get out and find some dudes you DO like. If this requires you retooling your corporate offerings or marketing, then maybe you should take a hard look at your business and decide what market you really want to play in. Stop being a slave to million dollar contracts. Trust me: the payoff is not worth the stress and abuse you’ll take over the life of the contract if your client is an asshole.
Enhanced by Zemanta

There’s been a slow, creeping movement in DC these past few years to renovate the way we think about government. The Gov 2.0 Summit and Expo, put on by O’Reilly Media and TechWeb, drew a monstrous crowd of people last year to explore challenges, requirements, and strategies for adapting the phenomena we associate with the social media movement to the government of the future.

I just submitted a Must.Be.AWESOME!!! pitch for the Gov 2.0 Expo in May 2010. My topic is called Instituting a Culture of AWESOME in Government. The approach I intend to take on this preso involves analyzing a case study of how  AWESOME can exist and flourish in government today. I chose to use a very specific case study, one near and dear to my own heart: my experience with the IED Task Force Tech Team from January 2003 to April 2006.

Du4 pretending to be King Shit at the old Tech Team trailer

Du4 pretending to be King Shit at the old Tech Team trailer

My intent behind examining the Tech Team stems from the entire team’s own reminiscences about our time there. Not a single one of these exceptional people would tell you that working on this team was anything less than AWESOME. The team’s mission was to seek out, evaluate, and rapidly equip lifesaving counter-IED technology to American soldiers serving in Afghanistan and Iraq. There were long hours and a lot of opposition to our methods (our approach basically bucked and made irrelevant the entire Army acquisition system), but our cause was just and we celebrated it joyfully every day.

I’m really looking forward to digging into this study. It gives me a chance to catch up with a lot of my original teammates, all of whom left an indelible mark on me due to their profound professionalism and loyalty. I loved working with these guys, and I’d lay down in traffic for ‘em any day. That’s the kind of culture we need to instill in government today.

With some luck, my submission will get picked up by the Gov 2.0 folks, and I can get to work putting together a badass preso. I’ll blog about how it’s going as new developments occur; maybe something I’m looking into will help YOU in instituting a culture of AWESOME in your own organizations.