Tuesday, June 30, 2015

Götterdämmerung

Scoreline - June 30, 2015
USA: 2
Lloyd 69' PK; O'Hara 84'
Germany: 0

Biggest match up in women's soccer history.

Everything to prove - against Germany.

And we OWNED them.

Dream Team? Yeah, kinda.


Everybody was playing out of their minds: Holiday, Brian, Sauerbrunn, Krieger, Lloyd, O'Hara, Heath, Rapinoe, Klingenberg, Morgan, Solo....

Oh, and Johnston! Hell, yeah, Johnston - I'd say the player of the tournament - but Lalas said that, and I swore a blood oath to disagree with everything that man says.

Still - Johnston - what a game - offense, defense - and YES - she pulled down an attacker in the box, but the Soccer Gods decreed that this would not stop us.
Johnston: Clearly better than you.

And the crowd... Just magic - Morgan's first big shot wide had the place jumping outta their seats.

Lloyd? Flat out aces. Old Guard? I'm fricking DRIVING this bus.

Swarming midfield, Solo psyching out Sasic...

Yes, Germany can pout about the PK, but they had their chance and blew it. Crappy calls are part of Soccer - and lord knows, the US has had their share. (You think I forget? I FORGET NOTHING).

This was the culmination of the USWNT's campaign. They were on their game against the world's best and beat the crap out of them.

I feared for this team in the group play, but they are clearly on afterburners now.

Go USA.

Monday, June 08, 2015

Rapinoe to Rapinoe

Rapinoe: American badass.

Not our best effort by a long shot. We looked really ragged at the back for most of the first half.

And I don't know if Wambach is putting too much pressure on herself, but two flat our misses by our used-to-be guided missile forward just boggle.

And after a fortuitous bounce goal, Rapinoe looked like she was trying too hard as well. All kinds of whiffed crosses, flubbed passes - even a missed throw in.

And then she does this sh!t:



And this was after getting the ball at the half-way line. She ran half the length of the field, looked up and thought

Well, everyone thinks I'm gonna cross - I'll just shoot this F*&-er.

And boom! Low to the far post, for the icer.

Take NOTHING away from Press & Laroux's efforts to get the go-ahead goal. Leroux is all kinds of hustle and guts, and Press threw down ironclad evidence (if any was needed) that-



COACH? 

I AM 

A FORWARD

Hell's yeah, she's a forward -  and make sure she gets more playing time in the middle, eh coach?


Sad for the Matildas. De Vanna was her usual full-throttle self, she was criminally unmarked in the box and instantly reminded the US why that is a bad thing.

I hope the Aussies get some success, but looking at the rest of their schedule - it's not like it gets easier from here.

USA: 3
Rapinoe 12', 78'; Press 61'
Australia: 1
De Vanna 27' (who else, seriously?)

Sunday, June 07, 2015

Feels like 2011

Hell yeah, I remember.

122nd minute.

Ian Darke, Julie Foudy and the rest of all right thinking people losing their minds as one.

I just shortened the lives of countless Brazilians.

A fan could live a lifetime for this sport and never get a moment like that.

The Cup doesn't care if you are worthy and the Soccer Gods have always been @ssholes. 

Japan was a fairy tale worth telling, but Germany 2011 should have been ours.

And here we are, back for another helping of whatever the Soccer Gods choose to serve us.

Defying reason and the odds, we still have Rapinoe, Rampone - even Wambach.
Germany is - once again - terrorizing the minnows, and the Samba Queens are the same as always.
This time, the French are looking solid and the Dutch look to be the newcomers who could mess things up.

We have injuries, we have scandal, and everyone would love to be the team that sent us home.

Still, I can't wait.

Go USA.

Rapinoe to Wambach for the win.
Always and forever.

Friday, June 05, 2015

Farewell to Megatron

I'm in our stakeholder meeting, a few weeks ago - presenting one of our new features done by the west coast devs and things are not going according to plan.

Being me, I blurt out "That's not right."

In front of a crowd is never the right time to encounter a new bug. Yet it happens.

I try a few more times, before realizing that the app is behaving fine, I've just completely misread what was happening.

I reset, and get the demo done and hand things over to Noddy.

Noddy launches into their part of the demo - a feature that was supposed to be RFD in January that is only now taking tangible shape in code. Noddy's dev's have endured missing requirements, late requirements, incomplete requirements - and late edits when they were still coding.

