I'm just wrung out.
I'd intended to walk through the full (and truly epic) windout of the Ahhh saga - but I never seem to find the energy.
Summing up is only marginally less unjust than skipping over it, so here is the abbreviated version. On a week when Gumby was out on PTO, Ahhh announced to the team that they'd taken another job and would be moving from the west coast to the shadow of the Smokey Mountains.
As most of the team shared a negative view of Ahhh, there was the usual mutterings of 'best wishes' and what have you, but the relief in the room was palpable. Ahhh was constantly inserting themselves into the process of tracking work, but was doing painfully little
actual work. And they had been - inexplicably - put in charge of a critical piece of functionality. They'd written up a story for the team whose centerpiece amounted to "Do these 3 impossible things, yadda yadda yadda" and then went out of the office.
When the devs encountered this, they came to me in lieu of Ahhh. I read Ahhh's story and was completely mystified. "Magic" was our former UXDir's favorite shaming weapon when critiquing one of our stories. Ahhh's story was full of Magic. Not that a UX needed to write down every aspect of how a story would work, but they had to have had the conversations to validate that what they wanted was feasible. Ahhh had done none of this, so the devs were clueless of what was needed or where to even get it.
As soon as this was clear to me, I told the devs to skip those portions of the story and finish what was known and defined. We could work on the impossible items once Ahhh was back to better define what they were. Stop the bleeding, regroup.
I knew this would make some waves, but there was absolutely no other alternative. Ahhh was out - I didn't know how they felt the impossible things could be accomplished, and Ahhh had neither told the devs verbally, nor wrote it down.
Naturally, I had underestimated Ahhh. I called them to advise them of the situation and spent (I am not kidding) an hour on the phone telling them what it's taken me a paragraph and a half to tell you. Ahhh wasn't getting it. They seemed to think there was enough detail at first, then when I asked them for what the devs were asking for, they suggested that what I was asking for wasn't their responsibility.
For an hour.
They then went to Gumby and Ihaq and told them the feature could not proceed because I had insisted on a different approach. I ended up clarifying this numerous times to the boss and to others that "hey, all I said was - 'we don't have enough info to know how to do this in the story. We'll do this when we have the right info.'"
I then called Ahhh directly and said basically 'let me have it,' and got treated to an incredulous Ahhh asking why I was messing with their story.
Ugh... I'm failing at this summing up thing. I think I ended up burying the hatchet with Ahhh at the end, but Ahhh's goodwill was still suspect. On their last week at NerdHaven, Gumby asked me if there were loose ends I was worried about with Ahhh's departure and I said we needed to make sure we got all of Ahhh's user research.
Up until the last week of their time with us, Ahhh had shared exactly one file with the UX team, a file that Gumby had made them co-author with Runner. Runner had taken a first crack at it and Ahhh had independently started some epic research piece. When Gumby told Ahhh that Runner's PowerPoint would be the final format for the report, Ahhh petulantly disposed of their own report and sent Runner two photos to include in the deck.
This was all we'd seen from them. Week after week, we were told that Ahhh was doing 'user research' and I'd spent weeks asking to be invited to observe their sessions or see their recordings. All I'd gotten was pushback or silence. With the end in sight, Ahhh finally posted three powerpoint files on our wiki detailing their user research efforts. The files were light, but not badly done. One of them drew heavily on the T-E-R-R-I-B-L-E user test sessions I'd forced my way into earlier. Reading the file it was hard to put faith in the conclusions. More importantly, each of these files touched on feature work that Ahhh's fellow UXers were working on - none of us had seen them until now. Likely we wouldn't have seen them had Gumby not made Ahhh give them up.
Ahhh was leaving with just a week's notice and was probably eager to get gone. I asked for them to transfer their recordings to me, since they were on the cloud and would be hard to recover once Ahhh's account was deactivated. I sent Ahhh detailed instructions how, but they called to insist I walk them through it. Frustrating, but we got the files.
Ahhh's next move just floored me, though.
We have a lot of sensitive information at NerdHaven. No state secrets or anything, but information that has legal ramifications if it makes it into the wild. We have posters all over the halls telling people to be careful about locking their screens, displaying this information only when absolutely necessary for a business purpose, and basically keeping it wayTheHellSecure.
Ahhh mentioned that they had some artifacts to transfer to our network drive and that some of their files contained sensitive information. We'd created a secure directory on our share drive for this kind of stuff, but it was new and Ahhh hadn't been given rights to it. Since they were leaving the company tomorrow, they weren't about to get rights, either. Ahhh had asked us what they should do with the files so they could be put in the secure directory.
I can't remember my exact suggestion, but it was something like 'Hey, ping me when you're ready and you can drop it in the directory next to the secure folder and I'll move it in as soon as you do.'
Ahhh's response was to email the entire department with the sensitive files as an attachment.
Can one of you put these files into the secure directory for me?
It actually took me re-reading their email to believe they'd done something so stupid. They'd actually asked us to put these sensitive files somewhere secure
by sending them to us via unsecured email.
I went and asked everyone in the department to delete (and purge) the offending email and its attachment. I then told Ahhh what they'd done, and told them to do the same.
Reality Check time....
Then I went to our experts in secured information and asked them what to do. They gave me the company policy which read like I needed to go to DEFCON-1. It required an incident report be filed within 24 hours.
Double Reality Check time...
So I went to our in house manager of secure info to ask "Really? Do I really have to do this because of Ahhh's screw up?"
What do you think a manager in charge of security says? They say "Follow the policy. Now."
So I put it in Ahhh's lap.
Hey, Ahhh - I know it's your last day, but you need to fill out this incident report on your data breach. Best wishes and Good Luck!
Honestly, I'd had it. Ahhh did something any of us could have done, but really, they were the ones who brought up the fact that the info was secure to begin with, so their just emailing it was incomprehensible. Odds were, no data was compromised - but policy was policy and I was not going to let their stupid become any more of my problem than it already was.
At the very end of the day - Ahhh sends me an incident report that read like a Nixon presser:
Mistakes were made.
I pass it on to corporate, since if Ahhh won't be available for comment in 10 minutes, and *poof* Ahhh vanishes in a puff of fail.
(Three phone calls with corporate later, they agree that the incident was not a breach, but they are glad we reported it to them, since they had questions about why we were storing files of this nature and perhaps would we be willing to discuss what other kinds of files we were keeping...?)
* * *
That was one small piece of the maelstrom going on in my head now. There were the holidays, loaded with goodness, sloth and gluttony. A week of sleeping in for damn change. Holiday VISA bills, a snowless Christmas and right about the time I'm feeling normal I'm flung into NerdHaven's new year.
There's no way to really sum up the other NerdHaven history, either. Arwafn's broken features had been in Beta for months, and one of our two problems appears to have been solved, but the other was maddeningly stubborn. It involves figuring out the specific location of a person at a given point of time. Our clients were either not sending us this data at all, or were sending it to us at the wrong time, so Arwafn was showing bad data.
The seemingly simple response would be to yell at our clients and say "send us the right data" but this was not an option. There were other ways to get at this data, and we had been commanded by management to develop them. Clients would not be asked to change what they send us. They could not, or would not - and we had no leverage, anyway. We would find this datapoint for them, by leveraging the data clients
were sending us. I'll call this elusive mcguffin PofC.
And it's awful.
(It is also one of those 3 impossible things that Ahhh included in their fail-a-thon story so many months ago. That I've been working with people in three time zones for months to get
an idea of how we could get
part of PofC drives home how inadequate Ahhh's analysis of this element was. "Make Magic." Ugh.)
As it happens, the feature that Ahhh needed PofC for still has not been built, because all of Ahhh's stories were utter crap and imploded as soon as devs looked into them. Dash is now plowing through the feature like a demon and leaving awesome UI in their wake.
Gumby met with our support team about PofC and came up with theory about how we could do it. They passed it to Data and Thespian over on the west coast to do some data analysis on it and lo and behold, it showed some promise. Thespian is one of our database gurus and getting their time is like getting 1 on 1 time with a minor deity. Thespian is humble as hell, and a marvelous person to boot - but getting time on their calendar is intimidating... "Do I really need to bug them...? What if they think what I'm asking them is stupid?"
etc.
But Thespian gives us some good data, and HockeyOne suggests additional analysis that we can do to get a better picture of where we are at. More people get involved. It becomes what Data has always been asking for "a team of people from across the organization." Gumby calls us all together and asks us to present to our SMEs, but we aren't really sure what we have yet. So I pull a smaller group together to beat our data into conclusions we can put before our SMEs for real-zies.
It goes well, and we start hammering out the ever expanding list of details we are going to need to get what amounts to
a very small portion of the PofC datapoint.
It will be enough to get the features we need done and Arwafn will finally be made whole.
Olympus demands it.
Oh, yeah - there was the high altitude drama. Which takes some explaining of its own.
Right before the holidays, we had all kinds of executive turmoil. Our CEO was driven out for unknown reasons (but under a cloud, something to do with not getting Project X ready for market in time), their replacement made the rounds in a bizarrely Orwellian meet-and-greet "What is your favorite thing to do, person who could fire us all in an instant?"
UX was pulled out of the tech wing of NerdHaven and attached to Product. (Which gave me the shivers, since CorpWorld's favorite activity was passing around the unwanted UXers until they cared enough to eliminate them). NerdHaven was being meshed together with a "sister company" in the central time zone, and with Devil's boss leaving, our new Product VP, Remote, became Gumby's new boss.
Remote is nice, but very corporate. Dev background, funny. REALLY hooked on PowerPoint. But I'll give them credit, I didn't hear a lot of bunk when it came to the state of the company. They wanted transparency and honestly both ways. I'm afraid of Remote, but I believe they are not up to anything nefarious. They want things to get better.
Then our GM quit. I liked them a lot, they were plain spoken and fiercely direct - but you believed every word they said. They believed in attracting good people, building a culture of hard work and quality and keeping it that way. I heard via Remote that the GM had serious health problems and were broken up about no longer being able to do the job they loved. Depressing.
Shortly after that, we got more corporate convulsions. Having spent the past six months integrating us with a "sister company" under the big tent of our corporate masters, we would now begin the process of un-integration. Portal explained it to me as "it was a bad call, and now they are realizing that and reversing themselves. It is a net good."
I believe Portal, but it meant that UX would potentially be reporting to yet a different Product exec. As it happened, we got a new Product Actual, who would report to Remote - and everything about Product Actual is encouraging. They have a plan - they are articulate at explaining that plan - and they are letting the air out of a lot of institutional stupid.
NerdHaven is the best UX gig I've ever had, but there is more than an air of WTF with some of the decisions about what we should build next. Above a certain level, everything is politics - and the political class at NerdHaven is unable to grasp that they are not market experts. Historically, we've used SMEs, but they are SMEs of our user workflow (sort of) but they are not market researchers. Product Actual wants competitive research and actual data to decide what we do next.
It's.... refreshing.
Back when Noddy was building his new form of failure, everyone knew it was a doomed feature, because the end of the workflow we were trying to support would not be available for over a year. We could not support that workflow, yet we built the feature anyway, because our SMEs said we had to. Lots of money was spent - a lot was learned that we could use elsewhere, mind you - but Noddy's form was a sack of useless crap.
Product Actual was saying no more of this foolishness - and God bless them for it. I wondered how they would do when the (amazingly headstrong) leader of the SMEs tried to grab the reigns.
The answer was swift in coming - With our ailing GM gone, one of our VPs was elevated to GM - Olympus.
As in, Not Atlas. Olympus.
Olympus is the person responsible for our company olympics and a host of other bonding activities, but they are absolutely not a person to trifle with. Olympus will cut you off at the knees and throw your former limbs overboard. Gumby is absolutely terrified of them.
The same message announcing the ascent of Olympus to GM also includes a postscript that the head of the SMEs is leaving the company. The remaining SMEs will be attached to Product. This is a significant reduction in their standing.
I enjoyed listening to the head of the SME's presentations, they were passionate about their work (they worked on Project X), but I've come to learn more than a few troubling things about their professional ethics. Combined with their grasping political methods and big idea nonsense, I'm convinced their departure is a good thing.
So Olympus is holding the reins now. UX works for Product Actual, who seems awesome and sensible. Gumby is a peer of Product Actual, something they had to clarify, since I'd mistakenly thought Gumby was reporting to Product Actual.
Awkward.
But the truth is, Gumby has been losing political ground of late, and you can tell they are working hard to make that up with effort. I barely see them now outside of department meetings, and truth be told, I've really started to hate those meetings.
Used to be, the UX staff would get together and share what we were working on and set up collaborations that needed to happen. "Hey, you're working on a widget like that? I just made one, we should talk." A lot of camaraderie happened there as well. Good culture, as the former GM would say.
Gumby squashed that. UX meetings are now an agenda sent by Sprint to the team and Gumby reading through it, belaboring each point like they are trying to fill time. Gumby is good people, but they always use several sentences when one would do. It hurts their credibility and I don't know that there is a good way to help them with that. To mention it would be insubordinate, but I wish there was a way to help them. UXDir used to have a hand signal that meant "adequate answer, now stop talking." I wish there were a way to cue the boss when they were making half the room's eyes roll.
A Gumby staff meeting is something to be endured. Administrative procedures, corporate happy talk and.... questions? Moving on.
I haven't spoken to Sprint outside of a meeting in probably two months. It's nuts.
So much has changed. Used to be Runner and I were happily working away on BigDog's team.
I'm off BigDog's team - BigDog is now a manager, so even they are splitting time with their team and other teams.
Runner is hip deep in work with the Dragon team. Dragon is a backend dev team that fears UI work. Runner is big UI, so it's been a struggle. Runner had a huge project and appears to have landed it to the satisfaction of Juice (who is high in Olympus's favor, and now a VP). Runner threaded a series of needles and has every right to be proud.
Red is the newest member of the UX group and they are enthusiastic and very capable. They are on the contract bubble and we're all hoping they get converted to FTE. I wonder what they think of the latest batch of crazy - back when we interviewed them, things were so very different. They seem to fling themselves into the work and do well. They are getting some of Dash's work in the near.
Dash landed a big wedge of new UI that ran up against a brutal timeline spawning a series of bugs in production that made everyone unhappy. I believe this was the result of asking too much by a set date (beginning the death spiral of development) and BigDog's team doing their level best to get everything over the finish line in time. They made it, but will all kinds of asterisks.
Olympus doesn't like asterisks, and there will be lots of recriminations on this one. Dash should be proud, though - their feature is good. Far better than the rest of our other similar features, and it can be a springboard to more success in future.
Heater... I don't know what to think anymore. Noddy was the worst I've ever worked with. After they left, Ahhh was my go-to frustration. With Ahhh gone, the title falls to Heater.
I want to like Heater. They are sympathetic. They are nice, they joke around. I get the impression they want to do good work. They just....don't. Heater is assigned to Dragon, and Dragon is chock full of competent devs and QAs who know their stuff. I used to think Heater would write up stories, get them approved and present them at showcase - same as the rest of UX. With Runner moving to Dragon, I got to hear what was really happening.
Heater starts writing a story... and Dragonman or one of the other Devs or QAs will finish it. At showcase, one of the Devs or QAs will present it. Heater doesn't call clients, doesn't do research, doesn't do....squat.
And I like them, they are likable. But Runner would come to me almost daily, to tell me of yet another incredible thing that Heater did or didn't do. Heater has an amazing ability to forget things - to the point where I honestly fear they have a mild form of dementia. Things that have been ironed out by their team and written down in front of Heater will later be amended by Heater as if nothing had happened. Runner would repeatedly find a finished story of theirs had been rendered unrecognizable by Heater.
Heater is just behind the pace. That they've been on a team as clockwork as Dragon is probably the sole reason that Heater has been able to cope this long.
It's also likely the reason Dragon habitually treats UXers with such contempt. Likable as they may be, Heater is hampering the speed of their team. And the rest of UX is busting their butts while getting blamed for all manner of problems to boot.
Gumby has been feeling the pressure. They have ceded huge political turf in efforts to please Olympus and Juice. Gumby doesn't seem to realize that their favor is fleeting. And you can only give away turf once.
But PofC is turning a corner, BigDog's team is putting an end to the bugs in the last release - things are starting to mend. I can feel it. Right before the holidays, Data let me know they were flying in from the west coast - which is great.
Data and I had a rough start - I was way too slow in appreciating the wider world they live in - but we've finally arrived at a place where we can trust that the other is going to do their level best to help the project. I'm excited to meet them in person.
They are exactly as I expected - a real hoot. We plunge right into PofC work and then Data disappears into an all day meeting that would have me tearing my eyes out. Data's stock is up lately, other people are finally appreciating Data's wider world as well. The future of NerdHaven will rely on things that Data has been telling us about for quite awhile now. It sounds like we will actually start to build the things we need for the future of the company.
Today was UX staff meeting - Data will actually be attending in person. Data has been attached to UX for awhile now, but they report to Portal (they asked to be moved right before Gumby started), so it's a rare thing to have Data in the room with the rest of UX. Sprint is calling in from the west coast, they are sick as a dog and I'm surprised they don't just skip it.
Product Actual is also in town, which is a bit odd. They live five hours to the west, and are usually only in for three days out of the month. These days - they've been here three days out of every week. We start up and I'm briefly embarrassed for Data to have to sit in on how awful our meetings are in person. Data does our meetings over the video phone, but somehow listening to Gumby rattle through the agenda in person seems like more than Data should have to bear.
But today, Gumby is direct and abrupt. They are taking a new position in NerdHaven, they will be doing work in Product - doing work like Devil - and they will report to Product Actual. Their portfolio will include Arwafn and Project X.
There's more - UX will no longer report to Gumby, we will all report directly to Product Actual. Product Actual laughs and tells us that they are
the worst administrator around (my mind immediately flew back to UXDir's lax ways) and I laugh back "
bring it!"
But mostly, we are all shocked. There was no hint of this. I ask if there is still a UX Director, and the answer is no. Gumby is leaving us, and now we are all direct reports to Product Actual.
Oh, and a big wedge of future UX work is going to be done by an external design firm.
And the head of Sales just resigned. And...
This is not CorpWorld - this is NerdHaven - but there is still that sinking feeling.
First the boss leaves, then you get re-assigned, then they start killing off the department.
Last one out...
No. It won't be like that. I have to think that this will be different. Product Actual is smart, practical. They like us. We are respected - most of us anyway. It won't be like that.
It can't be like that.