Tag Archives: STARTUP

Spelunking to uncertainty

Last week I wrote about the major differences between my experience at Dell and my experience here at Infinio.

One of those was the idea that here, there’s no supposition that at least someone, somewhere knows the answer.

That is really, really hard to digest for someone like me.  I have a predisposition to assume that there is an answer to everything.

I shouldn’t think that, I know.  Even my professional training as a mathematician should teach me that isn’t the case – look at how many unsolved problems still exist in math and may forever.  Look at Godel’s incompleteness Theorem.

Or, last week I was at an engineering meeting and the topic of discussion was a terrible little behavior we were seeing in our product’s interaction with another product.  This behavior came up over and over, and while we fixed each instance of the problem, we had no way of knowing that we had addressed every instance of the problem that could arise.

While extensive testing could minimize that risk, it can’t eliminate it entirely.  As one of the engineers said, “There’s no real way to know when software is ‘done’ or ‘right.’”

This feeling has awed me in the past once before as well.  Before babyDiva, mrDiva and I used to travel a lot, and one of our best vacations was to Belize.  We had planned to hike ATM, a well known cave-system in the Cayo district, but the rains had been so intense that it was un-navigable.

Disappointed, we went to our hosts who said, “Oh, let’s call Ken!  You can go see Ken’s cave.”

 

mrDiva, our guide Leo, and Ken, with Ken's 1979 Land Rover

mrDiva, our guide Leo, & Ken, with his 1979 Land Rover

Ken’s cave, it turned out, was amazing.  Known more formally as Achtun Chapat, it was only accessible by a bumpy ride in the back of Ken’s 197X Land Rover.  He and his guide led us through a 5-6 hour hike into the cave system, pointing out bats, bones, and pottery shards as we went.  There were cathedral height ceilings and crawl spaces.  Beautiful stalactites and stalagmites.  It was pitch black when we turned off our headlamps.  Like, literally black.  At the end of the cave, we sat under a sinkhole that provided some sunlight from above and enjoyed Ken’s wife’s homemade burritos.

As we were sitting, Ken mentioned casually that this was one path, but they hadn’t mapped the entire cave yet.  There were probably 100’s of additional yards of cave that nobody had yet traversed, because of safety issues – low oxygen rates and unpredictable lakes.

It was inconceivable to me.  This cave was obviously a national treasure for Belize, at least as complex and rich in archeological and natural items many of the well-known sites in Central America.  How could they not have mapped it out?  Aren’t there X-rays or robots or something that could do this?

mrDiva and me at the entrance to Achtun Chapat

mrDiva and me, at the entrance to Achtun Chapat

But there aren’t.  Or they’re not economically or practically viable in Belize.  Or Belize chooses not to explore this for fear of losing control of their resources.

Whatever the reason, I am still overwhelmed by the idea that there’s a cave that I have been in that is only sort of understood.

Sometimes, we just don’t know the answer.

 

3 things that have changed at work

After my very early impressions of Infinio, I’ve tried not to overthink the transition.  I’ve had moments of reflection here and there, but being prone to over-analysis I’ve tried to be “in the moment” here.

Recently, however, a handful of themes have continually appeared in my everyday work that I want to share.  My life at Dell was *so* different from my life here.

In my decision to come to Infinio, one of the most important conversations I had was with Matt Brender, who had recently made a similar transition from EMC.  In fact, when I interviewed at Infinio, my now-manager Carrie quoted to me from his blog:

At EMC you first assume there is a process.

At Infinio, you start confident there isn’t one yet.

Here’s his entire post on his transition to Infinio.

Anyway, back to ME.  Here’s what was different when I was at Dell:

1.  I (mostly) stuck to my quarterly plan.

At Dell, I’d propose a 3-month content plan for my team, negotiate with them on it, negotiate with my management on it, and usually by week 2 or 3 of the quarter, we’d have agreement.  I was measured on (and great at) how well I delivered that which I committed to.  Sure, we kept some slack in the plan for unexpected projects, but that was the exception, not the rule.

In fact, if anything major came up, more than a few days of work, we’d go to the work plan and decide what was getting pushed to the next quarter.  We’d let the stakeholders for the different projects fight it out about whose we tackled.

This is not to say that we didn’t work hard and try to overdeliver on our plan. We often would work late to meet a deadline or otherwise do things that otherwise seemed impossible.

But there was a language and a process around how we handled additional workload throughout the quarter, and in fact navigating that is one of the major skills managers at Dell acquire and use.

Is that different at Infinio!!

We did create a quarterly marketing/content plan this quarter, and I’m told it’s the first time we’ve done it at this level of detail.  However, two weeks later, I’m looking at my plan nostalgically as I would a homework assignment list of mine from high school.

It’s not that I don’t need to do those things, but in the span of just a few weeks, so much changes with respect to prioritization and opportunities that it seems outdated very quickly.

