Categories
customer success leadership work

The Speedy Scale-Up

Someone recently reached out to me with the following query and I thought it would make good blog fodder since I haven’t blogged in ages.

Their Question:

I’m currently in the throes of planning for 2022 and I’ve hit a few roadblocks on items I haven’t had to do before:
1- Hiring people, but not having enough applicants to the role (seems to be a widespread issue though)
2- Thinking ahead to what infrastructure I need to have in place to grow from 5 >10 >15 >20 over the next year

My Answer:

Yes #1 is a widespread issue right now!

I am the Global Head of CX at Humio. Before Humio, I built out support and success at Nylas, and before that I did the same at Shortcut (fka Clubhouse).

From my humble experience, these are all great things to be thinking about ahead of time!

Hmmm, here is what I’d say just off the top of my head.

  • Build out your org chart ahead of time and hire good deputies before you hire too many ICs.
  • Give the deputies some headcount out of the gate so they can build their own team.
  • Promote the strong ICs to managers and be ready to coach them (and/or have the deputies coach them).
  • Focus on having your direct reports be no more than Bezos’s 2-pizza box team.
  • Plan to do skip levels at least once quarterly so the people that report to your directs can give you the view from where they are sitting. It really helps with overall team cohesion — especially as you start to manage managers — and it gives people a view of what is coming down the pipe from senior leadership and/or the board or investors.
  • Keep in mind that you still need time to manage up to leadership. So delegate, delegate, delegate so you have time to carry out all the random little tasks that will pop up outta nowhere (because Tha Leaders always come into your DMs with that stuff!)

The other thing I didn’t mention that comes to mind now is this:

  • Take breaks and time off! If your company has unlimited vacation, really just treat yourself to days off randomly when you need them or even before you really need them. You will hopefully come back better off for it. And if you’ve delegated like I told you too, you won’t come back to a mountain of work.
Categories
customer success leadership

Old Customer Care Lady Sayings

As a leader in customer care, over the years I have developed a few sayings that I believe have held me in good stead.

Camille’s Top Three Customer Care Sayings

#1: No Special Snowflakes

To My Fellow Caffeine-Fuelled Zombies: The Special Snowflake Paradox

This means that –as much as possible — we want to avoid having to support custom features, special builds, weird bespoke SLAs, and anything else that is going to be hard to track and resolve. Specialness is frustrating to handle and an impediment to scale. If we are running a tiny neighborhood cupcake shop, fine, I am happy to handcraft cupcakes. If we are trying to build a mega cupcake conglomerate, it needs to come off the conveyor belt the same as the others. I tend to say this to sales people and occasionally to overzealous engineers.

#2: Keep Receipts

In your career and in your day to day work, a lot of information goes flying back and forth and it can be hard to track across public Slack channels, private Slack channels, DMs, emails, Google Docs, Zoom calls and so and so forth. When in doubt (and you should mostly just STAY in doubt), write things down, have other people write them down to you, record things, screenshot things.
You will forget.
People will forget.
People will pretend they forgot.
People will try to reinvent the wheel.
People will try to rewrite history based on their faulty memories or wishful thinking.
Keep receipts to remind them (and yourself!) of the good things, the bad things, the mistakes, and the almost-forgotten strokes of genius.

#3: Reduce information asymmetry

I wrote about this here and it is a brief read, but the tl;dr isI this:

If you know something that the customer should know, tell them right away. It will give them some information to gather OR help them set expectations on their side OR prompt them to fashion a workaround. They might not be happy about what you tell them, but at least they won’t be sitting idle wondering if you forgot about them and their problem.


What about you? What are some of your favorite sayings or rules of thumb?

Categories
customer success leadership

Reducing Information Asymmetry in Customer Care

As a customer care person, you are placed at an important vantage point between the company and the customer. You (should) have visibility into the product and people in your company beyond what your customers currently knows/can see. You are there to solve problems for the customer using both information that may already be publicly available to the customer as well as information that is not.

