Why We Still Need Girls Learning Code Events

A group of girls and parents sit at laptops in front of a projector screen learning HTML/CSS.
Girls Who Code Workshop, 2017.

I had the great experience of mentoring at Girls Learning Code event this weekend. The event was for girls aged 8-13 and their parents to learn HTML/CSS and build a website in one day. One of their core beliefs that I really support is that they don’t want to make it seem strange that girls are coding—they just want to show them how to do it.

I was really excited to be a part of this event for a number of reasons. I have always enjoyed teaching (my English degree was originally setting me up for teacher’s college). I have been a coach/trainer/captain for horseback riding, soccer, and ultimate frisbee since I was a teenager. I was one of the first captains of our first women’s league with my local ultimate league.

I love teaching/coaching everyone, but I’ve found it particularly rewarding to work with women and girls.

To bring it back to technology, I taught myself how to code, and when I did have the opportunity to take both a computer engineering class and a computer programming class in high school, I was the only girl there every year. In my career, I have often been singled out for being a woman working in tech, especially once I moved into a management role—I once had an HR manager tell me I was her favourite because I counted favourably in her diversity statistics.

At the event today, I worked with a 10-year-old girl and her 7-year-old brother who was also attending. I didn’t want him to feel left out any more than I wanted any of the girls to feel left out, so I made sure he also had a laptop so he could participate. Both kids were great, but I couldn’t get over the microcosm I experienced in one afternoon of some of the underlying issues I see with getting girls into equal roles with boys.

Attention

This is definitely in part because of the age difference, but the boy needed a lot of more of my attention, and he was not afraid to demand it of me. It took more effort to keep him focused on the task, and he spoke up quickly to ask questions. The girl was much quicker to pick up concepts, and much quieter. It took about an hour before she would shyly ask me anything, and, even then, it was usually me pushing her to try different things as we built her website.

Showing Off

When the day was over, the girls were invited to put their website on the big screen for everyone to see. The girl I was working with was adamant that she did not want to go up in front of the group, despite encouragement from me and her dad, multiple times. Her dad asked her brother once and his response was “YES!”

Now, there is absolutely nothing wrong with either reaction. And there were lots of other girls there who couldn’t wait to show the group what they had created. But that moment of not wanting to stand up and be proud of what she had done hit me hard. This video from content creator and author, Louise Pentland states a similar experience:

I often find myself downplaying my technical skills by saying things like “I’m not a developer” or “I’m really a content person,” or by explaining my job to people who don’t understand the industry by comparing it to more traditional editorial roles at a newspaper or magazine. But the truth is I have a lot of technical skills, and years of experience behind them, and there’s no one holding me back from saying that but myself.

Adult Commentary

This is an area I try particularly hard to correct in myself. The kids’ dad (who was also great), made a comment about how his daughter wanted to be a vet, but “you know, you have to be a very strong person to do the difficult side of that job.”

Now, I have no idea what kind of conversations he might have had with his daughter to reach the conclusion that being a vet might not be for her. But I do know that when I was a bit older than she was, I wanted to be a vet too. I even went on a co-op trial day at a veterinary clinic. That’s “trial day” because I discovered that I definitely did not have the stomach for surgery that day when I almost passed out from the smell alone. I told them that story, but I also told them about my amazing cousin Katy, who is a vet tech, and is most certainly strong enough to do all aspects of animal care.

After the event, I stopped at the mall to pick up something, and as I was walking through, I passed a little girl running ahead of her family holding a shopping bag. Her (presumably) grandmother saw me smile at her and commented, “you have to teach them young!”

And that’s why we need to keep having events like Girls Learning Code. Because the ways we shape girls’ perspectives about their worth and their potential are subtle and pervasive, and most people don’t even realize they are doing it.

Does Your User Testing Include Technology Profiles?

As I went through user testing for my first app build, one of the fundamental questions I asked (and you should too) was “is an app the right thing for our users?”

There are generally two sides to this debate: everyone needs an app vs. UGH, stop building useless apps. During the discovery process and in the months since our deployment, I’ve solidly been on Team No App for my current clients. I believe our energy is better spent adding functionality and useability to our sites when accessed via mobile devices. Anecdotally, the web professionals in my network are generally against apps in our personal use as well. Yet Yahoo’s Flurry reports that 90% of mobile media time is spent using apps vs. browsers.