And as new things come up, there’s no negotiation on what doesn’t get done.  It’s more like triage – “well, I’ll have to delay creating that training module so I can get us certified before this show we just decided to do,” but that doesn’t mean delaying until I next get to write a quarterly plan, it just means something jumps the queue.  All the work still has to get done.

 

2. I didn’t do a lot of guessing.  

For example, when we launched a new product, we knew what resources we needed to support it. Sure, we may not always have known exactly what claims would resonate best with customers (or what results we could achieve in the lab) but we knew we needed claims and there was a process to get them.  We often felt understaffed and under-resourced, but the reality was that we had teams of people dedicated to various different aspects of the marketing for a launch, a refresh, and sustaining operations.

There was no concept of someone at Dell not knowing the answer.  That person may not have been in the meeting or in the room, but you could ask and someone would have an opinion which was determined to be “The Answer.”  The job of being a manager at Dell was very much about executing within the system, escalating uncertainty, and decision-making within a pre-defined structure.

At Infinio, I think the phrase I hear most often is, “I’m not sure, let’s try it.”  Everyone from our executive team on down talks about A/B tests, experiments, learning, and mistakes, nearly every day.

This isn’t to minimize the experience of the leadership team here or the employees – it’s an amazing group of people from Endeca, vKernel, EqualLogic, NetApp, and other name brands.  Many of them have built a company before.

But we are in a new market selling something that is very disruptive – and there’s no codified “right way” to do that.  Inbound marketing is still an adolescent.

We just don’t know the answer sometimes.

Back to the discussion on priorities, often during my weekly meeting with Carrie, I’ll bring a list of the new tasks I’ve accrued during the week.  We’ll look at it along with my plan.  “Should I do the content for this project or create the materials for this project,” I’ll ask.  And we’ll consider both, without knowing the “right” answer.

 

3. At Dell, I was detached from the minutiae

At Dell, I was light years away from lots of daily decisions.  If I staffed a tradeshow, I basically just showed up with the right polo shirt on.  For Dell Storage Forum, I was a little more involved in things like T-shirt slogans and activities, but mostly I just knew about them early, I didn’t create them.

In contrast, the number of details that come across my desk as part of a 5-person marketing team is incredibly high.  What should the booth graphics look like for Citrix Synergy?  What should our giveaway be?  Is this close enough to our “blue”?  Is the text in this ad centered right?  With which vendors should we split our lead gen spend?  With whom do we syndicate which content?

It’s an amazing education.

All of it is an amazing education.

(It’s also exhausting!)

Three meetings that didn’t suck

“If you had to identify, in one word, the reason why the human race has not achieved, and never will achieve, its full potential, that word would be ‘meetings.’  (Dave Barry)”

One of the things I’ve noticed as I’ve adjusted to life here at Infinio is that we have different types of meetings than I am used to from being at a big company.

First off, we have a lot more ad-hoc meetings.  Perhaps due to the open floor plan, it’s far more common to mosey over to someone’s desk and start chatting rather than to schedule time with someone.  “Can I grab you for a sec?” “Are you interruptible?” are very common here.

Twice a week I participate in a marketing “stand up” meeting.  I remember reading about these in grad school as part of Agile/Scrum methodology, although not really related to marketing.  In ours, we go “around the horn” and everyone does a quick update of their major goals for the day.  Sometimes we have a short conversation about something or show a piece of work off, but usually it’s just to set up for the day.  Oh, and it’s called a “stand up” meeting because we literally “stand up.”  That keeps it nice and short.

Last Friday I went to my first engineering iteration meeting.  I am such a dork – I was really (*really*) excited to attend.  Engineering at my last job was not a resource directly accessible to me so it was exciting to see what happens in one of their meetings.  Basically, the engineers took turns talking about their work on particular features or problems, with at least 6-8 of them talking in a 2 hour meeting.  People asked questions and expressed worries, and there was a lot of sharing of images and screen shots.  We used Google Hangouts to connect to remote engineers so the graphics were definitely important.

I learned a few specific things at the meeting.

1.  Despite being warned that I might be bored I was pretty well-equipped to follow most of what was going on in the meeting.  With the exception of some coding buzzwords, the bulk of the things I didn’t understand had more to do with my gaps in knowledge around VMware than anything else.

2. The relationship between engineering and QA is fascinating – like siblings maybe?  Everyone wants to release a great working product but it’s QA’s job to poke holes in the code before it ships.  (Nudge, nudge, poke, poke, I’m not touching you….)  The groups were friendly and respectful towards each other.

3. Regarding language – I was impressed by how many times “the customer” was referenced (17) and how actively they seemed to be a silent participant in the meeting.  Specific customers were also mentioned and resolving their issues was clearly top priority. There was also some reference to “technical risk” and “technical debt” which were new concepts to me.

4. Finally, I understood – immediately, in a flash – what automation testing is and why it’s so important.  Suddenly, too, I understood what “DevOps” meant.   And I’m not sure either of those things would have made any sense if I hadn’t attended that meeting.