If you know something that the customer should know, tell them. Tell them as soon as you know. If time is running down on an SLA and you are still waiting on an answer from Engineering, find a nice way to tell them that (the phrase “I have escalated this matter to our Engineering team” works). If you are investigating something specific, tell the customer what you think might be the issue. If you need them to provide you with more information from their end, ask them right away so they know the ball is in their court.

I can’t count how many times I have seen a support ticket with numerous back-and-forth internal notes in it and no response to the customer. Things are obviously happening. Ideas are being shared. Surely there is something there we can tell the customer.

If it is a question between providing what you think is a perfect answer and speed, choose speed.
If it is a question between providing what you think is a perfect answer and providing context, choose context.
If it is a question between assuming something or asking the customer, ask the customer.

You are the customers’ eyes in the company, let them see.
You are the customers’ ears in the company, let them hear.
You are the customers’ voices in the company, speak up for them….. and to them.

Categories
customer success tech work

My 3 Favorite Tools (Right Now) for Working With My Geographically-Distributed Team

I recently started a new job where I am working from home with a team spread across Europe and the US. Some of the team is working from home because they always do, others are working from home due to the pandemic, but yet others are actually working as per normal from our company’s headquarters.

With a team spread across so many geos as well as work configurations, I prefer the term geographically-distributed to remote, since that better describes what we are. And while we definitely use the typical collaboration tools (e.g. Slack, Zoom) to connect us, there are a few others I also really like when working this way.

Clubhouse

Clubhouse is a great project management tool in the sweet spot between Jira and Trello. (Full disclosure: I used to work at Clubhouse and am still a shareholder. But, seriously, if I didn’t love it, I wouldn’t mention it. ) When my company was mostly just team members colocated at the HQ, they would track their tasks on a physical whiteboard. In fact when I started here a few weeks ago, I remember someone in the office taking a picture of the board and dropping it into a Slack channel so those working from home could see it. However, with all this uncertainty and people working in and out of offices, that simply can’t do anymore.

So several teams have been using GitHub Issues, while my team and several others have started using Clubhouse. I have introduced Clubhouse at every startup I’ve worked at since I left Clubhouse and it has been a hit with the teams. We can communicate in the comments and threads, create filtered views for specific teams or efforts, and the ability to have cross-team views and higher levels of abstraction beyond tasks is such a win.

My favorite thing, however, is the daily summary notification email.

The Clubhouse Daily Summary (beautifully redacted by me)

At a glance, I can see everything that got touched, created, completed. It is nice to wake up every morning and get a full situation report. The more people in the company are using it, the clearer that image becomes. It is a great time saver.

Clubhouse also has a handy app and a great Slack integration.

Geekbot

With a team this spread out, a lot of important things can happen long before some teammates even wake up. In order to keep people on the same page since we aren’t all in the same timezone, we use this handy Slack app.

With two simple questions (that the Geekbot is programmed to ask at the *end* of the person’s workday), we can share a lot of details and easily pass the baton” from east to west without having to do a boring daily standup either late or night or before we’ve gotten out of our jammies!

Loom

Long before the pandemic, I shared my hesitation about working from home (click to read if you missed that one). One of the things I most miss about working together with people in a colocated office (aside from free lunches, coffees, and team singalongs LOL) is being able to just look over someone’s shoulder at their screen as they explained something to you.

In order to approximate this, I’ve been using Loom a lot. It is an easy way to show someone something without being in the same place or having to set up a Zoom call. Because we all surely have extreme Zoom fatigue. When you wanna try and avoid a Zoom, try a Loom!

Categories
customer success leadership

Support Night School Podcast

I started a podcast about how to get into tech support with my amazing friends Nicole and Brianne. It’s short and informative and part of a limited series. Click the screenshot above to check it out!

Categories
conferences customer success leadership

May 2020 Lead Dev AMA

AMA_Camille

In case you missed it, here is everything I said in my Lead Dev AMA the other day

Categories
conferences customer success tech

Making Them Pay: Tales from the Immutable Stack

This is pretty much the entire text from the talk I delivered at Paymentsfn 2018 on May 24, 2018 in Durham, North Carolina.

Edgar Allen Poe - The Gold Bug