This got me thinking about the different user profiles we can consider when it comes to use and comfort with technology. Consider these personas the next time you’re doing user testing.

Child of the ’90s 

This person places a high value on bandwith and storage because they lived in the time where there was a huge cost to both. They tend to be a bit more forgiving of slow load speeds and functionality as a tradeoff to downloading your app, but give them a smart, bare bones mobile site version and they will be exceptionally loyal.

This person has automatic updates turned off, which means they will wait two or three versions by the time they jump onto the wifi and update the 56 pending updates. Okay fine, this person is me.

Screen capture of Google Play updates screen.
Not even close to the total number of pending updates on my mobile device.

True Millennial

Tech-savvy and impatient, this person wants the easiest, fastest experience. They update apps automatically, and they always have the latest mobile device so storage is never an issue. Apps are easier, so as long as that user experience does what it should, they are on board.

This person never cleans out old apps, and will have no tolerance for how slow your mobile site loads, or if the functionality is not as robust as your app or desktop version.

Won’t Be Left Behind

Your parents or even grandparents might belong to this user testing group. They are not even close to as tech-ignorant as they were even five years ago. Now, they Tweet, Facebook and maybe even Snap alongside you, as long as none of the buttons move in your layout. This group has no problem with using apps (they are easier) and will wait for wifi to use them.

Hopefully you are already doing accessibility testing, but this user group is a great example of how good accessibility makes for better design for all of your users. Consider your design from the point of view of that grandparent holding their iPad two feet out from their face while trying to single-finger type on the virtual keyboard and the changes you make will no doubt help everyone.

4 Things You Didn’t Know About The Web

The digital world operates in its own timezone and it can feel hard to keep up. These quick facts point to important trends in our industry and we all need to strive to do better.

1. “If your site takes more than 3 seconds to load, users will abandon loading it.” @yeseniaa

Ready to feel old? According to Craig Hyde, CEO of Rigor, the size of a web page today is about the same size as an MP3 file. Do you remember how long it used to take to download a single MP3? I do.

Fast sites build trust, and slow-loading sites are abandoned. According to the New York Times, if your competitor loads 250 milliseconds faster, users will use that. In fact a mere 160kb added to page weight meant a 12% increase in bounce rate on Etsy.com for mobile users (source).

2. “There are 8 billion mobile devices in the world today.” @beep

Think about the last time you purchased something online. If you think about it, I’m betting you may have checked it out on your laptop, maybe compared places to buy from on your tablet, and maybe finally pulled the trigger from your mobile device while you were waiting for the bus. More than 40% of all online U.S. users start an activity on one screen and finish it on another.

More and more, users are becoming intolerant to differences in experience between accessing your digital product. As digital designers, we no longer have the luxury of not holding every channel we manage to the same standard. We cannot rely on driving users to our preferred platform. As Jeffrey Zeldman says, “No one wants to download your app when they come to your website.”

3. UK.gov saved £1.8 billion in support costs by redoing their digital knowledge base. (source)

Every time Walmart can reduce their page load time by 1 second, they see a 2% increase in conversions. On the other hand, Amazon loses $1.6 billion if their pages load one second slower.

Good websites save money. Efficient and user-driven content strategies mean an easy interaction for your users with your brand, and that directly affects your company’s bottom line. Keep that in mind when you’re deciding who you want to run those properties and when you’re pitching digital projects to your upper management.

4. Microsoft.com has 15 million pages, 4 million of which have never been visited.

Websites are not document repository systems – over and over I have this debate. It is easy to fall prey to the idea of putting something on the website “just in case someone needs it” but this is how we end up with cluttered, unfocused content.

Suspiciously, more often than not the “just in case” content is a PDF. Karen McGrane calls PDFs “content blobs” – not responsive, not searchable, not accessible, and ultimately, not truly digital. PDFs are essentially content coffins; if there is valuable content inside your PDFs, bring it out and make it useful.

3 Things I Learned At An Event Apart Boston