Noddy has created features with a single requirement - that is wrong. Noddy's feature work has spawned endless "fix it" stories, to correct some omission or other mistake. Each correction will require changes to automated testing, more time and additional expense.

But now, Noddy has landed the first wedge of their feature - and it's...

...it's a mess. The overall problem that this feature is supposed to solve - CANNOT be solved directly by our product. This feature's value rests on the dubious assumption that our users (who hate data entry) will enter data into our application, print out that data, and then re-enter the same data into the Nachen website.

This makes sense to absolutely no one.

Because Noddy has been on this feature, it is being built in incredibly small slices of functionality. Which is agile, but the fact is this feature is a webform. Something as basic as a webform does not need to have a lot of slices to be built by an agile shop.

Sure, you can say, build me the basic form without the ability to validate it. Then validate it. Then make the printout. Then show me how to find all the forms I've filled out. And so on.

Noddy has turned this into story pong, where features are added - then moved, then shifted to other stories, and finally landing in a heap right before a looming deadline.

Noddy's built their form, and it's maybe a third of what it needs to be in order to be a basic, dumb form. The stakeholders are not mean, but they ask pointed questions until Noddy starts deflecting in their usual way. Talking technical and promising future work until people lose interest.

Pinning Noddy down is just too much work sometimes. Even I've given up most of the time.

The meeting ends and I'm off to get a beverage. I meet HockeyTwo in the breakroom. They laugh at my struggles in the demo, but as they put it "at least you fess up to problems. If that had been Noddy? They'd have pressed on, never said a word, and hoped nobody noticed."

It's a remarkable how often a co-worker can (out-of-the-blue) break into a critical observation about Noddy.

*     *     *

The Noddy effect. It's amazing.

I've been in the hallway and been accosted by co-workers, "GOD, Noddy is just so good at pissing people off, huh?"

I've been at team building exercises that have turned into full blown Noddy venting sessions. One of my co-workers related the story where once, at a work sponsored family fishing outing, their six year old child had caught a fish and wanted to catch-and-release like everyone around them.