In his story The Mystery of Marie Rogêt, Edgar Allan Poe wrote

“Experience has shown, and a true philosophy will always show, that a vast, perhaps the larger, portion of truth arises from the seemingly irrelevant.”

And it is in that spirit that I lend another perspective, voice, and beating heart in the hope of unearthing some more truth around payment technology.

While it may seem like we in the tech world don’t share much with a 19th century poet, I’d like to tell you a story.

the-gold-bug-cover

In 1843, Edgar Allan Poe’s story The Gold Bug was published, which ended being the most popular and lucrative work he released during his lifetime.

Most of you have likely never heard of it. You’re probably familiar with The Raven or The Tell Tale Heart, but probably not The Gold Bug.

However, it was this story that won him a whopping $100 at the time ($100 being the equivalent of a little over $3000 today), which was the total winnings from a short story contest held by The Dollar Paper, a Philadelphia-based publication of the day.

Edgar Allan Poe was actually was one of the first American authors to actually attempt to make a living purely through writing and as the headline of this blogpost indicates, he wasn’t very good at it.

broke-freelancer
link to read

Unfortunately, Poe was the son of two actors. His father abandoned the family not long after Poe was born and his mother tragically died when he was just about a year old. An orphan, he was taken in by a wealthy merchant one John Allan who had young Edgar Poe baptized Edgar Allan Poe.

While a student at the University of Virginia, Poe repeatedly gambled away money meant for tuition and school supplies and eventually dropped out. This lead to him becoming estranged from his foster father Mr. Allan. Additional quarrels with Allan — who was rich and extremely adulterous— lead Poe to be disowned by Allan and excluded from the will.

So no trust fund. No parents or foster parents to fall back on. Poe had just a pen, a vivid imagination, and dogged persistence.

telltale

So The Tell Tale Heart was published before The Gold Bug in January of 1943 and Poe was reportedly paid $10 for it.

The-Raven-manuscript-cropped

His poem The Raven published in 1845 came on the heels of The Gold Bug’s success. However Poe was paid only $9 for it.
It was The Gold-Bug that drew standing room-only crowds to Poe’s lectures and  gained him fans across the globe in places as France, Russia, and Japan.

In fact , he was actually paid twice for the story. First $52 by Graham’s Magazine a periodical for which he served as an editor but then he heard about the Dollar Paper’s contest and withdrew the piece from Graham’s — notably never returning that initial $52 to Mr. Graham, mind you.

I don’t begrudge you if you’ve never heard of The Gold Bug. To be honest, I’d never heard of it either before I sat down to write this talk. Having read it,  I can’t necessarily recommend as it is to— put it bluntly–kinda racist. Without excusing racism, I do think the kernel of this story and Poe’s story more generally is useful in illustrating a central point I’d like to make.

THE STORY

In The Gold-Bug, an unnamed narrator travels to meet with an old friend, one William Legrand, who lives on an island near Charleston, South Carolina. Legrand is sort of an eccentric prodigal son type who is full of endless fanciful sort of get rich quick schemes.

So when our narrator arrives, LeGrand and his companion, a freed yet still in servitude black man called Jupiter explain, that while wandering through the woods they came across a live beetle that they believe was somehow made of solid gold.

Our narrator listens politely to the story and then slowly heads back home to Charleston never actually laying eyes on this gold bug since Legrand had curiously lent it out to a friend.

A month later Jupiter comes to the door of our narrator and beckons him to return to the island. LeGrand who is now sweatier and wild eyed than ever informs him that as it turns out on this excursion where they’d come across the bug they also come across a scrap of paper connected to Spanish treasure hidden by one long dead pirate Captain Kidd. With that paper, LeGrand had been able to decipher the location back out in the woods where they’d be able to get their hands on the loot.

A month later Jupiter comes to the door of our narrator and beckons him to return to the island. LeGrand who is now sweatier and wild eyed than ever informs him that as it turns out on this excursion where they’d come across the bug they also come across a scrap of paper connected to Spanish treasure hidden by one long dead pirate called Captain Kidd.