The 2016 An Event Apart lunchbox.

The 2016 An Event Apart lunchbox.I was lucky enough to attend An Event Apart (Boston, #aeabos, this time) for the third year in a row this week. Once again, it was a great experience: industry-leading speakers, engaging content, and only one very loud venue emergency alarm (everything was fine!).

It sounds corny, but I really do look forward to this event every year. It’s remarkably comforting to spend time with hundreds of other people who get the web. From the Javascript debugging happening out loud at the breakfast tables to the appropriate audience gasp when a speaker points out that IE8 loads every imported font, even those that aren’t used.

I always learn so much every year, but here are a few of the themes I took away:

  1. Honour Thy User
    The biggest lesson I learn again and again in my work is that the user is always right (even when they do very, very strange things). Users are flooded with information and choice – if you don’t serve them a) what they are looking for and b) what you set them up to expect, they will hightail it back to Google for another option. Identify the core goal of a user of your site and then value what your user wants to do. Or, as Jeremy Keith put it:

    1. Identify the core function of the product
    2. Determine the base level of technology you can use to deliver the core function
    3. Enhance!

    Be critical about your site – if you are a news site, what’s the most basic way you can deliver your core user goal (reading the news)? It seems simple, but I’ve found spending the time to clearly identify and agree on what that user goal is will help simplify all of the choices you make going forward.

    I find the “staggered” (progressive, but deliberately so) load strategy really interesting. My bank actually does this (unintentionally, I believe) on their homepage but, unfortunately, one of the last events to fire resets the form input for your card number, which means every time I end up typing in half a number, having the page erase it, then typing it again.

    “No one wants to download your app when they come to your website.” @zeldman

    Jeffrey Zeldman nails it again. As a member of Team No App (yes, I know I’m in the minority), I will try every possible avenue to avoid downloading your app. I don’t want it. But more than that, I want to be met where I’m at and interact with your product the way I choose.

    This is a lesson I reinforce with my social media team all of the time: if they tweeted a question, don’t answer by asking them to email us. And in my favourite example of this, don’t answer a tweet about a lost cell phone by asking them to call us (yes, that really happened).

  2. Be A Good Ancestor

    “We need to be good ancestors and leave behind a web that’s resilient and will last.” @adactio

    This idea really resonated with me as my team grows. How can we make good decisions now that our future selves (or future members of our team) won’t curse us for? Of course, the concept of future-proofing and/or progressive enhancement fits the bill here, but we need to also consider the not so fun but highly necessary need for documentation. Call it a style guide or a pattern library, but aspire to build something like Mailchimp, Starbucks or Devbridge Group, which is my new favourite example.

    I know, I know – you’re creating a website to document the needs of your website. But putting in the effort here will save you from inconsistencies and hours of unnecessary cleanup. Whether you’re a team of 30 or running the show solo, this exercise is incredibly valuable for putting thought into your daily decisions.

  3. What If Someone Doesn’t Use The Web Like I Do?
    Ethan Marcotte posed this question, and it came up thematically in a number of ways. At this point, he was explaining the importance of respecting the content hierarchy in the HTML, regardless of how it appears once styled. As beautiful as your design might be, a screenreader needs to find the content in the shortest and easiest way possible. Or, if your enhancements fail to load, your content will still be visible and easy to comprehend.Eric Meyer spoke about this topic through the lens of Compassionate Design. Most of us can probably think of a time when a form asked us a question that incited a very personal reaction. How about a question about gender that doesn’t offer a chance for you to respond with the term you prefer? Or a question about marital status for someone who is recently separated from their spouse? We make a lot of assumptions about our users, but if we take just a little time to consider different perspectives, our word and design choices can be kinder and more aware.Josh Clark approached this with the idea of calm technology – something I’ve been thinking about lately but didn’t have a term for. I don’t think we’re addicted to our devices; we’re addicted to the connection with and flow of information.

    The goal is to deliver on a real human need. Not just to make things talk but to improve the conversation. Design calm technology that doesn’t vy for our attention, but instead helps to enhance what you’re already doing. Move data gently rather than making it a constant nag. Make screens caption our lives instead of frame them.

    I couldn’t have put it better. It’s the reason I get uncomfortable when we talk about the applications of Beacon technology – I worry we’ll limit ourselves to pushing context-aware ads and miss the opportunities to create real change for how someone lives.