The other new kind of meeting I have begun attending since joining Infinio is the weekly all-company meeting.  After our company lunch on Wednesdays, our execs all get up and talk about what’s going on in their domains – Engineering, Sales, Marketing, and our CEO.  They share good news and bad news and major strategic decision-making.

It was really fascinating to see the engineerings ask about marketing programs and plans – it reminded me that you can’t just wake up one morning and decide to do marketing well any more than you can wake up and decide to do engineering well.  I forget that sometimes – even my own biases work against the field I’ve chosen to work in.  The other cool thing about the all-company meeting is what happens afterwards – people walk over to each other and follow up on things they heard.  It’s another good way to get engineering, sales, and marketing talking.  A test engineer came over to me to comment on some market research I was doing because he had worked at one of the companies whose technology I was researching.  Score!

I like meetings that don’t suck.  I hope to attend more of them.

Eavesdropping

I have a confession to make: I’ve been eavesdropping.  Not like the NSA kind of eavesdropping, but the kind that happens organically when you work at a startup that has an open seating plan.

When I started at Infinio, I thought I’d hate the open floor plan.  No offices, no cubes, no half-wall separators.  I really liked the team and the product, and most of the other startups I interviewed at had a similar layout, so I figured I’d have to just deal with it.  But as it turns out, I’m reaping all the advertised benefits.

My desk is next to the alcove where the salespeople sit – so I can lean a little to the left and clearly hear their conversations with customers – I hear what questions they are asking, what questions they are answering, and if our MQLs are well-Q’d.2014-03-13 09-28-24-438.jpg

If I pay attention to the reflection in my monitor, I can tell when our SEs (@mjbrender and @jklick) are whiteboarding something interesting behind me and I can roll my chair over to crash that conversation.  Last week I caught one on write caching – very helpful.

Just yesterday we had a customer issue during an installation and I watched and listened as Sales, Support, and QA negotiated among themselves as to how best handle the issue.  (And by Sales, Support and QA, I mean about 5 people total.)  At my last company that would have been a 20-person conference call that would have taken several hours to organize.

Over my right shoulder is the strangest co-worker I have: a telepresence robot – no, seriously – who is our Director of Product Management (@peter123).  He’s always available, and people tell me it’s easy to forget he’s remote after a while.  [Fun fact: during the interview process, I met him as a robot before I met him as a person.]  You can sort of see him in the shadows on the far left of the photo.

So I’m learning a lot from listening and inserting myself.  Another benefit is a complete lack of any personal conversations.  I don’t mean that we don’t talk about our lives outside work – we do – but without the illusion of privacy that a cubicle offers, there’s no inclination to have a protracted personal phone conversation in the middle of the office.

The other benefit is that people eavesdrop on me.  I’m getting used the “oh, are you guys talking about X?” “oh, is that the new Y?”  A few times, someone has come over to offer some information or ideas and it’s stuff I wouldn’t have thought of from someone I wouldn’t have thought to ask.

I’m not sure how this can scale as the company gets bigger – or how you would replicate the value of it in a large company, but I’m definitely getting a lot out of it for now.

CREATE TABLESPACE Blog

I’m glad you found yourself here.

You may know me (and some of this) from Twitter, but to level-set: At the end of January, I left my job in solutions marketing at Dell after 7 years.

kendallAfter a short hiatus, I joined Infinio Systems – a software startup in Kendall Square – as Director of Product Marketing.  There is so much to digest and learn, and there’s no way to share the experience in 140 character chunks.  So here I am in the blogosphere.

So why name my blog “storageDiva’s Tablespace”?  Two reasons:

A tablespace is the abstraction layer in a database that sits between the logic of the database and the physical datafiles it contains.  Basically, you group several tables and indices together and while they are physically stored in datafiles, the collection of them (regardless of physical location) is a tablespace.

I like the metaphor of this blog being a tablespace of interrelated tables, because I plan to share all sorts of interrelated ideas about my experiences in technology, marketing, and life at a startup.  Here’s a swag at what I think the “tables” would be called: 

  • LEARNING: My education around caching, performance, and all things Infinio
  • CUSTOMERS: What I learn from our customers and our not-customers
  • TECH: Thoughts and ideas about our product and the industry at large
  • MARKETING: How product marketing is changing in the Internet/Social Era
  • STARTUP: Life at a startup, especially after coming from a big company
  • XX: What it’s like to be a woman working in technology
  • HOME: Balancing my work life with my daughter(“babyDiva”) and spouse (“mrDiva”, also at a startup)

I said there were two reasons for the blog being called “storageDiva’s Tablespace.”  The second reason comes from Sheryl Sandberg.  In her book and TED talk she relates a story of being at a meeting and notices that the young women are sitting on the periphery of the room while the men all sit at the table.  She urges the women (and the reader/watcher) to claim a seat at the table (not behind it) to ensure their voice is heard.

The phrase “table space” is a reminder to myself that I have gotten where I am by always claiming my space at the table, long before the other Sheryl made it trendy.

I hope you’ll stick around.