With that paper, LeGrand had been able to decipher the location back out in the woods where they’d be able to get their hands on the loot.

LeGrand says to our narrator

“This bug is to make my fortune to reinstate me in my family possessions. Is it any wonder, then, that I prize it? Since Fortune has thought fit to bestow it upon me, I have only to use it properly and I shall arrive at the gold of which it is the index. ”

After some cajoling LeGrand convinces Jupiter and our narrator to head back out into the woods to a particular tree. From there the instructions are very specific, they have to tie the gold bug to a string, climb up the tree, dangle the gold bug on a string through first the right eye lobe then the left lobe of a skull nailed to a branch at the top of the tree. Then Jupiter — who is doing all the work here — is to drop the bug and X marks the spot where they have to dig.

poes-stories-20

The narrator at this point relates a certain amount of doubt to us saying something we in the startup field likely all can relate to:

“Upon the whole, I was sadly vexed and puzzled, but, at length, I concluded to make a virtue of necessity –to dig with a good will, and thus the sooner to convince the visionary, by ocular demonstration, of the fallacy of the opinions he entertained.”

So after quite a bit of digging and shouting and napping and more digging they actually finally obtain the coveted treasure. When they’ve dragged it back to the shack, LeGrand explains to Jupiter and our dear narrator that he hadn’t been crazy after all that month. Instead it turns out he’d been wound up in an elaborate cypher which required quite a bit of code cracking and Sherlock Holmes style detective work.

In the end, Jupiter and our narrator are fascinated, and from what I could tell highly relieved that their friend had finally gotten he was looking for and would hopefully stop dragging them into the woods at night.

Now LeGrand with his righteous indignation about being due his fortune in life is surely just a thinly veiled version of Poe. And in some ways, Poe is himself not so different from us in the startup field.

At-Demo-Day-WeWork-Gives-600000-to-14-Startups2-1

Much like Poe, founders have a vision and some positive indicators from the market and people seem enthusiastic about what they are doing. But how do they get the fortune they believe is their due?

In Poe’s day he wrote on spec and the hope that he might win a contest or a small contract that he could go collect on.These days, tech founders throw together a pitch deck and a website and then try to set up a simple system for people to add their credit card and pay them.

So I shared this story with you because I think Poe’s life and work offers a few key lessons for the modern startup.

ITERATION

The first lesson is around iteration….

Edgar-Allen-Poe-Artwork-edgar-allan-poe-7363811-386-500

Edgar Allan Poe is known as the father of modern horror and also the father of science fiction and also the father of cosmology and cryptography.

Nearly 600 words or phrases were coined by Poe. Some words we still use today, like bugaboo and finicky and multicolor.

This wasn’t simply because he was a creative and divinely inspired human being. He was scrambling for relevance and money. He was iterating and aiming to please.

decoding_003_large

In 1839, four years before the publication of The Gold-Bug, Poe published an article in Alexander’s Weekly Messenger where he challenged the readers to send him coded messages to decipher. He received hundreds of messages so he knew the interest and audience was there for this kind of thing and that’s what lead him to write The Gold Bug.

Poe wanted what we all want which is to deliver to customers and be paid for it. He was an artist to be sure but he was intensely concerned about being an entertainer and reaching what today we might call Product Market Fit.

So as Vice President of Customer Success at Clubhouse Software, I help customers find their way around and begin to master our product and I also oversee our customer support team. Support is responsible for being responsive to those customers, and support is also the frontline for fielding any payments problems.

I don’t know how many of you are old enough to remember this but in the 80s there was a commercial for a brand of hair products called Vidal Sassoon. Their tagline is “if you don’t look good, we don’t look good”.

vidalsassoon

The idea there is that your appearance and success in using their products was a direct reflection on them, and this is true in all manner of customer facing work. regardless of how chaotic or seemingly in flux the company is, the role of success and support is to make the company and product look pulled together and sleek.

We want our customers not only to choose us but to feel encouraged by their choice, both in the product they receive and also in the ways they interact with our company. As such, no matter how the product may we change we need the user experience to feel consistent from initial marketing touch straight through to payment.