I can’t wait for next year. If you’re so inclined, I tweeted like a mad person during the conference.

Guest Lecture Alert – Digital Voice and Tone at George Brown College

King Street entrance of George Brown College in Toronto where I'll be lecturing about digital voice and tone.I’ll be guest-lecturing at George Brown College this week as part of their Entrepreneurship course in their Continuing Education program.

I’ll be covering how to create a digital voice including:

  • What the heck is a digital voice and why do you need one?
  • How do you create a digital voice?
  • How do you maintain a digital voice?

I will post my notes after the lecture. Hope to see you there!

Speaking at the AAAE/Sixel Airport Digital Summit Conference

I had the pleasure of speaking at the AAAE/Sixel Airport Digital Media Summit Conference (#RDUDigital) in Raleigh, North Carolina at the end of September.

I gave a case study on a digital response for an international airport, which included web, social, architecture and app. It was great to meet airport communications, marketing and digital people from all over the U.S. Special thanks to Raleigh Airport for hosting!

On stage at the Airport Digital Summit.
Speaking at AAAE/Sixel Airport Digital Summit

Simple and Searchable: Improve Your Page Titles

Stick figure making a confused face.

I was going about my regular morning on the internet, as you do, and I found this example of a constant problem I see – the difference between how a content creator (company or organization) will name something, vs. how a user will search for it. What comes to your mind when you see:

Availability Guide

If you’re like me, you probably make this face:

Stick figure making a confused face.

 

To be fair, in search results the full page title is: Availability guide | Foodland Ontario

Screen capture of the Google search result showing the Availability Guide from Foodland Ontario.

But on the page itself, while the logo informs that name, the page title is divorced from that sole indicator as to what this page is about.

Screen capture of Foodland Ontario's Availablity Guide page.

 

Here’s my point. I actually really like this page overall. It is slick, appropriately uses a hero image (what a wonder!), minimal text and an appropriate graphic to easily show what foods are in season when (which is what “Availability Guide” apparently means). And this page does appear readily in Google results even though I search something completely different each time I want to get to this page. But why make it more difficult than it needs to be?

This title reeks of multiple approval levels. I would love to see what search results actually drive people to the page, but I suspect it would be something like “What foods are in season” or “is X in season”. Changing the page title to “What Foods Are In Season In Ontario” or even “What’s In Season: Ontario Food Availability Guide” something similar that was (and this is the crucial part) informed by the search queries people are using, it would simply this page and drive additional search results with minimal effort.

Keep it simple – if you can’t tell what the page is about from your page title, your page title needs work. If your page title doesn’t consider how the user will be looking for this information, your page title needs work.

Now back to my grocery planning!

3 Things I Learned at An Event Apart Chicago

It’s #aneventapart time again! This year, I picked An Event Apart Chicago to attend because I’ve never been to the city and because the A Day Apart workshop was put on by Karen McGrane and Ethan Marcotte. I would listen to them teach how to dust properly, but the workshop actually focused on Responsive Design, which I’m about to undertake with my main client. If you haven’t been to An Event Apart, I can’t recommend it highly enough. I learn more there than I do all year. I took eleven pages of notes, but here are the top takeaways I will be able to immediately use:

  1. “The customer is no longer King – they are Dictator.”Gerry McGovernThis was my first time hearing Gerry McGovern speak, and he was excellent (plus the accent adds +10 to the entertainment factor). This quote echoes another one I heard last year at An Event Apart Orlando – your users will decide how they want to use your site; you have no say. I see this all of the time with my clients – the internal expectation is that a user will follow your navigation from top down, yet so many simply google the business name and the search term and bypass your information architecture altogether.

    It’s amazing how many clients seem to want to hide the meat of their content inside a lot of words, buried far down the page, or deeper in the IA. This is something I encounter with students as well – there’s an urge to really spend a lot of time and characters setting up the conclusion, instead of leading the strongest information. Don’t make your users work for the information because they won’t – they will simply go to Google.

  2. “Responsive design won’t fix your content problem.”Karen McGraneHallelujah. During An Event Apart Chicago’s A Day Apart, Karen walked us through some high level steps to take when moving to a responsive design. She suggests that a content reduction of 60-75% isn’t uncommon, and I completely agree. So much content makes it to the site as either an archive function (put it there just in case) or without ever putting it through the test of “is this valuable to the user or does it just check a box for us”.

    Doing a content audit like this is hard work, and will no doubt result in a lot of testy conversations with internal clients. In much the same way that an editor becomes a therapist, so too does a digital content specialist. My personal suggestions here are to be sensitive to the attachment many clients feel to their work (it is theirs, after all) and to really find out what their goal is for the content. When you take the time to really hear what they want to achieve, you can make a lot more headway by suggesting the best ways to help them get there.

  3. “Your customers’ top tasks are often not the same as your organization’s top tasks.” or Top Tasks vs. Tiny Tasks – – Gerry McGovernHow often do you find yourself in this situation? You’re spending all of your time posting information to your website that you know no one will look at, while the pages with the highest traffic remain unchanged or even looked at. For my main client, this came in the form of spending so much time adding information to pages that occupy less than 0.01% of the overall traffic, while the mobile platform, of which 73% of my users were hitting, received virtually none of my attention. Our top traffic pages (excluding a forced routing page) have not been touched in four years.

    I’ll be the first to say this is crazy.

    I’m betting I am not the only one who has experienced this. It is my primary goal right now to try and right the balance in this equation, and what I think will be my strongest weapon is the simple idea that right now, we’re yelling into empty rooms. I find there’s a real fear clients have of stopping a practice because of that “just in case” reason, but really, it’s just a waste of everyone’s time to shout at people who aren’t there.

Bonus quote: “Imitating paper on a computer screen is like tearing the wings off a 747 and using it as a bus on the highway”Karen McGrane

Amen. Thanks, An Event Apart Chicago.

3 Interview Mistakes I’ve Made So You Don’t Have To

I’ve been working since I was 13 years old (and wearing an onion in my belt, as was the style at the time). I’ve been interviewed for all kinds of positions and despite being successful overall in my career, I’ve definitely made interview mistakes. I’ve also been on the other side of the table and done the hiring. Here are three interview mistakes you can avoid.

1. Not Knowing Your Resume

I once interviewed for a part-time job teaching horseback riding lessons. I was really excited about the job, but because I had been out of the industry for nearly eight years, my grasp on the dates and timelines of my relevant experience was fuzzy at best. I struggled to remember the dates and total number of years I had been teaching and riding.

Interviews are stressful for everyone. However, if you’ve been offered the interview, you should have one big leg-up: your resume. You have already done the work of thinking about your skillset and experience. Now, you had better know that resume backwards and forwards. Being uncertain about simple information like how long you’ve been doing something makes it seem like you are at best unorganized and at worst, lying.

2. Not Having Questions Prepared

In my first “real job” interview, I spent a lot of time preparing to talk about myself, but I was completely thrown when they asked if I had any questions for them. I have also been on the other side, and candidates with thoughtful, relevant questions come off as being genuinely interested and invested in the position. And that’s the secret about the entire hiring process – hiring someone is like asking someone to go on a first date. The hiring manager is in a vulnerable position, so help them feel confident that you are the right person for the job by putting a little effort into customizing your questions. Think about:

  • What does a typical day look like in this job?
  • What is the goal for the business in this area over the next five years?
  • What does success look like in this role?

3. Not Preparing Your Elevator Pitch

This is the fundamental reason you’re being interviewed – to prove that you are the best candidate for the job. It’s called an elevator pitch because you’re supposed to imagine you are in an elevator with the hiring manager and you have the length of the ride to convince them. Take this to heart. If you’ve done a good job on your cover letter,  start there. Go over your resume, which should already be a distilled version of your best assets, and start highlighting the most impressive parts that are the most relevant to the job you’re applying for. Between the two documents, get your red pen out and rewrite that information into the most concise, convincing 400 words you can. Know that distilled sales pitch cold – not necessarily word for word, but all your best highlights should be on the tip of your tongue.