I'm neck deep in a government spreadsheet from hell. A regulatory data barf, courtesy of one of the brighter corners in our bureaucracy. NerdHaven's app has to be in synch with the valueset in one of this spreadsheet's many worksheets.
The spreadsheet details how our 2000 plus data elements have changed this year. Each element has four values, each could have changed. Some elements have ALL four of their values change.
Also, the spreadsheet does not separate the old values and the new values. If a field has changed from
Old Footo
New Foothe value's cell is written as
Which makes me want to stab someone.OldNew Foo
Oh, and there's no primary key. Because: of course.
Some elements are being replaced by new elements that are being added this year. And they are adding over 1,400 elements this year. It is my job to detail all the field changes for the devs, spell out the 1,400 new values (and look up an additional value from outside references so these new values won't break our other features that rely on this fifth field), list the elements that will be made inactive, and list which inactive elements will be replaced by other elements.
It is soul crushing work. A person with better programming chops would probably be able to slice and dice the file better than I did. Faster. I do all the Excel-fu I can think of and it takes me almost two weeks. I don't know how the QA effort will start, and I already feel sorry for whoever pulls QA duty on this gig.
* * *
Whales... think about the whales...
* * *
I'm getting this work done in support of a feature called RuRa. Well, actually just the Ra portion of RuRa. Sprint's been working the Ru portion and has been wading through all kinds of data hell to build the feature in compliance with what the government demands. NerdHaven's app aggregates data from clients and gives it back in useful ways. Since client data varies (sometimes dramatically) building features with hard data requirements is...challenging.
Sprint has been getting it done. They work with Data in our west coast office, and Data is borderline OCD when it comes to getting the business intelligence right. Together with Pirate & Thespian, Sprint was well positioned to land this beast.
But I can tell Sprint has hated most of the project. Gumby has been hands off in the past, but deadlines are approaching and they cannot help themselves. Weekly checkins, over the shoulder advice, and lots of emails ending with "Thoughts?" I think Gumby had made a deliberate effort to back off at the beginning. Sprint has a reputation for efficiency and professionalism, I know Gumby had wanted to respect that. But where Sprint is known for being fiercely independent, Gumby is positively clingy.
It is a bad mix.
Sprint chafes under Gumby's endless questions and meddling - Gumby is irritated by the feeling of being left out of the loop. When Gumby is called to account by higher ups (the thing Gumby fears above all) they don't have the answers. Each complains to me about the other, and while I sympathize with both - my head is with Sprint. Gumby has stayed away for too long and is overcorrecting.
Talking with Gumby, I am struck by how little they know about the Ru project. They are the Project Manager and design elements I've known about for months are new information to them. I have spent very little time with Sprint about Ru, because very little of it affects my Ra project - but by simple osmosis, I've managed to keep current. Gumby? They know the regulations, but not the design. Which gives them enough information to drive Sprint up a wall with "What about this?" questions, week after week.
With most of the Ru feature built, Sprint is spooling up to put the feature into Beta. I'm head down on Ra and its looming deadlines when I start getting invited to Ru beta sessions. On these, I'm absolutely clueless. I don't know the setup requirements or the goals for the session. I wanted to be a fly on the wall for these - and I'm glad Sprint's invited me - so I can watch the Ru feature in action. It has nearly identical UI to Ra, so lessons learned in the Ru Beta will help my design work.
Which is why it seems odd that I get an invite from a rep to participate in an Ru beta session with Gumby. Sprint is not in the invite. Which I think nothing of, because Sprint is absolutely going to be there, it's their project. But I replay to the rep and say "Sprint's driving the bus on this," basically to say 'hey, don't expect me to do much in this one, I'm an observer."
But later, I'm on IM with Sprint and find out that no, in fact, Sprint has not been invited into the Ru beta. Which makes absolutely no sense. I forward my invite to Sprint and ask Gumby about it. It ends up with Sprint being invited and running the session, but something was seriously odd.
Shortly after that I was in a meeting with Gumby where I was asked about taking a larger role in the Ru betas. Which I said I was fine with, but made it clear that this was Sprint's show if they wanted it. If Sprint wanted out, I'd be happy to help - but I wasn't going to waltz into their beta uninvited.
This was all kinds of awkward. Gumby used to be my boss, and now they were the project manager for both Sprint's Ru feature and my Ra feature. They do get a say in lots of things that affect these features. but if they want a personnel change, they need to take it up with Product Actual. I don't get a say, hell, Sprint doesn't get a say either. If Product Actual says "you do this work," that's what we do. Gumby asking me to budge into Sprint's beta smells bad. We end the meeting with me reiterating that I'll help Sprint if that's what Sprint wants, but that's about it.
About a week later, Gumby, Sprint and I are in a meeting where Gumby asks the two of us who will be running the Ru betas. I clam up and let Sprint answer, and I get a pointed look from Gumby when I do. Sprint (who I think was surprised by the question) takes a moment to spool up, but answers that they will continue to run the Ru beta. Which is a relief to me. Sprint knows their stuff, and if they wanted out I would worry why.
Sprint was recently given a horrid project I'll call Notables. And if ever there was a project that would make you clear the decks, its this one. Sprint did 20 rounds with it early in their NerdHaven tenure, and any mention of it causes groans from pretty much anyone in the know. Project Actual had asked me to help out on it weeks before, but changed their mind and gave it to Sprint.
While I was genuinely relieved, I was too ignorant about how bad Notables was to appreciate the bullet I'd dodged. Sprint knew better - and I was afraid they would have to bail out of Ru to focus on this new beast. But Sprint was up for Ru and Notables - which meant that they were their old self. Kicking butt and getting it done, challenges be damned.
With the Ru beta thing settled, I tied down the spreadsheet work and beat it to death with a shovel. Then started slogging through the pile of Ra work I'd pretty much been ignoring. This one piece of the project was just a mental block, and I'd been working around the edges for a month. With the spreadsheet work done, suddenly I could find a way through. In about a week, I had the bulk of my Ra work slotted for technical review, the last step before RFD. I was on fire.
* * *
A Monday.
I meet TierI (our ace customer rep) in the breakroom to discuss caffeine addiction. Then clock through some shop talk with the devs. I gotta get some input from Red on something and we're in the middle of talking when I get a text.
It's from Product Actual:
Hi. Can you come find me when you have a minute?Uhhhh...
I must have been in a total fog at the time, because my only thought at the time was, I wonder if they are in the old product office? Product Actual is based out of state an only comes into our office every few weeks ago. When they do, they use the old product office.
See what I mean? A total fog.
Not: Hey, I wonder why Product Actual is town?
Not: The boss is asking to meet with me out of the blue, wonder why?
Nada.
I just marched off towards the old product office.
When they asked me to close the door is when it hit me. Uhhh...
Again, though - the first thing in my head was: I'm betting that the Ra project is getting benched. All that work is going in the crapper.
Product Actual never beats around the bush. One of the things I really like about them. You get the real from Actual.
"This is going to be another one of those bad days."
!!! There is a second to absorb this, and the sinking feeling starts.
"I've had to lay off Gumby. There will be others in this office getting RIFed."
(RIF. Reduction In Force. Yet another acronym for firing people.)
"The west coast office will not have its lease renewed. All the west coast staff will be offered the opportunity to work remotely."
Actual tells me that no one else in UX group is affected. But (per policy) there will be no formal list of those affected.
Yet again, NerdHaven staff will walk the halls trying to figure out who is here and who is gone.
Not at their desk. RIFed? or PTO?
Sprint is safe- and when I get a hold of them they tell me that the west coast office's only QA resource had resigned that morning. The west coast office staff had been savaged in the last RIF, now they were thinned again. Oh, and their office would close in May.
Sprint sounded absolutely gutted.
There's really no way to end those kinds of conversations. We sign off with the obvious promise: Let me know if you hear anything definite.
And then you walk back through the office in slo mo. You want to check in with your favorite people, see if they're okay - but you don't dare linger. HockeyOne isn't at their desk, HockeyTwo was let go in the last bloodletting. No way they got rid of HockeyOne.
Metrics is not at their desk, but you know they were out on PTO. Right? And just like that, you're unsure again. I try the CorpWorld method from Black Wednesday, but our IT isn't as draconian, so email status is no help. I try IM.
Gumby offline update is the marker for when heads had started to roll. Anyone offline with a similar timestamp is a possibility: a quick scan shows SpecialK, Branding, Cure, and...TierI.
Somehow I know that TierI is on the list, but it is a total shock all the same. TierI was one of the folks who seemed to come with the place. Easygoing with the clients, reasonable, funny...
Can't be.
Data pings me and we compare notes. They know about a person in contracts on the west coast. I tell them about two sales people I've heard of. I don't want to spread rumors, so only the stuff I know gets passed. I'm all but certain about TierI, but I don't say anything - I could be wrong.
* * *
Olympus holds an all staff meeting to lay out the situation. One staffer asks the obvious question: Are we going to do this again in the next three months? Olympus says the same thing they said last time: "We don't plan on having to do this again." Which leaves everyone unsatisfied. But really, what can Olympus say? "I swear on a stack of all that is holy that we will not have another RIF this year - unless the situation changes."
* * *
The week after, some of the casualties are known.
In our project tracking software, former employees still display on historical documents, but with a suffix indicating their status:
TierI [x] InactiveSpecialK and the Cure are safe. HockeyOne and Metrics are okay as well. Oh, thank God.
Branding [x] Inactive
Epro [x] Inactive
...
Morale is absolutely in the sh!tter. Everyone is fed up. NerdHaven had just had our company outing (which I'd missed) - which is usually a good time with good food. Not two days after a team building exercise, we do layoffs. Genius, that.
I'm trying to nail down all the work for the Ru project prior to going on vacation. Actual wanted Sprint to focus on Notables, so I was given the remainder of Sprint's Ru and the beta. Sprint was behind it, or at least being a professional about being asked to focus on Notables full time. With Gumby gone, what they'd wanted has come to pass anyway - for totally different reasons. Sprint will ride shotgun until they're sure I'm not going to faceplant - then dive into the unholy mess that is Notables.
The vacation is a hell of a thing - going off to Alaska to see glaciers and whales. Should be freaking awesome - assuming I live long enough to get packed and get my sh!t together enough to leave.
Mom is in town, fretting about all the details and basically taking over all the work E and I are too frazzled to do. I literally don't know how we would have gotten the kids ready to travel without her.
I'm trying to squeeze runs to the store into my newly freed lunch hours when I get what looks like a meeting reminder on my phone. It's a 1:1 with Actual.
Not good.
But then I'm like - Wait, our regular 1:1s keep getting rescheduled. This is just Actual finding a time that works for-
BUZZZZZ!
It's a text. From Sprint.
Hey thereI'm in the parking lot at Target. Full sun, struggling to see the screen, but I don't need to read it.
Sprint is leaving.
They ask if I've spoken to Actual yet. Which is all but confirmation of...
I just resignedI'm in the middle of the street and stand there blocking traffic. Seeing those words means there is no escape. This is happening. The best UXer we have at NerdHaven has finally had it.
I get honked back to reality by some helpful man in a truck. Sprint gave notice, so they'll leave two days after I go out on vacation. They've got every reason to go. They're getting a job at a big firm where UXDir went (but not working for them). Gumby drove Sprint up a wall, a bunch of their friends were let go, then they were given Notables... I mean, if you weren't looking after the layoffs, you'd have to be out of your mind. Sprint hung in longer than most anyone would have.
I say what I can manage, but there's really no way to cover it. Sprint was a class act, the person who made things get done on the west coast - oh, and they were a great person to work with.
How did we get here?
When I joined NerdHaven, UX was eight: UXDir, The Professor, Data, Heater, Noddy, Sprint, Runner and me.
Today, Sprint handed over their meetings in Outlook, so we could keep the same room reservations. One of them was the UX team meeting.
Data still works at NerdHaven, but left the UX group, so here's the invite list:
- Red
- Dash
- murph
* * *
So, over a week ago, I found a bug. It's part of an addition to Arwafn that Gumby prioritized to fill dev capacity. It wasn't supposed to be in the release, and now it's blown up into three more bugs two days before a software release. A junior dev screwed the pooch, gave their work to a junior QA who did the same, and now we are faced with the damning choice of rescheduling the release or shipping a broken feature.
I have client meetings to set up for beta - I have to do knowledge transfer to Red re my Ru work in case it comes up while I'm out.
I have no time to give Sprint a proper sendoff, I'm barely packed, my signature project is back in the ditch, and I'm flailing to just get a list of what I need to do before I go. There's no chance it will actually get done - I just need to have some hope of tracking it for when I get back, or if someone has questions while I'm out.
So.
Effing.
Done.
* * *
But I'll get to see whales...
Despite having had f*%k all to do with this, they've gotta fix all this.
I hope they are up to it.
No comments:
Post a Comment