In a recent whiteboarding exercise, my colleague in customer success worked with one of our engineers to devise what would be the “ideal invoice”, working backwards from a list of customer complaints about our confusing existing invoice. This is frustrating.
The invoice should just work, so we can work on providing a great experience to the customer.

When we can’t decipher mysterious bank codes but the customer insists their form of payment is valid, we don’t look so good.When we struggle to make refunds or rerun invoices or when we have to read through convoluted logs to understand the how and why of a user’s billing history, we can start to lose customer confidence.

Our payment system needs to look good or else our product and our company start to look downright bad in the eyes of the customer.

INNOVATION

Edgar_20A_20Poe_20Dameron_20final_20-_20smaller_400w

The second area after iteration where I think Poe can shed some light is in the area of innovation.

Poe’s Gold Bug arrived on the scene at a challenging but exciting time in this country.

The American economy had just rebounded from the Panic of 1837 a five-year depression that many believe was caused by Andrew Jackson’s policies against the banks. At times during that depression, things got so bad that people were giving out this thing called a “Hard Times token” in lieu of pennies.

hardtimestoken Sojourner Truth’s “Aint I A Woman” speech commemorated

This is an abolitionist one. They came in many different themes.

But by 1843, the year The Gold Bug was published, a number of innovations made publishing cheaper and easier than it had ever been before.

These innovations include the first lithographic rotary printing press, a press in which the type is placed on a revolving cylinder instead of a flatbed. This sped up the printing process considerably and a form of it is still used today.

The inventor Charles William Siemens, of the same electronics company Siemens that exists day, had also helped to roll out anastatic printing, a process of printing using zinc plates that made copying of prints, designs, and literature faster and cheaper.

This is incidentally around the same time that Ada Lovelace and Charles Babbage were pulling together their work on the Analytical Engine, largely considered to be an example of some of the earliest computer programming.

So lots of experimentation was going on. Electricity was in the air.

We are living in a similar period.

Innovations like the introduction of protocols, the decreasing price of microprocessors, and services like AWS enabled the rise of our current tech industry.

However as our poor unfortunate Mr. Poe discovered, there is quite a difference between riding a wave and being submerged by it.

While I’m not an engineer, in the beginning at Clubhouse we were a tiny team and I worked very closely with the engineers to set up and maintain the payments system.

And the process hit us rather hard.

Enabling payments was one of the biggest hurdles to clear before we could formally launch.

Like at many companies our engineers were hired for their competency in the skills necessary for building our product. While we have to build or integrate and also maintain a payment system, that is not our product. We build and maintain a payment system so we can get paid for building our product.

Now the payment system is integrated in the backend and our backend developers work with a functional programming language called Clojure and a database Datomic. For those unfamiliar, Datomic is a system that is immutable, which of course means that an entity holds on to values over time and as such you get a lot of fancy “time travel features”.

For billing and more importantly for understanding a customer, that is so valuable.

Knowing who did what and when at any given moment in the span of the customer journey is so valuable. For example, if someone was an active user and then left for a long stretch that is useful to be able to trace back actions to find out what may have lead to them abandoning the product. Being able to see the fullest picture of the past and the present is important to people who do any sort of account management. And if you are interested in this, there is also a really great talk called “Exploring Four Datomic Super Powers” that I encourage you to check out. There is a lot of great functionality there.

However, for us, leveraging Datomic to get that full picture meant that we had to take on a large share of the complexity of the payment system and set up our own trialling and payment logic. Something we weren’t terribly thrilled to do. Taking on this complexity also means that we have a hard time using the out of the box integrations with many analytics, metrics, and subscription management services.

Most of the integrations tend to only work properly with the vanilla implementation of payment processing not the sort of mixed up version we’ve implemented.

So at Clubhouse we are still very much in the process of trying to find a middle way where we can leverage the cool innovations of the day like Datomic without losing the great functionality of the payments software and— perhaps more importantly — the expertise of engineers who actually specialize in payments.

INTERNATIONALIZATION

poeinjapanese

