Tag: featured

  • 12 Days of Creativity

    12 Days of Creativity

    Something that I was struggling with as 2020 came to a close was that I was leaving the year the same way I started it – feeling burnt out. Whilst things had improved – I had managed to get a better baseline, address life debt, change the situations that had caused me to be burnt out – I hadn’t managed to reconnect with my creativity.

    Of course, the pandemic has not helped. Emotionally, the background news of the world being on fire is draining. Practically, I used to write on planes, in coffee shops… I managed a couple of posts written in hotel lobbies or bars, but a hotel stay is an expensive way to blog, and not always possible anyway with the periodic lockdowns. I used to spend a lot of time in art galleries, exploring, finding inspiration. This, too, has not been possible.

    I have felt so lacking in drive and inspiration to create; I haven’t known where to begin. My Glowforge arrived in May and it took months for me to even do a test print – let alone anything more. My house renovation blog post moved achingly slowly. A common topic in coaching calls was that I wanted to write, periodically had ideas and yet… consistently failed to do it. Of course, these things often don’t get easier as time goes on, either. Writing is a habit; a practice… my habit was gone.

    But as the working year wrapped my coach and I came up with a plan. 12 days off, something creative every day.

    I took a broad view of what would constitute “being creative”, simply put it meant something would exist that didn’t before.

    Day 1: Flowers

    I started with something easy, where the only variable was raw materials. I knew if I bought home enough fresh flowers, I would do something with them. It has been mostly seasonal bouquets at the grocery store lately, but thankfully M&S came through for me. A great selection of both small and large roses, and some exciting seasonal extras.

    I made up three vases. The first combined sticks of willow with lilies and eucalyptus leaves. It’s a really large arrangement (around 3ft x 1.5ft) but it’s been a lovely focal point in the kitchen.

    The second is the simplest, three colors of small roses (white, deep pink and yellow) in a bowl vase.

    The third is another large (not quite as large, ~2×1.5ft) my favourite pink blush roses with cream and some Alstroemeria (what I would call a “filler flower”) to round things out a bit.

    Aside from being easy, flowers were the perfect way to start because they became a physical reminder and validation of the exercise. All of the arrangements are still going, and I’m excited to create new ones to replace them as they die out.

    Total cost was in the region of €50-60, which is pretty reasonable for three good sized arrangements lasting around two weeks.

    Day 2: Cake

    Day two I was still not feeling particuarly “creative”, and so looked for something that it would be easy enough to see through if I started it. I settled on making a coca cola cake (this recipe looks similar, although I suggest single cream instead of milk).

    It was going pretty well until I made a crucial mistake towards the end. I flipped it, regretted it, tried to unflip it, failed. I piled the pieces that had fallen off on top and iced it, figuring it would taste the same anyway. Unfortunately (or fortunately? for my sugar intake) that was not that great (two more mistakes: double cream because there was no single, and cooking it fully – it’s better slightly undercooked and gooey). I stuck most of it in the freezer, so maybe I’ll be grateful for it one day.

    Day 3: Photography

    Day 3 was December 25th, and I was still lacking in momentum. My partner and I went exploring, walking a completely new route. I took some photos, and tried some new styles when editing them.

    Day 4: Bowl

    Made a bowl on the Glowforge. This was following a pattern from the catalog, but the gluing was pretty finicky. I learned some things, bought a different kind of glue, and a few days later, much more easily, made a second one that is a little bit better aligned.

    Still! It was an achievement and the first meaningful thing I had made on the Glowforge.

    Day 4 was the day that I finally found some momentum and could see how the practice compounds. I photographed the flowers, incorporated the previous days walk into my “usual” walk.

    I start making notes about how I’m feeling to turn into this post.

    Already this idea has allowed me a broader lens. Instead of “I must write” or “I must use the glowforge” I think more broadly, and pick something I “want” to do, or that fits the energy / expertise I have. The bowl was a print from the catalog, next step will be a print from the catalog on a material where I have to encode the settings. I’m working up to printing some ideas I have from scratch, but I don’t have to start there.

    What would it look like to do something “creative” every day, even once my time off is over?

    Day 5: Friendship bracelet

    During time spent searching around town for materials (more glue, keychains, spray paint…) I found thread for friendship bracelets. I used to make loads of them as a kid, and it seemed like a fun thing to try again as part of this project. I put on a movie and knotted away, by the end I had this. I gave it to a friend who was super touched, and a second friend asked for a thicker one (which took much longer to make), so in all it was a success.

    The big project of day 5 was supposed to be a tea light holder, but I messed it up and put one side on inside out. So frustrating!

    Question: is it creativity if it fails? I want to say yes, but I think the need to make things successful, to “finish” them, is one of the thing holding me back.

    I learned a lot from my failures. Once I realized the tea light holder is wrong, I experimented with removing the protective coating with dish soap and a sponge (works great!) The bowl is not perfect, so I was happy to experiment on it. I ended up using them both to test out the metallic finishes I bought.

    Day 6: Owl

    I had had this kit for ages, so long I don’t even remember who gave it to me! (Sorry!) But in the mood for something different, I got it out the cupboard and spent the evening constructing it. I messed up a few times but I got there in the end, and I think the result is pretty cute!

    I also printed out some leather letters for keychains. Blocked on keychains arriving (after searching Cork for them I eventually gave up and bought online). This was a momentous occasion, as it was my first time using a non proof-grade material in my Glowforge. I had been super anxious about this, but it worked fine. I bought some comparable leather, and used the same leather settings as the proof grade material. It probably needed a little more power, as some of the needle holes needed to be pushed through a bit more, but came out fine over all.

    Finally, I took a second go at the bowl: this time with better glue (more precise, faster acting). Much better!

    Day 7: Tiny Planter

    I had been looking at this design for ages but lacked the required material (thick acrylic). Finally, I decided to try some fluorescent yellow acrylic I had but wasn’t sure about. Again, it wasn’t proofgrade (I love proofgrade, but shipping wood and acrylic from the US to Ireland seems bonkers) my friend Seb recommended a more local supplier and gave me his acrylic cut settings. My plan: print twice, glue together.

    Unfortunately, I had two problems. The first was the material was a bit too big for the Glowforge. Apparently you can score (very deeply!) and snap acrylic, but there’s a real risk it will shatter and anyway… I lacked the tools to do the scoring. Thankfully the lovely man at our local hardware store offered to saw it in half for me. The second problem was that the design uses a lot of acrylic, and I didn’t have enough to print twice.

    Instead I decided to make a tiny version. I sized everything down to 50%, and… voila!

    It turned out adorable so I figured I could get four tiny planters out of the material I had. Unfortunately, I had a bunch of problems with the side pieces snapping off, and being just a smidge too wide for the cut. I think the design would work better at 60% rather than 50%, but I would need to check that. US sizing is in inches and it’s ~1/4″ (thick) and ~1/8″ (medium), but Europeans size in mm and it’s 0.5 (thick) to 0.3 (medium). Imperial “measurements”: why. So inexact and frustrating.

    But still, I love it, and managed to produce one extra for a friend! Now to get a tiny plant to put inside it!

    Also: experiments with spray paint and acrylic for the tea light holder. Conditioned the leather for key rings. Found some interesting supplies at the art store! Started on another, much wider friendship bracelet on request from another friend.

    Day 8: Custom Print

    Took a picture, used an app (Rookie Cam) to render it as a drawing, touched it up to remove artifacts (downloaded GIMP!), added a border and made it a PDF (keynote) and printed it. I did a test on some draftboard, and found a step I needed to remove.

    Quite excited about this, will go through my archive and see if I can find other pictures this can work for. I think they need to be structurally recognizable, but low detail. This one with the (Skellig) island and the bird is perfect.

    Day 9: Keychain!

    The keychains I ordered online arrived earlier than expected – yay! I took the leather letters, applied leather conditioner and leather protector, then stitched together with two colours of thread. This was pretty hard and I stabbed myself multiple times with the needle; there was quite a bit of blood. I also ended up unpicking it and restitching it tighter, but in the end I’m happy with it. I like the two tone thread look!

    Also: wrote the first WTHIC since October. Continued work on thicker friendship bracelet. Went through photos to create more of the day 8 style prints.

    Day 10: Retro Camper Desk Organizer

    My biggest piece yet, the Glowforge January design (I subscribe to Premium). It seemed like a good way to start 2021 and the #makedontbreak challenge (my friend Rachael suggested in response to my WTHIC email).

    This was so fun! I am really happy with how the metallic paint came out.

    Sprayed the tea light holder with a copper spray, so that is now “finished” bar the electronic tea light (which I have searched all of Cork for and cannot be shipped to Ireland from the UK). I’m not totally happy with the finish, so I may respray it again later, but for now but I think it will look okay once the light it in it.

    Also: unpicked day 9’s keychain and restitched it tighter. Yet more work on the thicker friendship bracelet.

    Day 11: Cross Stitch

    Made this piece from a kit a friend gave me ages ago. I think I unpicked about as many stitches as I ended up with, but I’m pretty happy with how it turned out!

    Also: letter keychains for my friend and her husband! And, I finally finished the thicker friendship bracelet. 12 threads: never again.

    Day 12: Bracelet

    This was my most tricky creation yet. I had the idea that it would be fun to engrave my own handwriting on things, like the custom prints from day 8, but why not also a leather bracelet. Who knew how hard this would be.

    Step 1: Write on a piece of paper. Attempt to write in a straight line.

    Step 2: Use the scanning function on the phone to capture the text.

    Step 3: Crop and make the background transparent (I thought this was easy to do in keynote, but in the end used some online service for this).

    Step 4: Build up bracelet design in Keynote.

    Step 5: Try and turn it into an SVG. Fail. Build it from scratch in Gimp. Somehow still fail to turn it into an SVG. Try various online services. Fail. Eventually find this site and get a reasonable SVG.

    Step 6: Upload design to the Glowforge, and carefully select which bits to cut / engrave / ignore.

    Step 7: Try on draft board, check size, adjust as necessary.

    Step 8: Print on leather!

    Step 9: Add thread and turn it into a bracelet.

    I am summarizing here, because step 5 was actually around 100 steps and took about an hour but finally I have made something that if not perfect is wearable. I really love the way the handwriting came out.

    How I want to improve it: double side it, and edge it with stitches, that will hold the thread in making it more sturdy.

    Bonus: yet another keychain.

    What I Learned

    • Momentum builds momentum. Looking back through the whole thing it’s really clear that I started with very little momentum but once I got going it really compounded. The first days I really just eked out one small project a day, but not long into it I was pushing multiple things along, and achieving larger things.
    • Ambiguity can be freeing. The lack of specificity helped a lot. It freed me from things that had become a chore (“write!” “use the machine you spent a fortune on and years waiting for!”) and focused me on how I wanted to feel – creative. It also set the bar lower on days when I needed it to be lower, and allowed me to get started at all.
    • Significant change requires singular focus. I had this time off work, but I did not fix my sleep schedule, the house is chaos, and I haven’t been outside every day (normally a core rule for me). I have generally lapsed at everything I would “usually” do, in order to address the one thing that I really wanted to change. This isn’t sustainable long term, but for twelve days? Whatever. And, after over a year of trying to “feel less burnt out” / “find some creative energy”, I actually did, so who cares about… anything else at all. Yes, I’ll have to bring those things back in, and find some sense of balance, but that’s fine – now I know I have it in me to create again.

    What now?

    The last three days of my project coincided with the first three of the #MakeDon’tBreak challenge, so I’m going to try and keep doing something every day through January [twitter thread]. We’ll be in lockdown all through January, so distractions are pretty minimal, and this seems like a nice way to spend it. I have more prints (like day 8), more friendship bracelets, more keychains, and another (terrifyingly complex) cross stitching kit. Wish me luck!

  • The Great DomestiCation

    The Great DomestiCation

    At the end of 2017, after 3 years of nomadic life since leaving London, I moved to Ireland. I did this on the basis that I had to live somewhere, and in Ireland British people have the right to live independent of the EU – it was a safe haven from Brexit, which had left me determined not to return to the UK again – aka, Brexile.

    Since rental yields in Ireland are amongst the highest in Europe, the sensible thing to do financially was to buy a property. On an emotional level, less sensibly, I wanted a really nice bathroom. Of course, with rental yields being so high, every habitable place I found I was in competition with investors – who thought nothing of outbidding me by €15K. After the devastation of finding the “perfect” place (two bedrooms, two bathrooms, in an apartment complex just across the river from the ~6 month rental I’d found on arrival) only to be dramatically outbid, I got real, defined my parameters, vowed not to get emotionally caught up in a place again, and accepted that the extent of the renovation work might be much more than “just” a bathroom.

    Eventually, I found a place that fit my parameters. A 3 bed 1 bath townhouse in an apartment complex. There was parking, and it was empty and clean (unlike some places), but had had essentially nothing done to it since construction, well over 20 years prior. It was a shell.

    I had planned to hire an interior designer, but after (also) being SOL there, I found a project manager, and set out to see what I was capable of on my own. My goal: the feminine smart home, modern, vibrant, but not overwhelming, everything with either purpose or beauty (but preferably both). At that point, I owned a desk, two exercise balls, and an assortment of art. I was really starting from scratch, and as my friend Camille said to me some time into this endeavor, I “really did go from zero to fully domesticated very quickly”.

    To start with, the things you don’t see in the pictures. Every room has underfloor heating – so much better in the cold Irish winter. I was very intense about this, vowing that I would “be warm in February”, only to learn that not all Februaries are quite as cold as the only one I had then experienced. This means the radiators don’t have to be as big, and in practice I rarely turn them on. All lighting is Hue, so I can control the colors, and keep rooms warmly lit in the evening – which helps with sleep. There are Sonos speakers throughout the house, typically music is playing from the moment I wake up until I go to sleep. Similarly, there are 4 electronic diffusers and 3 reed diffusers throughout the house. As I set about creating each space, I asked, “how do I want to feel?”, and scent is an important part of that.

    I thought about designing the house much like designing a user interface. Knowing my own limitations I eliminated texture – no wood – because it’s much harder to match and would make ensuing decisions more complicated. Instead I opted for the same base of mid-grey flooring and pale grey walls throughout, and then on top of that built out each room’s character. Whilst all the colors would be too much together in one space, they all work together, creating a sense of harmony and progression. In each room then, there were two decisions – accent wall color, and blind color. Much more manageable than creating every space from scratch.

    Kitchen

    I wanted the kitchen to feel vibrant and energizing, like a sunrise or a sunset. The pink wall and pink and orange blinds, coupled with a large flower arrangement on the kitchen island make this a space that I’m always happy to walk into. The pink shelf brings the pink from the opposite wall across the room, and the mirror creates more light and space. In this room, I opt for fresh and clean scents, like Eucalyptus or Tea Tree.

    The kitchen is from Cash and Carry Kitchens, and was designed by Marie. I really like the white look, and it allowed me to buy high end white appliances and have them fit in, without dealing with the annoyance, flakiness, and limited selection of built in ones.

    All the appliances came from Ann M at Harvey Norman Little Island, who was incredibly helpful.

    Other notable items:

    • The love seat and counter stools are also from Harvey Norman.
    • The London pillows come from the Futon Company shop in Cambridge.
    • The purple patterned throw is from Ecuador, I bought it during the Feria de las Flores at the Jardín Botánico de Medellín (one of my favourite places in Medellín.
    • The art is mainly pieces I’ve collected on my travels, but several prints come from Wild Design.
    • The cityscape above the shelves is from Boston.
    • The four pictures next to it are scenes of NYC.
    • The small painting depicting Paris on the shelves is by Jean Pierre Weill, it’s built up on layers of glass.
    • The grey containers are by Starsglowing.
    • The ceramic owls are from the Chiang Mai Art Museum.
    • The lamp in the bottom right of the shelves is from Kaïko.
    • The vases and tea set I bought on my travels in China.
    • The rose gold bin is from simplehuman.

    Living room

    I wanted the living room to feel relaxing and peaceful, like dusk. The blankets and the scent of lavender make this a cosy place to chill out at the end of the day.

    • Normal People are just People you Don’t Know Well Enough, I am pretty confident I got this in NYC, either at the Whitney or MoMA.
    • The cockerels below that print are an original by Srijai Kuntawang, I bought it at the Art Mai Hotel.
    • The planter was a gift from my friend Camille, by Madam Stoltz from Unbound.ie.
    • The vertical black picture is a tea towel from Japan.
    • I bought the big picture in the middle of the main wall from Perry St Cafe – they regularly rotate displays of local art.
    • The picture of the boats is by Christine Creagh from the Yellow Door Gallery in Baltimore.
    • The small blue picture on the far left is from an artist in Guatape, I found his gallery wandering around the town.
    • The left shelf: The brown container on the top I got in Fiji, the vase underneath it is by Diem Pottery from Kilkenny designs.
    • The right shelf: The bowl I bought at a store by the Museo de Arte Moderno de Medellín, the vase underneath I bought in Venice (that style can be found in many of the stores selling glass) and filled with regular fairy lights.
    • The sofa is from Harvey Norman, and the black patterned throw is from Equador, I bought it with the other one during the Feria de las Flores at the Jardín Botánico de Medellín.
    • The TV shelf is custom built for the TV (a 55″ Sony Bravia, also from Harvey Norman).

    Hall

    An early decision in the design of the house was to paint the staircase orange. There were various suggestions to carpet the stairs and make it a more neutral space (aka cheaper and unappealing), but I went fully the other way!

    I wanted to create a connection between the kitchen and the hallway, and rather than let the hallway be bland and boring, create a light and beautiful space – this is particularly apparent at the top of the stairs, where the mirror, statement light fixture, and glass doors make what could be a small dark space feel light and spacious. It creates a lot of warmth and generally makes the house feel welcoming, especially when combined with fresh but neutral scent, such as fresh cotton.

    • The shoe rack is custom made.
    • The cogs I bought at the boat station on the way to MoNA in Tasmania.
    • The map of Ireland picture was a gift from my friend Sophie.
    • The picture of the woman above the shoe rack was a gift from my friend Rochelle.
    • The pink and yellow picture by the kitchen I bought in Montevideo, Uruguay.
    • New York pictures I bought from a vendor by the Highline in NYC.
    • Flower pictures (bottom of the stairs): bought on my adventures in Canada.
    • Beach pictures (near the top of the stairs): bought on my adventures in Bondi Beach in Sydney, Australia.
    • Pictures at the top of the stairs are from China, bought on my adventures.
    • Lighthouse picture, bought at Mizen Head in south west Cork.
    • Boat picture by the bathroom door is from the Framemaker in Cork.
    • The orange print on the top shelf was a gift from my former colleague Nick.
    • Light fixture is from Galaxy Lighting in Cork, I saw it and fell in love – I love the shadows it casts and the way it reflects in the mirror.
    • The rose gold bin is from simplehuman.

    Bathroom

    In my work on this renovation, my first stop was City Tiles and Bathrooms, where I told a lovely man named Barry that I was determined to have the bathroom of my dreams (modulo the depressingly small size of most European bathrooms). For me this meant: a rain shower and storage.

    Note the little details in the shower – the shelf to put your leg when shaving, and the built in shelves. Finally! A shower with enough storage space for all my products without being messy. The cabinetry gives me space for all my beauty products, my beauty product stockpile, and even the storage of towels. Underfloor heating and a surprisingly powerful towel rack keep this room dry and warm all year round – even in February.

    The light fixture conceals three Hue bulbs, which allow me to create the perfect evening lighting.

    Office

    I wanted my office to feel energizing and creative, but also cosy. As I was working from home even pre-pandemic, I wanted to create a space where I would be happy to spend every working day! I like to scent it with something energizing like orange or mint.

    Despite the impression the pictures give (wide angle lense on the newer iPhones is amazing), this is the smallest room in the house, and given there was no way to make it feel bigger and spacious, it was unsuited to a minimalistic approach. Instead I went for a kind of creative clutter. I love this room, everywhere I look I find something to inspire me. The hanging egg chair gives me a space to relax during breaks in a long day.

    • Grey vase on the window sill, Paul Maloney from Kilkenny designs.
    • The owl fabric covering the black console table was a gift from Ellen.
    • The grey storage containers underneath are from Søstrene Grene.
    • The hanging egg chair (long time dream) was from Debenhams (garden furniture range, but who cares) and the blanket is from Kilkenny designs.
    • The desk is black glass and from Harvey Norman.
    • The mysterious machine taking up so much space under the shelves is a Glowforge.
    • The rug is from The Range (and yes, it is as soft and fluffy as it looks).
    • The pinhole photography prints are from an artist who only sells them Saturdays on the Highline in NYC.
    • The Calder mobil is a Flensted, bought at Kettle’s Yard in Cambridge.
    • The light fixture is from Cork Lighting & Interiors, in the same style (but different) to the one in the bedrooms.
    • The pictures above the monitor were bought from a vendor by the Highline in NYC.
    • The raccoon pictures were gifts from Nate and Sarah.
    • The landscape belonged to my grandparents.
    • The panda pictures were both bought on my adventures in China.
    • The cockerels are another original by Srijai Kuntawang, I bought it at the Art Mai Hotel.
    • The small green vase on the top shelf was bought on my adventures in North Korea.
    • The small picture on the top shelf is of Casa Mila in Barcelona, my favourite building in the world.
    • The owl picture on the top right was a gift from Emi.
    • The elephant, elephant vase and cat picture were all bought on my adventures in Thailand.

    Guest room

    I wanted to create a guest room that would feel like a beautiful sanctuary for anyone who came to stay in it, whilst also providing extra storage space that I desperately needed with the corner wardrobe and under bed storage. I believe the only scent for a bedroom is lavender.

    • The bed is from EZ Living, and features hydraulic storage (amazing).
    • The wardrobes are from Cash and Carry Kitchens, copper handles match the copper light fixture from Cork Lighting & Interiors.
    • The lamp is from Reykjavík, Iceland.
    • The small purple vase on the left of my bed was my Grandmothers.
    • The picture over the bed is a Japanese tea towel.
    • The hanging is also one I bought in Japan.
    • All other pieces of art were picked up on my adventures.

    My bedroom

    The final room, my bedroom, which I wanted to be a space where I felt happy and inspired to wake up every morning. I painted the wall my favourite shade of pink, and filled it with items that I find beautiful – as well as the comfiest, cosiest bed linens I could find.

    • Bed (aside from size), closets and light fixture the same as the guest room.
    • The pillows are Makimoo bamboo pillows – lovely and soft and hold their shape really well.
    • The picture over the bed is called “Venice in Love”, by Jean Pierre Weill, I bought it in Tel Aviv, Israel.
    • The vertical pieces either side of the bed are Japanese tea towels.
    • The two pictures on the left at the foot of the bed I bought in China.
    • The two owls on the right I bought at the Chiang Mai Art Museum.
    • The two prints in the middle are by Felicia Thomas from Wild Design.
    • The owl print by the door is by Belinda Northcote from Kilkenny designs.
    • The glass orb I bought on my adventures in Nova Scotia, Canada.
    • The two glass paperweights belonged to my grandparents.
    • The vase was a gift from my parents from Jerpoint glass.
    • The diffuser is Green Lavender by Urban Apothecary.

    Other credits…

  • The Cost of Fixing Things

    The Cost of Fixing Things

    Fall in Bruges

    In September, I disappeared in Seoul and caused everyone who cares about me to think I was having some kind of breakdown. I deactivated my Twitter account, and refused to engage with anyone other than my closest friends. I got to the point where I felt I had to drop everything, and then I came back and chose things that could return, one by one. Some things still haven’t made it back. Maybe they never will.

    What took me to that point was three team turnarounds in three years. The final one, with a fractured shoulder whilst buying and renovating a house (also a turnaround). But that is the big story – what took me to that point was a thousand choices, made at various decision points, that consistently put my own well-being last. What took me to that point was some deep seated need to act as-if I was some highly-optimized, resilient robot rather than a physically hurt human being with her own needs and life.

    It was hard to untangle this, because the ways in which I am good at the turnaround are directly related to the ways in which I am bad at being a human in the world. I focus on the important – I let things that are not important go (but life is made up of unimportant things and it’s hard if none of them are “done”). I stop dysfunction like some kind of human shock absorber – I am afraid to let people into my own dysfunction, to the point of being willing to shut them out entirely. I have high standards – the standards I would hold other people to are nothing compared to the standards I have for myself. I see it as my job to live in the space of ambiguity and create clarity for other people – I don’t prioritize resolving ambiguity for myself. I am very driven by values – sometimes the values I hold conflict with what I need as a human.

    “Show me your heart like transparent Glass Catfish” ~Seoul Aquarium

    In this space, when people expressed concern it was met first with bewilderment, then resentment. Bewilderment, because this was – as I understood it – what I had been asked to do. It was always going to be terrible for me, the real surprise was how badly my shoulder was injured and that renovating a house was extremely terrible too. Resentment, when that concern came as feedback, to which I wanted to respond, “I did what you needed, I’m sorry it didn’t look pretty, too.”

    In a distributed environment, no-one needs to know how you really are.

    Around the time I disappeared in Seoul. I was winding up on the third turnaround team, handing it back to the proper person. I was deeply burnt out, and my then-boss hadn’t decided what team I would go to, resulting in me drifting around without a clear place to go, unsure of what I could take on – my life in general feeling on hold around medical appointments and waiting.

    At home, I found a therapist, finally unpacked and started living out of closets rather than boxes, did the work of building a life in the city I had spent the best part of a year calling home but didn’t feel like home yet, prioritized medical appointments above everything else (with some help from my mom). At work I covered a month of parental leave for one of my peers, and the engineer leading a huge project (the new editor) asked me to come help him. I joked to my peer leading that part of the organization that he had brought me to her like a cat with a dead animal offering. I “joked”. It felt true.

    “I’ve found out that life and soul are the most essential elements in art.” ~Arario Museum in Space, Seoul

    We rolled out the new editor. I moved to another team, reporting to the CEO again – I was grateful to him for resolving the drifting, but felt like I was doing what everyone else wanted me to do – although how could it be any other way, when I didn’t know what I wanted myself? I kept going to therapy, got to the place where I could confront some of my less appealing characteristics, spent time with friends, finally shared pictures of the house. Had moments where I could contemplate feeling okay again, even if that was definitively, absolutely, not right now. Always contingent on things outside of my control.

    Today I feel okay, even happy. Things are not perfect, but I have a sense of direction and purpose, some kind of stability – some internal, some external. Various things came together, and it started to feel like enough to go on. I started to feel like enough.

    Only the most perceptive people notice when you disappear

    Raccoon ~Seoul

    This was not supposed to be a story about burnout, this was supposed to be the things I learned working through it and being able to see the other side. But it feels dishonest to write about how to make teams more functional without some level of insight into what that process has done to me. It feels futile to talk about working through burnout, without some insight into the context that burnout was within. Only the most perceptive people notice when you disappear, especially if the Achievements keep accumulating because it’s easy to assume busy instead. Not everyone can be present when you’re a shadow, simpler and less confronting to say “let me know if you need anything” and disappear instead.

    When I think about burnout, I always come back to the Maslach Burnout Inventory (there is a book, but it’s more succinctly summarized in this article). It is a helpful framework for thinking about burnout, in particular the five causes of burnout that are not overwork. They are: lack of control, insufficient reward, lack of community, absence of fairness, and conflict in values.

    Lack of Control

    Lack of control was a huge factor for me. Both on a personal level (the healthcare system and builders), as a human at work (what is my job now?) and in a work context (these things are not working well, but out of my remit to fix). This is really what triggered my disappearance in Seoul, when I realized going with the flow was leaving me completely miserable, and even (in a certain context) triggering an existential panic where I wasn’t sure if I existed at all. It was a topic that came up again and again in therapy.

    Owl, Tokyo

    Letting go of everything allowed me to focus on things within my control. The relationships I was confident were good, the appointments and calls I could make to move things forward, the remit I had at work. I refused to engage with the ambiguous or bad, and demonstrated to myself that most things continued without them. As I let them back in, I was very deliberate in giving them an appropriate place in the hierarchy of importance, and any supporting structure needed to be manageable.

    I learned more is within my control than I thought, and that I need to accept and manage the impact of things outside of my control. The result of this is that I feel more centred and less blown about by uncertainty or ineptitude. I change what I can change, influence what I can influence, and when neither is an option, I aim to contain it and move on.

    Insufficient Reward

    One way to look at the situation I was in – drifting – was that the reward for doing a good job was the ambiguity, because the only decision that had been made was that I wouldn’t go back to my previous team. I understood (and agreed) to this, but it definitely left me living in a space of uncertainty that got harder and harder to manage over time. I felt less confident – did my boss really value me? Would other people think I had been demoted? Would what I ended up being given be something I even wanted?

    In response to this, I searched for validation elsewhere. Focused on shipping things: internal blog posts, progress reports, external articles. Hoarded complements. And with people I trust, admitted that I felt terrible and straight up asked for the validation I needed. These things helped in the moment, although fundamentally they needed to come with a change in mindset too – one of looking for information that supports a positive hypothesis, rather than a negative one.

    Lack of Community

    It is a truth universally acknowledged that leadership positions are lonely. In many ways, I got myself into this situation by so badly wanting my peers to be a team and being prepared to do things in service of that. At the lowest point, though, I did feel disconnected from them in terms of tempo – they were busy and focused and I was drifting around. They had direction and I was lost.

    This was a time to lean on the community I had worked hard to build. When I left our group to move to the new team, one of the most meaningful things was the support and enthusiasm of my peers in seeing it as a positive move – even as I wasn’t sure – and as I left the channels, one of them veto-ing my departure from our backchannel and peer support call.

    “If all relationships were to reach equilibrium then this building would dissolve” ~Arario Museum in Space, Seoul

    other people assumed I felt the most confident at a point where I felt the least confident

    It was also a time to build community. On my new team, and with other groups of people who it’s in our remit to help. Peers in other parts of the business, all engineering team leads, everyone involved in our hiring processes. This work is just beginning, but I am genuinely excited for it.

    Last week I was at a leadership offsite where we had an intense development week. A coaching exercise with a colleague I don’t normally have much interaction with surfaced that other people assumed I felt the most confident at a point where I felt the least confident. This is one of the dissonances that can arise when people don’t see each other, and I think in the absence of other cues, can make it easy to assume someone is busy and not reach out. I’m not totally sure what to do with this, but I can at least model the behavior I want, and make more effort to check in.

    Absence of Fairness

    There was one situation in particular that really got to me – a lot of my time was wasted, I was denied any kind of input, and a situation was forced onto the team that I felt negated much of the effort I had made. It felt like a situation where “assuming best intent” and trying to be helpful – usually a good thing and a strength – in the wrong situation feel like an attack vector.

    I’m not confident in what I’m taking from this, yet. On a concrete level, the importance of documenting and being direct. I think it’s easy to assume that “other people notice” but if they don’t this can lead to a cycle of frustration. Usually little things are just that – little things. However sometimes they are a product of something much bigger and much more problematic. If no-one flags the little things, the patterns take much longer to surface.

    On a meta level, it’s reminded me to ask, “how much is this is my problem?” and accept that sometimes the best we can do is manage the impact of failure, because we do not have the power to prevent it.

    Conflict in Values

    “Inframince” ~Arario Museum in Space, Seoul

    This came up, and particularly when people’s stated values differ from their lived values – creating a compound effect. This is a concept that has come up a lot in coaching for me – for every turnaround project – the question “what values is this hitting for you?”

    so much of good management seems to be about being a decent human being

    I am personally very values driven; so much of good management seems to be about being a decent human being. Of course, being decent is rarely the easiest path in the immediate frame, and often a lot of work. This is the kind of dissonance that will escalate a disagreement to existential crisis for me.

    Again, it is a strength, values scale much better than people or process and creating values on teams is part of how I have been effective, and able to hand things off. However, the downside is clear and intense. I think this is true for a lot of effective people who burn out – we are good because we care, but the downside is that care is for a reason – often values – and we struggle when those values are violated. It can seem like the path for success is to be more self-serving and care less, but that just creates the situations that we claim we don’t want. If we want things to be different, we have to make them different as we can, but in a way that isn’t self-destructive, or requires changing the core of who we are.

    This is not a concrete takeaway, so concretely, I seek to support people rather than systems, make sure my work aligns with and communicates clear values, and ask questions and seek clarity on things that are open to interpretation or are potentially problematic.

    Work Overload

    “Live without dead time” ~Museum of Art, Seoul

    Of course, in all of this, working a lot was a factor. I worked long hours and regularly over weekends (even if “just” travelling so as to avoid missing a weekday). In many ways overload was a multiplying factor, though; I used working to avoid things I didn’t want to deal with (like the building site or the medical system), and the fact that I had worked so hard compounded the existential problems of reward, fairness and values.

    The first thing I changed here was working to make the time I did take off better. Moving to a place where I could have a separate office (I work from home), and organizing my living space and containing the mess such that I could have a place to relax without seeing a physical todo list in the form of things not yet done or tidy. The better my physical space has been, the better I have felt. The first time I had a weekend where I didn’t have any domestic stuff I needed to do was a milestone.

    Within that, I made more effort to stop work by 7pm, and then be deliberate in spending my time on what would make me feel better. E.g. making an active choice between the gym and bringing some sense of order. When I needed to work a weekend, I made a point to balance that with other things I needed – like working in a coffee shop for some human contact, and breaking up delivery points with things for me. And also making sure I didn’t make the exact same mistake the following week and have to work a subsequent weekend.

    The second thing was a resolution to take statutory holidays. These are not super meaningful to me – as an atheist, I don’t celebrate religious holidays, and in a distributed environment there are always other people working. However coming to see them as like weekends – arbitrary days that we have agreed as a society not to work – has been helpful. Yes, I could take a three day weekend any time when flights to Paris are cheaper, but I can take that three day weekend and the arbitrary one too (and using the arbitrary one to play video games is completely reasonable).

    Similarly, I started taking time off for medical stuff. This wasn’t always possible (it’s unfortunate if one is in hospital on a day that is supposed to be release day, for example), but overwhelmingly has been. If I have to go to the UK to see the doctor, I take the entire period, rather than trying to work around flights and transit and appointments, to do what is going to be best for me. This was a bit of a culture shock for me, at the Conglomerate when people were sick they “worked from home”, but in an environment where people already work from home people actually take sick days. Including me.

    Finally, I think it’s always worth taking time where there is opportunity. I took an extended break between ending my last job and starting this one (I fulfilled a life goal and went to Tuvalu). I made two weeks of space between the first team and the second, even though I had some work to do, I was free of responsibility and had two amazing long weekends (one in London, and one in Paris). Winding up on the second team made space for the disappearance in Seoul – where I had many positive experiences (including meeting a raccoon!) even though I didn’t feel particularly positive in myself.

    The Other Side

    The TL;DR of this is perhaps that I have spent a lot of time lately confronting the shadow side of my strengths – the personal cost of the professional “success”, and how that manifests as burnout. It’s hard to understate how confronting this has been, how difficult, and it’s still far from done.

    I know, though, it’s something I am far from alone in. Burnout is the epidemic of millenials, and the epidemic of tech, particularly in those of us who genuinely and deeply take on the work of inclusion, of trying to make the functional environments we have never, or rarely, experienced ourselves. A while ago I wrote that the third shift of inclusion work is to heal ourselves and more than ever I believe this is true. Broken leaders cannot create functional environments – especially if we have power, we owe it to the people we work with to do the work on ourselves that makes us safe and reasonable people for others to show up to.

    “Forgive Yourself” ~Sign in Tulum, Mexico

    Thanks to my colleagues who engaged so openly in our leadership training, which helped me break out the other side of this, my boss who looked out for me at the worst point, and the amazing community in our engineering managers slack, who started the conversation that made me realize I was ready to write this, and inspired me to do so.

  • Phase 1 of Hiring, Getting from 0-30

    Phase 1 of Hiring, Getting from 0-30

    Towards the end of 2017, we reopened hiring on the mobile team at Automattic which had been shut since the start of the year as we got things in order. I think of this as phase 1 of hiring on the team – nailing the basics of the process, and making some progress with diversity numbers.

    An up front note about diversity: Diversity is more than gender, and gender is not binary. However whilst acknowledging the limitations and flaws, we can use gender as metric as to how our hiring process is doing with respect to inclusion. We can use it as an indicator for diversity at every phase in the process, and use that to identify where we can improve the process for everyone.

    For reference, I was the first woman on the team, which was ~24 people when I joined at the end of 2016. When we opened hiring, there were two women, although both in leadership positions – this helps a lot.

    The TL;DR of how our funnel looked at the end of phase 1 is this. You can see that using our raw (and flawed) metric, the diversity improves at every step in the process. This makes sense given that data shows women hold themselves to higher standards when applying for jobs.

    Q4 20173 people
    Q1 20185 people
    Q2 20182 people
    Q3 20185 people
    Q4 20181 person

    Revamping the Process

    Whilst we didn’t change any of the steps in the process, we did revisit each one and improve it.

    • We revisited our job postings to appeal to a broader spectrum of people, emphasising impact and collaboration. The job postings now score 95 and 96 in Textio.
    • We diligently posted a hiring stats update each month (the way we review all our projects on the team regularly!), breaking down progress at each step of the process. Monthly was a good cadence for this – it allowed us enough data to make good decisions, but short enough timeframes to meaningfully iterate.
    • We standardized code tests with checklists of what we were looking for, what was necessary, what was nice to have. This also helps us give better feedback.
    • At Automattic, everyone who is hired does a (paid) trial project where we work together to determine mutual fit. We treated our trial projects as a pre-onboarding. Every new hire has completed a shippable feature and has meaningful interactions with at least three people on the team.
    • Previously, onboarding had been inconsistent and hit-or-miss. We got serious about onboarding, identifying good first projects and teams, and working to make sure every new hire felt welcome and set up to succeed.

    Successes

    • 31% of our new hires are women.
    • We added teammates in six new countries: Chile, Turkey, Germany, Serbia, Hong Kong, and Ireland.
    • 63% of new hires speak English as a second language.
    • We added three languages to the ten already spoken on the team (helpful for internationalization!): Hebrew, Serbian, and Polish.
    • Outreach:
      • WordCamps – we presented at WordCamps in Montevideo, Montreal, and Taipei, as well as WCEU and WCUS.
      • People from the team also presented at various local meet-ups and ThatConference.
      • We hosted a Women’s Brunch at 360AnDev.
      • I did my usual slate of presentations and started writing for Quartz.
      • Eli (the new mobile lead) and I did a webinar with Women Who Code in both English and Spanish!
      • I did an interview with GitPrime about our hiring and onboarding process, and Amanda followed up by sharing her own experience.

    Areas for Improvement

    Whilst we’re pleased with the progress we made in phase 1, it’s clear we have more work to do. 2019 marks the start of phase 2, where we will be focusing on:

    • Racial diversity.
    • Under-represented geographies based on our user base: APAC and Brazil in particular.
    • LGBT.
    • Gender diversity.

    We’re also keen to take advantage of the openness that working in Open Source allows – so we’re supporting our teammates in sharing more about their work online and IRL at events.

    If you liked this post, you might also like being part of our team: we’re hiring.


  • Towards Productive Technical Discussions

    Towards Productive Technical Discussions

    Note: I wrote this post for an internal team blog, but thought it was worth sharing more widely.

    wool-2197757_1920.jpg
    Credit: Pixabay / congerdesign

    Part of getting to good code reviews is some up front discussion about trade-offs and implications for bigger architectural changes. I think of code review as when “my” code becomes “our” code – for architecture, those conversations need to start earlier. We all live with it, decisions have consequences beyond the project we are currently working on, and it has a huge impact on our ability to execute over time.

    Some things to think about when giving feedback:

    Ask questions. If it’s not clear to you 1) it’s probably not just you 2) it’s still worth clarifying.

    Think further out. How does the proposal affect things in 6 months? 12? We might choose a shorter term option, but we should make a mindful choice.

    Consider the effort vs the impact. I think this is a really important skill as an engineer or designer that I expect everyone on the team to have some sense of. We hire experienced people who we can trust to be autonomous, and I think this skill is pretty critical to that level of trust and autonomy.

    Don’t nitpick. Small details are distracting. Big picture feedback is more important. If something is a nitpick, clearly mark it as such – and then consider whether it’s worth nitpicking at all. When that nitpicking can be automated, let’s do that. It’s fine to be reminded by a script. It’s not a good use of anyone’s time to be reminded by another human.

    Style guides. It’s easy to have opinion on style, but consistency is more impactful than the details of it. The purpose of a style guide is to never discuss it again. Every other discussion should focus on the substance of what is being proposed, not style.

    We need to be less afraid to give people feedback in general. Technical feedback is a great place to start since 1) that is our focus 2) it is not personal. You can question and critique someone’s idea or proposal without attacking them as a person, and being able to have our ideas and proposals critiqued without taking it personally is important for any professional. We don’t have to agree with each other on everything in order to treat each other with consideration and respect.

     

    Some things to think about when asking for feedback:

    Put it in the right place. Small changes are best discussed in PRs. Bigger changes are for the internal blog (but as an OSS project should be in the README architecture document once decided).

    Be clear about the problem you’re addressing. This is really helpful context for people to understand where you’re coming from.

    Explain why it’s important. Make a case for the impact, and why now.

    Talk about what you’ve considered. What are the alternatives and their tradeoffs? Why do you think this is the best option?

    Think about the kind of feedback you want. What would be most helpful? What might other people have more knowledge of?

    Be clear on next steps. When do you need to make a decision? What do you expect to happen next? Who do you need to agree / help?

    Making Decisions

    The goal of these discussions is to define a path forward, and they should end with a specific decision which we then act on. Non-decision decisions* are a common dysfunction that I strongly prefer we avoid. Have some back and forth, switch to a call if necessary, but at the end of the thread there should be a decision and some next actions. Review the feedback, answer the questions, and then based on that, circle back, summarize, and state the decision.

    If the thread has been productive, and people feel heard, this might still feel scary but at this point we have all explained our point of view, and should be willing to accept the outcome.

    * Non-decision decisions: where a decision is made by not making a decision.

  • Whose Expectations are Those, Anyway?

    Whose Expectations are Those, Anyway?

    This is part 1 of a series of blog posts based on a talk I prepared called Successfully Derailed Product. It’s about the ways in which we define and talk about “success” influence what – and how – we build.

     

    raccoon
    Credit: ToRange

    There used to be a joke at a company I worked for that went “how many test frameworks do we have” and the answer was “how many SET5s do we have?” It was “funny” because an SET was a software engineer in test, and to get promoted to Level 5 they would have… written a test framework.

    How often have you have seen those kind of things? Where the things that get incentivised for individual success turn out to be a joke at scale? Because clearly when it comes to testing frameworks, more is not better. It’s pretty orthogonal to the goals of testing – which are generally around continually shipping with confidence.

    This isn’t to say that promotion processes are inherently bad, or that individuals shouldn’t desire and work towards professional advancement. Just that the processes and goals that we define profoundly affect our organisations, the environment it creates for people who work there, and the things we are able to ship as a result. Your processes define your culture, and your organisational dysfunctions show up in what you ship and when you ship it.

    This isn’t to say that goals are bad. Goals are good… it’s well documented that we make more progress when we know what we’re aiming for. But if we set the wrong goals, or we set goals that aren’t compatible, then what? And when we agree on the goals we should be setting… are they supported or sabotaged by our processes?

    Let’s talk about what “success” even is. Take a moment, and think about some goal in your life. What is it? (Leave it in the comments or tweet at me).


    Do you have something in mind? Now I want you to think about where it came from.


    Hard part over: how do you measure it and how do you report on it?


    Example 1: I have a goal of increasing the monthly actives in the app. My boss gave it to me. I measure progress on it using analytics and report on it every two weeks.


    Example 2: I have a goal of clarifying the “vision” for my team. I got this from my team in various ways – surveys / direct feedback about this being something people want. I measure it quantifiably using surveys, and less quantifiably from the kind of questions that get asked in our monthly townhalls or in the regular skip 1:1s I have with everyone on the team. I report on it quarterly – in that we have a document outlining the longer term plan for the team, and this is how often it gets updated.


    There’s a framework by Gretchen Rubin on how people respond to expectations, called the Four Tendencies. She describes it in Better than Before (Amazon) and goes into more depth in The Four Tendencies (Amazon). Essentially, there are four ways in which people respond to expectations.

    Obligers respond to expectations from other people. They struggle meeting their own expectations.

    Upholders respond to all expectations – including those they define themselves.

    Questioners question all expectations, and respond only to expectations they think make sense.

    Rebels resist all expectations.

    https://twitter.com/alexisylchan/status/975048974032814086
    Obliger Goals, 2018

    So how does this relate to goals? Well obligers probably got their goals from other people, upholders might be making great progress on things they don’t actually want, questioners are trying to ignore things they can’t make sense of, and rebels are opting out of the very thought.

    Meanwhile, obligers often feel unappreciated because they’re so busy putting other people ahead of themselves they can’t get their own stuff done. Upholders don’t understand why people don’t just do what they are asked or say they will do without complaining or asking so many questions. Questioners are annoyed by all the arbitrary things that other people want (and also, ironically, by being questioned) and rebels just want to be free to do whatever they feel like and resent all the interference.

    All these things are playing out around us. But a lot of the time we don’t have a way to articulate it so we don’t talk about it.

    Currently, I manage five managers, and we started talking about it towards the end of last year, in part because reading the book I realised that I was not great at managing obligers. I’m a questioner, and I was completely mystified by the behaviour of taking on arbitrary things and then resenting them. So you know, an obliger gets overwhelmed, and my response is along the lines of “why are you doing that anyway”, which, you know, they don’t find helpful… and then they feel resentful and I feel confused. It’s great working with obligers because they are so nice and helpful. But because of that it’s very easy for people to inadvertently create expectations and take advantage of them. Meanwhile upholders can lack empathy for people who aren’t as effective. This gave us a shared language to talk about how we are creating and responding to expectations with each other.

    On a more organisational or social level, there’s an idea called Campbell’s law.

    “The more any quantitative social indicator is used for social decision-making, the more subject it will be to corruption pressures and the more apt it will be to distort and corrupt the social processes it is intended to monitor.”

    ~Campbell’s Law

    Bit abstract, right? A good example of teaching to test. Standardized testing can work for measuring attainment, but once students are taught to pass the test, both the teaching and the test lose value.

    You can think about this in terms of promotion processes. You define a system which makes sense, but then people work to the system, and both the work and the system become less useful.

    Another place you can see this is the tension around shipping culture and something that might be called a “quality culture”. When you define a process to incentivise shipping, shipping becomes the goal and what is actually shipped tends to become secondary – and not very good. Then in a “quality culture” the quality is the most important thing, and so nothing gets shipped at all…

    …But if it does ship, it will be perfect.

    animal-black-and-white-fence-160709
    Credit: Pixabay

    (As an aside, this is why I like to talk about shipping as a habit rather than as the goal itself. I think this is something where release cycles help, because it can force shipping on a cadence rather than shipping specific things).

    One way to phrase Campbell’s law is that we work on the definition of the thing. And the result is that definition is probably nonsense.

    I find all this pretty fascinating, but what does it all mean? How do these things connect? Well when we define systems, we create incentives – or expectations. Individuals take these expectations and it influences their goals (even if they’re rebels – just in the opposite way).

    Essentially – defining systems is fraught with risk of derailment, because teams are not made up of rational actors, but rather: people.

    What’s next? A look at the way individuals define success.

  • One Year as 📱👑

    One Year as 📱👑

    One year ago today, I tweeted:

    Three weeks after that, when my support rotation ended…

    As I recall, my friend James described it as “the most low key new job tweet”. I pointed out the extremely descriptive emoji for my job title, and he said “I felt both enlightened and informed”.

    I think he was being sarcastic.

    I hear the thing to do is to write one of those omg I have a new job and I’m so excited posts but that’s not my style. Not that I wasn’t excited – I was, I still am – but it always seems a bit dangerous to be excited in public about something I haven’t proved I can do yet.

    In the final year of my undergrad, I was a teaching assistant. I remember this dude from my course – I don’t think I knew his name at the time, and if I did it’s long forgotten now – said “why are you a TA?”

    Just the usual drive by misogyny, I guess. But it’s the kind of question I worry about, the kind that I don’t want to invite (where invite is… showing up and doing my job?) until I have a good answer for it myself.

    And the timing. I was coming into this out of a failed startup. I’d taken ~6 weeks between finishing my job search and starting, and gone all the way to Tuvalu to escape everything. I was still kinda wrung out from that experience. The US election results came in, and the world seemed to be ending. I finally believed Brexit would happen. It didn’t seem like a time to be excited about things at all, let alone in public.

    Anyway, I started with three weeks in support. This was eye-opening, as I saw the ways in which the app was confusing and failing our users. The queue was embarrassingly long, I worked on better FAQ answers, trying to get better, faster, answers to the people who had a simple question that they should never have needed to ask at all. It is weird, and more than a bit intimidating, to start in a job that I didn’t apply for and didn’t think I would be good at. But perhaps that’s the point – I learned a lot.

    My job title was emoji for a reason. A way to own my responsibilities, but in a cute, not-too-threatening way. Finished in support, I am the 📱👑. There were three teams, with three leads. I was somehow responsible for all of it. I spent a lot of time listening, making sense of things. I knew people were nervous about change, so worked to be accessible and transparent. Trying to turn a disconnected non-team into a high performing one. My first two weeks as 📱👑, I did a 1:1 with every person on the team, and flew from Buenos Aires to Philadelphia for WCUS where I met Matt (the CEO, who had recruited me) and one of the team leads for the first time. The lead – Will – and I ran user tests together. Saw in real life some of those things I saw in support.

    I took all this information and tried to figure out where to start. What is a symptom, and what is a cause? 

    Some time in December, I cried and allowed myself to question if I had made the right decision.

    I put that question in a box and kept going.

    • We clarified the purpose of each project and started talking about timeframes.
    • We started doing daily standups.
    • We revamped our bi-weekly updates (now with more emoji).
    • We defined new projects that put user benefit at the centre.
    • We took a hard look at the ways we were failing users.
    • We shipped something.
    • We started talking about user empathy – we challenged ourselves to use the app as a user would.
    • An engineer got so annoyed by a piece of terrible UX we called “the seven item monstrocity”, he prototyped a new media picker experience over a weekend.
    • We changed up team leadership to have five teams, including a design team.
    • We set better standards around clarity, feedback, and 1:1s.
    • We thought about on-boarding, and defined a process for it.
    • We shipped again.
    • We worked to make the leads a team.
    • We were moved out to become our own division, with me reporting to Matt.
    • We failed. But this time we talked about it.
    • We shipped more.
    • We worked to be more accountable – to each other, and the wider organisation.
    • We kept shipping.
    • We revamped our hiring process, and opened it up again.
    • Ship. Ship. Ship.

    At some point… we became a team. When we got together at the Grand Meetup, it was really noticeable. We did an exercise called “Plusses and Deltas”, the plusses were things we had worked so hard on. The deltas included things that really showed how far we’d come.

    Our design lead wrote about the process of building the design team, and I love it because it captures something of the hard work, and where we are now compared to where we started.

    For me, I learned how to onboard and ramp up new managers. I levelled up my communication and coaching. I invested in getting better at product. I conducted interviews via text for the first time. I made ever more elaborate spreadsheets as I got further away from writing code. I got better at setting an example then letting things go. I reached new limits of how much I can get done in a week. I made hard decisions, and I had hard conversations, and I got better at both of them. I experienced that when you help a manager level up, a team levels up, and it was amazing. I built relationships with my peers and appreciated the difference that makes. 

    The past year has been brutal. Exhausting, challenging… I’ve had my share of moments of doubt. But I work with people I really like, at the intersection of things (mobile, writing, open source) that I love. I wouldn’t change it for anything… so bring it on, year two.

     

  • I Send Love Letters from Airports

    I Send Love Letters from Airports

    eiffel_tower January 3, 2016, I sent an email to 66 friends from CGD. In it, I wrote about falling in love with the Eiffel tower, spinning around in circles, and the entwined history of luggage and travel. Capture-d’écran-2017-07-27-à-21.18.24 July 1, 2017, another email from CDG. This time to 322 people. I wrote about an early morning walk through Paris, about going between a social whirl and being alone. In between, 70 of these. Postcards, love letters, something in between. I call it “Where the Hell is Cate”. It is an art project, an embracing of the transient, a map of the path taken, a musing on the in between. Most of them from airports, two of them from shipping ports. One from a train station. The subject line just the code. A handful sent from places. A letter from Pablo Escobar’s abandoned mansion, the one with the hippos (Hacienda Nápoles). In one I told the story of the kettle I left in Australia… I called it “Home”. Capture-d’écran-2017-07-27-à-21.19.53 There’s a format. One picture – I’ve found I look at the world, experience photography differently, when I am trying to pick out only one. One favourite thing – a reminder to find the unique experience, the best moment of appreciation in every place. An essay. In the first letter I included this idea of “unexpected joy”. When I flew out of LHR after the Brexit vote, I forgot to find the piece of happiness. When I arrived at EZE still shaken from seeing a corpse on the street the night before I had nothing else to say. When I flew out of BUD, I shared a cab with a random woman, who turned out to be a friend of a friend and there was no essay. Each exception has it’s own story. Capture-d’écran-2017-07-27-à-21.20.05 When you travel a lot, especially when you travel a lot for work, it’s easy for everything to blur, to lose sight of what you love about it, to decide to explore next time rather than right now. The act of choosing a favourite thing, the act of appreciation, connects me to the place and time. mountain Sometimes it’s easy. When I saw a giant sea turtle lay eggs in the middle of the night (SJO). Or when I edged around a rubbish dump, walked along an abandoned runway, and found myself standing on an abandoned WWII lookout point at the edge of an island that felt like the edge of the world (FUN). When my friends and I snagged last minute tickets to the Harry Potter play (LHR). Sometimes it’s hard to choose or describe. The river of five colors (LMC). Guatapé, the view from the top of El Penol, or the beautiful, eerie, abandoned La Manuela. The owl cafe – or the hedgehog cafe – or the bunny cafe (HND). The aquarium, or finally seeing the DMZ from the other side (ICN). The month I spent skiing every morning before work (TCL). My birthday adventure (MXP). tokyo And sometimes it’s hard to find a moment of joy. When the startup I was working at failed, and I packed up my life (MDE). When I said goodbye to my east coast home (EWR). When I was being stalked and threatened (SEA). When I visited the ghost of the life I left behind (SYD). It’s easy to start selling on social media. Selling an idea of a life we’re not really living. We’re not really that happy, or that angry, or that good– not all the time – life is made up mostly of in betweens. A blog post always needs a point. A thing to take away. I need to succeed in public, on the internet. As my “followers” have ticked upwards, my ability to be myself has slid down. My photo blog would lead you to believe I lead a charmed life – and in many ways I do – but the nuances of that are more safely explored in another place, without a character limit, or a “like” button. A place to be imperfect, and incomplete. grover At the end of each one, I include a postscript. Capture-d’écran-2017-07-27-à-21.28.40 guatapePeople write back. By email. By Twitter. By iMessage. By GChat. In person. They join me on my adventure as it ends, or sometimes weeks later – that’s the nature of email. Sometimes people write me an airport goodbye, as they begin – or end – an adventure of their own. Often these are my “IRL friends”, the reason why this started, who I’m closer to as a result. We plan our next adventure, and exchange snippets about our lives. The burden of keeping a correspondence is high, and so we embraced the “ambient awareness” of social media. But this project has created a new kind of space, where we correspond without pressure, and we know there will always be this prompt to resume. Another airport. Another adventure. Another story. Another goodbye. Capture-d’écran-2017-07-27-à-21.32.21 Sometimes they are internet friends. I went straight from ORD to meet friends for dinner. One of them had hired a designer, given her a brief, and made stickers. She put them in a card, with a lovely message. It was the most beautiful thing that anyone has ever done for me, and this project – that grew out of postcards I sent my friends – was paper once again. stickersAnd sometimes they are strangers. One of them called me his “imaginary friend”. Another wrote me this:
    “First, you talk about feeling a sense of gratitude for people who go first. The implication seems to be that you don’t, but I disagree. The fact that you let strangers into your life via these personal updates is very “Where the Hell is Cate?” to the point where I have to remind myself that it is, in fact, a very asymmetric friendship.”
    And one of them, went from a friend of a friend to being my boss. She forwarded him a letter. He subscribed. As my last job ended, he reached out. london I created this project to stay in touch with my friends, to create a space to be real – vulnerable – long form. Whilst it hasn’t grown in scope, the meaning has grown beyond what I ever imagined. It’s given me a different format, helped me grow as a storyteller and a writer. It’s prompted me to step back and see how I’ve grown as a person. nyc There are three letters total from CDG. The first, the most recent, and one other. In that one, I talk about how I found my friend Natasha at the Gare Du Nord. I sent a letter from SXP and she realized we were both on trains, heading to the same place, at the same time. We got something to eat, and walked underneath the Eiffel tower and along the Seine to the miniature Statue of Liberty. Now she’s in Thailand, and I’m in Colombia. But soon, we’ll be reunited in NYC. And she’ll know I’m coming, because I’ll send an email with subject: MDE. tuvalu
  • Running an Effective Mobile Team, Part 1

    Running an Effective Mobile Team, Part 1

    Shopping Cart Shopping Cat Figures Curious Danbo
    Credit : Max Pixel

    When talking about team effectiveness, the first thing to consider is what an effective team looks like.

    Predictable. The team has a regular cadence. They can set goals and expectations around deadlines.

    Clear on priorities. When you ask people what is most important and why, they can answer.

    Connected. People work together and take an interest in each other (this doesn’t mean everyone has to be friends – but they are friendly).

    Automated. Time has been invested to automate repetitive tasks, reducing the number and amount of time spent on “team chores”.

    Accountable. People can have expectations of each other. This includes leadership.

    What constraints do we have on mobile that effect these things?

    • We ship compiled code. No backseys.
    • Leadership is often dominated by iOS users, so Android can feel like an afterthought.
    • We lack a clear model for mobile infrastructure. This is one of the things that makes the question of whether to have a mobile team or pods hard.
    • Testing infrastructure is behind. Android was untestable by design. Still find things like jacoco (test coverage) doesn’t work with expresso (UI testing) out of the box. As apps got bigger, we need to consider architecture in a way we didn’t have to before.
    • Often these things result in mobile being a bit disconnected. Server side changes can break clients, and then mobile teams take the heat from users and leadership. This can lead to resentment, which makes accountability hard.

    Often people look to technical solutions for this. They think that the mobile team could move faster if they just adopted some latest new shiney, like, say, ReactNative.

    But…

    • We still have to ship that code. Adding more dependencies means you have to debug them (and increases build times).
    • We still have to have the app infrastructure… UI code is just a small part of the problem.
    • That UI code still has to look right and perform well on both platforms.
    • We still have the same problems with testing, but now the CI server takes even longer.
    • Teams will resist accountability for a strategy that they don’t buy into.

    I’m kinda hating on React Native here. For some teams it makes sense. Artsy wrote about how they use it for an API driven iOS app, which was interesting. So basically if your app mainly displays content. It may not make sense if you:

    • Need a great offline experience.
    • Interact heavily with platform APIs (e.g. media etc).
    • Have reasons to really care about good performance. E.g. text editing, or large amounts of data (notably all the issues here are performance issues that don’t arise natively using standard good practises).

    Whilst the Artsy article made a decent case for iOS in certain circumstances, it’s not a good case study for a genuinely x-platform experience.

    In the long run, we hope to extend this way of working as we start work on a React Native Android client.

    To really shine with React Native, you need native experience. JavaScript has not eaten everything yet. However, you don’t need a team of native experts. For example, we expect to be able to get quite far with Android support based on our work in React Native, but to make it amazing, we will need someone with history and context in the space.

    Android has some different performance issues, so I wasn’t surprised to see this comment in an otherwise glowing report about ReactNative on iOS.

    Unfortunately Android devices have much greater variance in performance and tend to trail significantly behind iOS. We were able to get our app running fairly quickly, but the performance — specifically on touch events was not at an acceptable level even on higher end devices. In addition at that early stage there was still a lot missing in the React Native Android feature-set that would have made getting our prototype to production level more time consuming than our iOS effort.

    So if React Native isn’t the answer, what is?

    The issues facing most mobile teams are not technical, they are personal. If you are the size of Facebook or Google, you can afford to try and create technical solutions to social problems. The rest of us can’t.

    This series continues next week – we’ll cover creating predictability on a mobile team.