Noddy had intervened and told this child (mind you, someone else's six year old child) that "No, that fish is invasive, you need to kill it."

Now, I can imagine saying something along those lines, in the absence of thought. I might do that. But faced (as Noddy was) with a weeping six year old asking Why? Why does my fish have to die? 

-most of us would reconsider. Not Noddy. They insisted - to a six year old - that the fish must die.

And on and on. Ad nauseum to anyone unfortunate enough to be near an employee of NerdHaven. Everyone has a Noddy story.

*     *     *

I leave the breakroom and head back towards my desk, then I remember I have something to check on with Dragonman.

On the way there, I see Atlas talking to Noddy. Atlas wants Noddy to meet with them in their office. Noddy is begging off, they have to do something, but Atlas is insistent, "Right after."

Now, I know Noddy's been on the hot seat for a while now. In fact, most people on UX know that as well. Noddy gets regular meetings with the boss, and a host of performance monitoring activities have become the norm for our entire team.

Hearing Atlas wants to meet with Noddy is filed away.

*     *     *

The day goes on. I'm back to my desk. Runner, Dash and I have our own little UX Shangri-La, separate from our team, and a genuinely nice setup. Windows, natural light and plant life.

Plus? No Noddy.

Our team hired two more devs and there weren't enough chairs for everyone, so Runner and I volunteered to move to the next room.

Noddy offered to move as well - and BigDog was about to go along with it, logic being move all of the UX crew at once - but Runner shot BigDog a look that could maim.

And BigDog pivoted on a dime. "murph and Runner will move over to the other room." Noddy would end up staying in the team room. In a way, this made the most sense. Noddy would be creating work for the team, while Runner and I were doing work exclusively for the west coast devs.

But mostly, we were sick to the brim of Noddy.

I've thought long (way too long) about what I think of Noddy as a co-worker.

They are not:
  1. Honest
  2. Hardworking
  3. Diligent; or
  4. Professional
Above that, they have a disastrous personality and virtually everyone hates their guts. 

Runner deserved a break, and I was happy to get one as well. With the new UXer, Dash - we've got a great thing going. Dash is cool - and a pro.

I miss our devs, but I love our new digs.

I ground out some work for the rest of the day, and was on the way out when I run into OneTwentyEight. 

"What's up with Noddy?"

Huh?

"After showcase, they came back, groused something about 'might as well hand in my resignation' and left in a huff."

!!!

This news is positively electric. Nobody wants to call it out as fact, but everyone is thinking it.

Noddy is gone??  

*     *     *

The next day, Noddy is nowhere, and their laptop is missing. Questions are asked at standup, but no one has solid info. Someone thinks that Noddy's child was in the hospital. This is greeted with a certain amount of disappointment. 

Later that morning, we get an email from the boss: Noddy has a family emergency and will be out until the next week.

So that's it. 

Runner is jubilant. Noddy is gone! But family emergency has me wondering - if they are gone, the boss would just say so. I remember all the crazy with H, that dragged on and they ended up coming back. I don't want to get happy too soon.

But days roll on and Noddy does not come back. Frankly, with Arwafn blowing up and damage control in full swing - I don't notice their absence. 

The next week, Gumby tells everyone that Noddy will be gone "indefinitely." This gets all the rumor mills flying, but there's still precious little to go on. Noddy's not here, and we don't know when or if they will be back.

*     *     *

I speculate openly with HockeyOne & HockeyTwo - towards the end of the week, I'm feeling flip and launch into "I think this may be it."  HockeyTwo is skeptical, but clearly thinks this would be great news. Noddy being gone has created a news item, and more than a few water cooler discussions stray into what if?

*     *     *

And then its Thursday, and I walk into standup late. I've been in some catchup session with Gumby or something or other - I've been running late for everything lately - and I blow into the team room right behind Runner.  They look pissed.

The team goes through the standup routine and BigDog is going through their list -

- And I see Noddy back into view. They'd been standing right behind Runner such that I couldn't see them at all. 

And there's the answer. When's Noddy coming back? Right now.

And they are back with a vengeance. We get the story on their child being hospitalized - they are okay now, but it sounded like quite an ordeal - and then Noddy is back onto muddling their way through their allotted work. They have meetings with Ihaq, and are working with Ahhh, the new UX in the west coast office.

Ahhh is a special case, and I'm starting to think that Noddy and Ahhh are on the same page. Noddy can wield a firehose of bullsh!t and I'm afraid Ahhh is starting to think Noddy is credible.

For that matter, I'm worried that Ahhh & Dash are going to need the talk about Noddy in the near future. Runner and I have studiously avoided talking to Dash or Ahhh about the Noddy situation. We'd hoped that the situation would be sorted out before it became necessary, but that hasn't happened.

Dash and Ahhh deserve to know that Noddy should not be relied on. That their pronouncements on Nachen work should be double-checked - always. 

They need to know that Noddy is borderline useless in a great many ways - but...

How do you start that conversation? I want Dash and Ahhh to make their own conclusions. I don't want to just start in with "Noddy's a useless hump," but I don't know a middle ground. I've punted and avoided the issue.  When Dash needs to work with Noddy, Runner and I try to assist.

Dash is no fool, and they have to know that there is a schism between Noddy and the rest of UX - but watching them struggle to collaborate with Noddy is hard. We want to jump in and say "Forget what Noddy is saying, do what you think is right."

The devs hold their fire as well. They are pros, and they are focused on getting work done, not smoothing things out for the new UXers. Sooner or later, they will figure it out on their own.

*    *     *

I'm running late on a Wed and want to check in with the boss before standup. Gumby's in their office meeting with Portal and Noddy on something, so I head to the desk and chat up Runner.

BigDog strolls into UX Shangri-La.

"One at a time, I need all of you to come to BigSad." BigSad is the main conference room.

Runner & Dash are confused - thinking we are each to go to BigSad by ourselves and then come back before the next person goes.

I took it to mean we were all to go to BigSad, but one by one so as not to make a big deal out of things.

I have a momentary flash of panic. OMG BigDog is leaving! Which would be biblically bad. BigDog is awesome and they are about to have another child. Why would they change jobs? They can't do that to us!

*     *     *

We make BigSad together, contrary to orders. Most of the team is there. BigDog tells us to close the door and starts in.

"No other way to say this, but to say it..."

Please, no.

Just no.

I love working with BigDog, they are awesome. They are the most supportive dev I have every worked with - and they kill it in the dev space. Their status as team lead has taken them away from the coding they love and they've been clearly frustrated by it... And they've been fed a steady diet of crap work by Noddy.

OMG, Noddy - if you've cost us BigDog, I will personally-

BigDog finishes in a rush.

"Noddy is being let go today. Portal asked me to get the team out of the room so it won't get awkward."

*     *     *

When the moment finally arrived - it was a total ambush. I was exhausted from the Arwafn grind, terrified that BigDog was leaving, and frankly - numb.

Of course. Portal. Duh. They always do the reaper work.

And today they showed Noddy the door.

Noddy. The person who has caused untold misery and wasted hours - will burden us no longer.

I made an excuse to go to the breakroom and get a beverage. Before coming back, I swung by HockeyTwo.

On the down low, deliverance is at hand.

HockeyTwo nodded somberly. They were totally on the same page.

Back in BigSad, we are told the information is close hold until we hear specifically that it is not.

Oops, already blew that. Odds are good HockeyTwo has at least told HockeyOne.

After a brief stay in BigSad, we are allowed to go back to our desks. Noddy has already been shown the door.

*     *     *

Official word comes during yet another Arwafn meeting. Gumby sends out an email to our team announcing Noddy no longer works at Nerdhaven. 

I'm sitting across from Teacher, who utterly detested Noddy - and have to share. With Gumby's email maximized on screen, I spin my laptop around and offer it to Teacher.

We're on a phone conference, so Teacher keeps composure, but leans over to Juice and relays the news in a whisper. Juice looks at me, eyes wide and I make the touchdown sign.

Somehow, spreading the news makes it real.

This has really happened.

*     *     *


The team went out for a celebratory lunch, and we read Dash into the situation. Dash took it well. "I guess I don't have to feel bad about wanting to redesign all of Noddy's work, then."

Nope!


Later, I'm in the hall and I run into SnT, a wonderful human being who does great, high stress work and yet still finds time to be amazingly nice. 

Did you hear?? I want to say, but SnT's clearly clued in. This news has whipped through NerdHaven like a shockwave.

SnT and I swap Noddy stories for a bit and they're all like "I wanted to give them the benefit of the doubt, but after that whole egg-kicking thing, I just knew they were a total asshole."

To hear someone as generous as SnT launch into profanity is no small thing.

I laugh and share our nickname for him "We called them Noddy."

SnT blinks.

"Because they were always falling asleep."

SnT busts out laughing. "We called them Megatron."
(apparently, Noddy was fond of using a particular buzzword that ended in '-tron' - thus, Megatron).

I bust out laughing, and we stand there laughing in the hall until we have to explain ourselves to a passing co-worker. And then they start laughing.

*     *     *

And before folks start accusing me and mine of being mean spirited, I would like to offer the following justification.

I tried for over a year to be sympathetic to Noddy. I gather their home life is not easy. But I have watched this person bring misery and additional work to a team I am very fond of for a very long time. 

An untold amount of work was wasted cleaning up after Noddy and stepping up to do stuff they should have done. 

Noddy added stress and uncertainty to the team - and very little else.

Everyone at NerdHaven gets to be happy that those burdens have been lifted from them.

I can separate any feelings of empathy for Noddy and their family from that. Yes, I hope things don't go too badly for them. I genuinely hope they land on their feet. That they find work that inspires them to actually do the work and not just phone it in.

And I sincerely feel sympathy for Noddy's family.
A family whose chosen breadwinner decided to surf Ebay for collectables rather than do their effing job. 

Who, when faced with the prospect of imminent professional death, chose to continue the same half-assed everything that landed them in hot water in the first place.

That family deserves sympathy.

But mostly, I'm happy for my team. The UX lost a staff member and productivity will increase. Morale will improve.

And we will do better work for our customers. 

We get to be happy about that. 

Free and clear.

Thursday, June 04, 2015

Derailment, part IV

That's not Agile!

I cannot tell you how often these words are uttered these days. Arwafn has gone over the cliff, and Nerdhaven has had to publicly walk back from its launch posture of "Wow, look at this!" to the less inspiring message of "Watch this space."

Upper management is involved to an alarming degree.

Faced with the possibility of completely shutting down Arwafn, dev effort was flung at the TURN issue to determine which customers could retain the feature and which could not. The SMEs drew a line in the sand and in the end, about a third of our customers could keep the feature.

Which would be encouraging, if it weren't for the filters. Arwafn has more than a few, and two of them in particular are near total flops. Both are based on fields that customers have never been required to supply. We'd assumed they were, and our limited beta tests looked promising. Data flowed in, and the filters acted on that data.

Trouble was, that data was crap. For some customers, Filter A's key field was being populated only 20% of the time - or was co-mingled with another field, rendering it unusable. In beta, these filters appeared to work, but what they would show was wildly inaccurate.

In beta - our users were not doing a rigorous comparison between their system's data, and what Arwafn was showing. Our users viewed the beta sessions as a preview - play time. And while they surely care about the accuracy of the report - they evaluated Arwafn based on what they imagined it was doing.

Fellow UXers of the world: learn from me. Spell out exactly what you want your beta testers to do. If you need them to do system testing, you need to tell them that. Regardless, you should ensure that your feature has system testing with live data before you green light it for wider release.

But some customers had good data. And there were options for us to explore - an alternate key field might get us there. It would mean an immense amount of re-tooling, though. The thought of it made my mind hurt.

Filter A was the good one.

Filter B was based on a field that not only had issues with being populated only some of the time, when it was populated it was almost always the right kind of data - at the wrong point in time.  Filter B is supposed to present its value as of a specific moment - and it was showing a value that was a few days later. And those few days were killing us.

We had a few customers who were happy to get the data at all - even asked for Filter B to be left on despite the time shift - but Arwafn is supposed to follow a standard. A few days later was not the standard. With over 100 clients active on the report, we only found 1 who had a working Filter B.

Worse, when I spoke with Data about our prospects for getting Filter B working, I read out the point in time requirement and Data just groaned. "If we ask the customers to send us an entirely new set of data, we could get closer to what is needed. But the literal criteria for Filter B does not exist in any data element that I know of."

For the millionth time, I ask myself - How is it I am learning this now? How did we get to the point where we have code in production, and I literally just found out that the data point I need does not exist?

And I don't have a good answer for that.

UX was primarily focused on the front end stuff - what the user sees and touches - and the back end stuff (where the digital bodies are buried) was supposedly the realm of other smart people. Our former UXDir encouraged us to provoke the change by asking for things without looking under the hood. "We'll figure it out," they'd say, "we can't design based on just what we have now, or we'll never make new things."

And there is a point there. If every design is vetted against the current codebase, legacy code limits what your customers get.

Fellow UXers of the world: learn from me. If a feature is dependent on a lot of user supplied data, design it to fail gracefully when some or all of those elements don't show up.

That's pretty basic, but its one thing to nod at a good idea in principle, it's quite another to realize that your feature is built on a house of cards while you are working on it. When all of this was happening, it all seemed so...right. And now Arwafn was a pile of roadkill in the middle of the road.

*     *     *

And everyone was rushing in to help. Which is great, but with upper management calling folks out, the agile culture in NerdHaven was beginning to crack.

Upper management said: Turn off Filters A and B. NOW.

And NerdHaven jumped to obey. Devs created branch code, stopped all other feature work and slammed two shutoff switches for Filters A and B into production. Devs were up in arms, because upper management never tells NerdHaven to work on this feature or that feature - and now they were.

But a fire was burning and this would put it out, so everyone got it done.

Next up was the TURN problem - and dear God what a mess. Telling upper management that the key value for Arwafn is being adulterated by our product was the easy part. Management realized there was a problem and TURN fit that bill. Resources were allocated to fix this issue and commandments were given.

FIX THIS. NOW.

The problem was, as we fixed TURN for Arwafn, we realized that TURN was used all over our product - and fixing it for just Arwafn would mean that other features would be out of synch with Arwafn.

Mind you, I'd always thought of Arwafn as a modest feature - and it is. Just a little report in one corner of the product. But TURN is a value that is used in the NumeroUno feature, and Nachen work, and more besides.  I spoke with Sprint when we started fixing TURN and they gave me the full list of what they knew would be affected and it was alarming.

Then, in the middle of one of our situation room meetings for Arwafn, I started spelling that out to the group.

This launched another round of anxiety telephone and soon fixing the TURN issue for Arwafn, became fix TURN everyGoddamnWhere.

Which meant the scope of work just ballooned - which naturally had to be reported up the food chain.

Upper management's response was predictable:

FIX EVERYTHING NOW. AND SWEAR IN BLOOD THAT THIS WILL BE THE LAST OF THE TURN PROBLEMS.

Now, you're an agile dev shop and you get this kind of directive. What do you say to that? There is absolutely no guarantee that we will get everything in one go.

The SMEs are being asked to sign in blood that everything is fine from their perspective - and they are already anxious about the current state of things. They don't see everything and now they want to see EVERYTHING.

We've got SMEs crawling down our necks asking for more access and more analysis. And then Gumby's asked to provide proof that UX has discussed our designs with SMEs (in a meeting, with no warning - so they don't have that information, which itself becomes a thing)...

...and now we're careening towards Waterfall.

Waterfall: an epithet in dev shops. Shorthand for let's add more analysis and more documentation and more signoffs and when that doesn't result in a perfect product - slow down and add still more analysis/docs/signoffs. Lather, rinse, repeat.

All the UX folks hate this idea with a passion, and I pointedly ask if this change is the new way of things going forward, or just until we get Arwafn/TURN fixed.

Gumby is direct, "this is going forward."

I feel like throwing up. Yes, we steered the company in the ditch, but we learned a boatload and absolutely nobody wants to go through that again. We will be more vigilant, and we don't need more goddamn documentation.

I point out (for the umpteenth time) that more SME contact in our process would not have caught our data issues. The SMEs don't go under the hood any more than UX does. But we have experts in house who do, and we will be joined at the hip with them the next time we roll out features driven by client data.

Let's do that, I say, before we get all process heavy. We are already getting berated for being slow, all this bloat is not going to make software happen faster.

Wasn't this why Agile was invented? to prevent this kind of stuff?

But the powers that be are unassailable - we will add process and hope this will get better  - or blow over.

Or something.

*     *     *

Today was a day that threatened to be the end of all things. I was roped into three meetings in a row, one about some future data issue I knew absolutely nothing about, one with the SMEs to discuss their (well aged) laundry list of desired features (that have absolutely nothing to do with Arwafn/TURN), and one that I was dreading most of all: a review of all our Arwafn/TURN work with the SMEs.

The laundry list meeting was a total bust - the SMEs want us to build what they want (as opposed to what Product has prioritized, or what the customers want). Their list of wants will solve issues that the SMEs have experienced, but may not do much to address root causes of user pain. And it is very unclear if all the items on the list should be solved with more computer code. Some might literally be user error. And all of the items are broadly worded concerns that cannot be vetted without specific examples of the behavior in question.

Sprint is in the meeting with Gumby and I and (heroically) volunteers to vet the list for the SMEs. I say (as diplomatically as I can) that this list should be given to our support staff, who can explain the inner workings of the application and perhaps get to the root of the matter without us trying to build a solution based on a speculative issue. I'm not sure the message took, but Gumby and Sprint are clearly way ahead of me. They want to do right by the SMEs, but route support work to support resources.

And then the review meeting. I wanted to keep my hackles in check, but this had all the hallmarks of being a "why did you put the button there?" kind of discussion. One of the SMEs, Ihaq, had ridiculed our design of a new form and I was dreading a new session of "Move that button, because I want you to."

The lead SME was Voldemort: brilliant, hardworking and overworked beyond all reason. They started out with a few probing questions which Gumby fielded for the first few minutes. Ihaq was there and clearly confused about what we would be running through. They had a few questions they wanted to run through before we got started. Ihaq's questions are never brief, and usually involve follow ups.

It was getting awkward.

When we got to the list of feature work, Gumby gave me the podium.

At the risk of appearing arrogant - I am pretty good at explaining things. So long as I understand something, I can transfer that information to pretty much anyone.

And the work we've been neck deep in for the past two months is stuff I can't help but understand. I wake up in the middle of the night thinking about this stuff.

Grok it? Hell, I wrote it.

And I go to town. You have a question, Ihaq? I got you. Voldemort wants clarity on the hideously technical matter of historical TURN values?  I got you, too.

And as soon as I realize that the SMEs are (rather predictably, I might add) solid professionals trying to do their jobs - the tension goes out of the meeting. The SMEs are not there to grill us, or re-design our work - they are literally trying to understand where the work is now and where it will be when we are all done.

Gumby asked our new UXer, Dash, to study our stakeholder demos and they pointed out a host of issues with how we present our work and how it is consumed and retained.

Predictably, shortcomings in our presentations leave lasting misunderstandings in the SMEs as well as others in our organization.

Having this Q and A session allowed us to close that gap for Voldemort and Ihaq at least, and at the end of it - it was a really good feeling.

Voldemort was exultant "That was awesome."

And I cannot tell you how much better that made damn near everything.

Yes, we have a metric sh!t-ton of work ahead of us, but we are beginning to round the corner and we've started to mend things with the SMEs.

The technical work is in flight, the release date is set. Our culture has taken a massive hit to the jaw.

But if today was any indication-

We can do this.