The third area where Poe’s life and work proves illuminating is internationalization.

As I mentioned before, Poe’s work particularly The Gold Bug and later The Raven gained him popularity not just in the US but in Europe and even Asia. In fact, the great French poet Charles Baudelaire spent some seventeen years translating the works of Poe, often putting his own writing aside to do so.

Unfortunately all of this international fanfare proved of little monetary value to Poe. In Poe’s day there were no international copyright treaties. The absence of such treaties meant two notable things:

1) Instead of paying American writers to produce new content, American publishers often simply copied the work of British writers and issued it from their presses. There was no author to pay so all the profits could be pocketed.

2) Poe had no real way of brokering to get compensated if and when his work was issued across the pond. Though his work undoubtedly circulated around the world, as an American whose work had not gone through whatever arduous registration processes England or France or wherever required, he had no standing in court to make a claim on his works or their translations.

While I consider myself a copyright minimalist, I do sympathize with Poe as he was faced with a significant obstacle to getting paid. As we know, the primary convention for payment on SaaS software like Clubhouse is a major credit card, but that simply doesn’t work for everyone who would like to use our software and we also know that much of the rest of the free world has wisely rid themselves of checks.

According to a 2012 World Bank report, “at least 110 money mobile systems have been deployed, with more than 40 million users”. Some six years later, I can imagine it may likely be double that number.

mobilepayment.png

When credit cards don’t work but mobile payment systems are on the rise, payment system purveyors should more easily enable tech companies to hook into the ways people around the world can and do pay for things.

When our products have avid fans all across the world, we need payment system providers us help us find more ways to let them pay.

THE EFFECT

To close, I want to share one last nugget of wisdom from dear old Edgar Allan Poe.

In a piece called “The Philosophy of Composition”, Poe explained why he wrote The Raven backwards saying:

“There is a radical error, I think, in the usual mode of constructing a story….I prefer commencing with the consideration of an effect.”

My ask is that payments system providers work with a consideration of the effect on customer success and support people like me, on engineers who are not payment specialists, and most importantly on our end user.

Help us iterate on our ideas while keeping the payment experience easy and constant for the user, help us leverage innovation without losing functionality, and enable us to cultivate an international user base that pays us in the ways that work for them.

And maybe, just maybe, we’ll all get a little closer to our fortunes.

Categories
conferences customer success

“Making Developers on Support Work For Everyone” at The Lead Developer New York 2017

Categories
customer success leadership tech

Some More Hands on Support

I am speaking about engineering – support collaboration this week at The Lead Developer conference. If the topic interests you and you wanna dig in further, here are a few handy links. US_Navy_030521-N-9109V-003_Sailors_and_embarked_Marines_flood_the_flight_deck_with_salt-water_solution,_scrub_brooms,_and_plenty_of_elbow_grease_in_a_mandatory_wash_down.jpg

(at Clubhouse) Eyes Wide Widened: My ‘Evolving View’ of Developers on Support

(at FullStory) How to avoid empathy fatigue on your support team

(at Big Cartel) Why All Hands Support Didn’t Work for Our Company

(at Statuspage.io) All-Hands Support: Why, No Exceptions, Everyone At Our Company Talks To Customers 

(at Wistia) All Hands Support

(at Automattic) 

 

 

Categories
conferences customer success

My SupConf NYC Experience – Part II

You can read Part I of my SupConf NYC experience here
………….

dsc09673

So after months of preparation and practice, SupConf arrived!  The day before the conference, we had a speakers and organizers dinner at the venue so we could familiarize ourselves with the space and also get to know each other. Aside from getting to meet so many of the fantastic people I chat and joke with on the Slack, the highlight of that night was insanely delicious cheesecake in a jar. I’d never had that before! It was dangerous! Stuffed and excited I headed home to rest up so I could come back energized fo the conference the next day.

——-

Day 1 of SupConf was a whirlwind of socializing and listening to wonderful talks. Every one had harrowing tales to tell and sage lessons to share.

dsc09533
I loved Lance’s talk. We all need this skill in our back pocket.

Some of the people I admire most in the support field were in the room and it was hard not to vibrate from enthusiasm and sheer smitten-ness (is that a word?) as they spoke. I’d actually told Scott, the organizer/founder of Support Driven, a few weeks before that, “There will be so many people that I admire in that room, I wish I had some sort of SupConf yearbook, so I could go around and ask my favorite people to sign it!” And so it was!

20170207_203929.jpg

After the first few talks, the organizers came around and passed out the SupConf mini-yearbooks. They featured headshots of every attendee, their name, company, and Slack handle. It was so cool and also exceedingly handy since they didn’t do nametags or lanyards. It also included a headshot page of every speaker alongside a blank page where you could note Key Takeaways for their talk. More conferences should seriously consider doing this!

dsc09579
Breakout session after Laura Marciano’s excellent talk on troubleshooting your  team

 

A slightly racy “GIF battle” (Support Driven folks LOVE their GIFs) officially closed out a full day of talks and discussion, after which I wandered off to take a little time to myself (and get an impromptu manicure).  That evening, one of the conference sponsors hosted a smaller group of us for lovely drinks and dinner. This was a good opportunity to get to know more folks and also calm my nerves a bit before Day 2, when I had to give my own talk. Shout out to Caitlin and Carin, my new support pals in Bozeman, Montana (the Brooklyn of the Northern Rockies!) and Rex (my UK-based Ghanaian brother from another mother) who gave me a big boost of confidence ahead of my talk. I left that night knowing that when I spoke the next day, I would be amongst friends.

 ——-

On Day 2,  I got up early and dressed in the way Lara Hogan prescribes when she says (in Demystifying Public Speaking)

 “Wear whatever makes you feel like a super hero.” 

I was a ball of nerves as I dropped my kid off to school and then rushed over to the venue. I avoided any coffee fearing it would make me too jittery, and I did my best to engage with the other attendees and the other talks. However, as time grew nearer I could feel my stomach knotting up, so I went off into a quiet corner and listened to one of my favorite songs (Akosua by Georgia Anne Muldrow and then did a quick guided meditation). I wasn’t speaking until a bit after lunch and I considered skipping eating so I wouldn’t have anything weird in my teeth, but I couldn’t hold out and ending up grabbing a small bite and rushing up front so that the day’s MC (shout out to the amazing Michelle Bearheart from Trello! ) could get me wired up for the mic. I had to go to the bathroom to clip the lav mic pack up under my dress and on to the waist of my tights. I knew this was going to be the deal, but

I was committed to dressing like my own version of a superhero. And that superhero wore a dress, not a skirt or pants.

dsc09697
That’s me there talking to my seatmates during another breakout session. Wearing red makes it easy to spot yourself in pics later on.

After sitting on the side of the screen through Emily’s great talk on setting career goals, I quickly reached into my dress and clicked the mic pack on. Unfortunately that was a few beats to early and shrieking feedback echo’d throughout the room. I clicked it back off for a second while Michelle announced me and then clicked it back on and walked up to the front. It turns out it was *still* too early to have it on and the first few beats of my talk were feedbacky and weird. I rolled with it and continued on.

I had great time up there, spotting faces I recognized in the crowd, hearing people laugh at funny bits, and watching nods of understanding and agreement.

At one point, I felt my throat dry up and  realized I had no water but I powered through it, mentally noting that I should have that next time (or ask the organizer to provide it/remind me). At another point, I  forgot my next point and had to grab my notes, but even then I felt like everyone was with me cheering me on. When I was done, I got great applause and lots of enthusiastic feedback and tons of high-fives (which I normally hate but relished on that occasion).

Watching the talk now I see where I can improve in the future, but I am genuinely proud of myself.

I think I am an engaging new speaker, and I will definitely grow and improve over time. I thank all the organizers of Support Driven for this incredible opportunity, and I am excited for my future speaking engagements as well as the growth and ongoing success of the truly nurturing SupConf community.

And without further ado, here’s the talk!

SupConf NYC 2016 – Camille Acey Where To Next? Evaluating Opportunities For Growth-HD from Camille Acey on Vimeo.