Marcela: I am not certain that teaching a large class would do what I’m wanting to do. The people I most want to help get into UX are also the people least likely to be able to afford to take UX courses.
Marcela: I am not certain that teaching a large class would do what I’m wanting to do. The people I most want to help get into UX are also the people least likely to be able to afford to take UX courses.
Fedora 28 (F28) is slated to release in May 2018. On the Fedora Design Team, we’ve been thinking about the default background wallpaper for F28 since November. Let’s walk through the Fedora 28 background process thus far as a sort of pre-mortem; we’d love your feedback on where we’ve ended up.
As of the past 3 releases, we choose a sequential letter of the alphabet and come up with a list of scientists / mathematicians / technologists to serve as an inspiration for the desktop background’s visual concept:
Backgrounds from Fedora 25, 26, and 27. 25’s inspiration was Archimedes, and the visual concept was an organic Archimedes’ screw. F26’s inspiration was Alexander Graham Bell, and the visual concept was a sound wave of a voice saying “Fedora.” F27’s inspiration was underwater researcher Jacques Cousteau, and the inspiration was transparency in the form of jellyfish.
Gnokii kicked off the process in November by starting the list of D scientists for F28 and holding a vote on the team: we chose Emily Duncan, an early technologist who invented several types of banking calculators.
We had a meeting in IRC (which I seem to have forgotten to run meetbot on ) where we brainstormed different ways to riff off of Emily Duncan’s work as an inspiration. One of the early things we looked at were some of the illustrations from one of Duncan’s patents:
Gnokii started drafting some conceptual mockups, starting with a rough visualization of an Enigma machine and moving to visuals of electric wires and gears:
After the holidays, we got back to it with the beta freeze deadline in mind. Note, we don’t have alpha releases in Fedora anymore, which means we need to have more polish in our initial wallpaper than we had traditionally in order to get useful feedback for the final wallpaper. This started with a regular triage meeting where the F28 wallpaper ticket came up. We brainstormed a lot of ideas and went through a lot of different and of-the-moment visual styles. Maria shared a link to a Behance article on 2018 design trends and it seemed 3D styles in a lot of different ways are the trend of the moment. Some works that particularly inspired us:
Both myself and terezahl, taking these inspirations as directions, started on another round of mockups.
Terezahl created mockups, one which appears to be inspired by Pilkington’s work, based of the concept of 28’s being a triangular number:
I was inspired by Weinkle’s paint waves, but couldn’t figure out a technique to approximate it in Blender. Conceptually, I wanted to take gnokii’s wires with data ‘lights’ travelling down the wires, and have those lights travel down the ridges in an abstract swirled wave. I figured probably it would take some work with Blender’s particular system, since the mass of a character’s hair is typically created that way. I had never used Blender’s particle system before, so I took a tutorial that seemed the closest to the effect I wanted – a Blender Guru tutorial by Andrew Price:
<iframe allow="autoplay; encrypted-media" allowfullscreen="allowfullscreen" frameborder="0" height="315" src="https://www.youtube.com/embed/XPFJGkB4v9U" width="560"></iframe>
As per the feedback I received from gnokii – the end result was too close to the output you’d expect from such a tutorial. I wasn’t able to achieve a more solid mass than the fiber optic strands, although they visually represented the ‘data light’ concept fork I was going for:
Time was short, so we ended up deciding to ship this mockup – as close to the tutorial as it was – in the F28 beta to see what kind of feedback we got on the look. Thankfully Luya was able to package it up for us with some time to spare! So far, the preliminary feedback we’ve gotten from folks on social media and/or who’ve seen it via Luya’s package for beta has been positive.
Since the time-consuming work of building the platform in Blender from the tutorial is done, I’ve started playing around with the idea to see what kind of visuals we could get. The obvious, of course, is to work the Fedora logo into it. Fedora 26’s wallpaper had a sound wave depicting the vocalization of the word “Fedora” – I was trying to think of how to have the fiber optic ‘data’ show the same. Perhaps this is too literal. Anyhow, here are the two crowd favorites thus far:
Anyway, this is where you come in. Take a look at these. With the system built in Blender, we have a lot of things we can tweak easily – the angles, the lens / bokeh / focus, the shape / path of the strands (like how the latest renderings follow the Fedora f/infinity), the shape / type of object the strands are made of (right now long / narrow cylinders.) These kinds of tweaks are quick. Any ideas you have on a path forward here, or just simple feedback, would be much appreciated.
I was recently asked what I would do if I didn’t have to earn money.
That was an interesting question, especially given that it’s difficult to say what that actually means. For example: If I don’t have to earn money, does that mean I’m able to do things that are more expensive than everyday things? Can I travel?
I decided to interpret it as if I had enough to be comfortable. For me, that includes at least some travel.
The first thing that came to mind with this was the significant difference in my mental state in winter and summer. I’m functional in winter (seasonal depression and insomnia are treated, but not completely countered). I’m good in summer — even with the insomnia, since it’s better with enough light.
So, ideally, I’d be doing something that feeds my soul (so to speak) in winter, and feeds my curiosity and enthusiasm and need for people in summer.
Having just returned from a week in Florida to visit my parents, I think that I would want to spend at least some of the winter somewhere with sun. I’m so much more… awake. Aware. Happy. Human. It’ll fade, since it still is February in Boston, but it’s such a strong reminder. I think Florida winter light may be better (stronger? More direct?) than Boston summer light.
So maybe in winter , I’d go somewhere bright for a few weeks to a month. And, overlapping or not, something involving animals. Whether it be spending time with lonely shelter animals, or helping out at a zoo or sanctuary, I find that doing something involving animals helps feed me in ways that help counteract the lack of light.<figure><figcaption>“I require surface area! It’s warmer than it’s been and I need warms!” — a turtle, also on the eco tour</figcaption></figure>
In summer, with better sunlight, I think I’d want to do two main things: Spend time outside in the sun, and teach UX to folks who cannot afford to pay for schooling.
At the moment, I’d need to spend more time learning and practicing UX research and interaction design, and maybe more visual design. I’d want to have years of practice, and maybe do some teaching on the side. Once I feel a bit less like I’m too new to teach (which isn’t actually true; I just would want to know more to feel comfortable), I’d want to pass that knowledge on to those who otherwise wouldn’t have the opportunity to get into UX. I’m already offering info to anyone who I know needs it, even though I am fairly new to UX. The fact that I tend to dive headfirst into anything I’m interested in means that — while I know there are gaps — I’ve learned a lot in the past two years of learning and practicing.
I think I’d want to focus on Women and Racial/Ethnic Minorities in tech (especially black folks and latin@s), as they may well be interested in and skilled at the UX field, but may not have any way to pay for learning. Similarly, I’d bet a fair number of people who would be excellent UX practitioners have no idea that such a thing exists.
Tech needs diversity, badly. Even if I ignore the fact that not having access to tech jobs means that there’s huge swaths of folks who aren’t making as much money as they could or need, diversity in a company means that there will be more people with different backgrounds looking at problems and the proposed solutions. There are far too many stupid mistakes and problems relating to thoughtlessness that would have a much better chance of being spotted if entire teams weren’t made of white, cis, men. It’s not their fault that they don’t spot problems, but different life experiences have a huge effect on how one thinks and the types of solutions one might suggest and implement. Refusing to admit that this is true is both short-sighted and self-centered.
So, I’d want to teach. And since I find UX so fascinating, and that’s my focus and likely to stay that way, that’s what I’d want to teach.
I need people. I need my family, my friends, and to interact with people I don’t already know in low-pressure environments.
So I’d want to build in time to spend with my family and friends, and find ways to meet new people and learn who they are and what they think and what they want. Sure, that last part sounds a bit like User Research, but it’s more than that. People are fascinating. And if it’s low pressure to us both — which user research is not — I get the chance to get to know more people without anyone feeling pushed into it. Some parties are good for this, if there are quieter spaces so that conversation is possible.
I need touch. Both with people I’m comfortable with and with animals who rely on me and who do not. That would need to be part of an ideal life, as well.
I need to move. Walking is great, but often harder in winter due to weather and to seasonal depression making inertia stronger. Kayaking is shockingly fun, although my inflatable kayak is not heavy enough — I always feel like I’m going to fall out. Swimming is good, if I don’t have to deal with chlorine. I’m sure there are other things that easily and comfortable fill my need to move, but those are the first that come to mind.
If you didn’t have to earn money, what would you want to do?
I used the weekend to moderate the supplemental wallpapers for Fedora 28. I did already check from time to time the sumissions and rejected the ones who break the guidelines, and started checking the legality of the ones with given references of the license.
So far we have 124 submissions, but I rejected a lot (so far 18) this time for wrong aspect ration, some never will get that we dont accept submissions with the Fedora logo on it and unclear licenses, this time I rejected all who was not licensed with the same license as on Flickr or any other given reference. Before I always informed the submitter about this inconsistency, but there is to many of them now and it is very time consuming (some really think its just hitting a button inside Nuancier, I can assure you its not). 61 badges are so far awarded
There might come some more submission as there is some time until 13th left. But dont think I can moderate you last minute submission, Pingou already added now finally the feature that we can have deadline for submission and the begin of the voting phase on different dates.
some of my personal favorites so far:
The contest is a time and resourcen devouring thing for me, I spend an average of 160-200 hours working time with it. I have to mention this also now, I have to live with just a mobile connection and this costs me serious traffic. I had to add volume on Sunday just to finishing it and that after spending already on saturday a lot of traffic for it. Ok mobile traffic is in Cambodia (for western view) very cheap, to add 500MB costs me just 0.30$ but there is a downside, if you topup here the money is only valid for usage during next 7 days, so using 30 cents from a dollar means, 70 cents stay and normally I just have 1$ a week costs for my subscription, so this money will be not used and on the end I paid 1$ for the add, except I use it for adding more. Currently a dollar, is a lot for me I also get a good meal for it but unfortunately a coffee (at least not a good one)
I recently applied for a job somewhere, and found the initial application process confusing and dismaying.
The reason, I think, is that it was not clear a) if the entire process actually happened, and b) what all I was actually submitting. So, I decided to take a bit of time and add some redesign to make things a little less confusing. I’ve also blurred out the company name for politeness’ sake.
When you look at a job description, you get something like this (with a bright orange ‘apply now’ button that is not visible in this screenshot). This seems fine.<figure></figure>
After you click Apply Now, you get an odd sort of thing about your personal data collection. I’m guessing this is because it’s a security company, but it reads all sorts of weird. Whatever, that’s not a huge deal.<figure></figure>
Next, you get your first page of the application. I like that they remind you what you’re applying for!<figure></figure>
If you upload your resume, your name and email are auto-filled. That’s cool, thanks! When you select ‘Next’, you get this:<figure></figure>
Wait. What? We just jumped to questions about my nationality and my affirmative action status? What about my work experience? My education? A cover letter? Did the resume upload skip the need for work and education info? Maybe, let’s keep going.
You might notice (I didn’t at the time) that this button says ‘Submit’, not ‘Next’. I didn’t grab a screenshot (and didn’t want to apply twice), but that’s the end of the application process. It thanks you, and it sends you email confirming your application.
What? I don’t even know for sure what it sent! I don’t know how well it parsed my resume. I have no clue at this point what just happened.
Ok, so that was all sorts of confusing. Enough so that last night as I was falling asleep, I was distracted by wondering what would help. I considered a progress indicator, as that would at least make the extreme brevity of the application not a surprise. I also wondered if they’d labeled the final button ‘Submit’, which they actually had. (but perhaps ‘Submit Application’ would have been a clearer signal!) Finally, right before I fell asleep, I realized that what I most missed was a summary of what I was about to submit.
So, my version of the first page, with a progress bar added (using their font as detected by What Font and the same color as the next button for the progress indication):<figure><figcaption>Look! It’s the first step of three!</figcaption></figure>
My version of the second page (which was the last in the previous version) also has a progress bar, and changed the button to say ‘Next’. Not sure why I couldn’t make the carets a little more visible when they are between things. And perhaps I need some sort of ‘completed’ indicator for the first step, like a checkmark.<figure><figcaption>Still a weird jump, but at least I had a chance to expect it.</figcaption></figure>
Finally, I made the very barest of bones summary page (the progress bar, what one was applying for, and a brief statement about the summary page). I didn’t make the whole page, which means that I didn’t get to include a “Submit Application” button instead of just ‘Submit” or suggest ways to make it easy for people to change things they don’t agree with. The latter seems important, especially if it really is automatically interpreting the resume; perhaps offer inline editing?<figure><figcaption>Not entirely sure how to end progress bars of this type, but you get the point.</figcaption></figure>
I’m struggling with the visual design part of things, but at least I feel a little better about the weird application process, having “fixed” it (at least in theory).
I’m not sure what happens if you don’t submit a resume in that first page (or if you use linkedin or something instead). It seems like it might be a kindness for them to tell you what submitting your resume (or associating with social media) did for you, so that it’s less confusing when it never asks about jobs or education.
Also, Gravit Designer is a pretty nice tool for this purpose!
UX folks may be in the best position to identify ethical issues in their companies. Should it be their responsibility?
This is the final piece of the story I’ve been telling. It started with an explanation of some of the problems currently present in the implementation of UX practices. I then described various ethical problems in technology companies today.
I will now explain how UX folks are uniquely situated to notice ethical concerns. I will also explain how, despite their unique perspective, I do not think that UX folks should be the gatekeepers of ethics. Much like UX itself, ethical considerations are too likely to be ignored without buy-in from the top levels of a company.
Ethics and user experience are tied together for a few reasons:
Given that UX folks are in a great position to see ethical problems as they come up, it may be tempting to suggest that we should be the ones in charge of ethics. Unfortunately, as I described in an earlier section, many UX folks are already struggling to get buy-in for their UX work. Without buy-in at the top level, we are unlikely to have the power to do anything about it, and may risk our jobs and livelihoods.
This is made worse by the fact that there are a lot of new UX folks in the Boston area. If they are on the younger side of things, they may not realize that they are being asked to do the impossible, or that they can push back. New UXers may also have taken out student loans, whether as an undergraduate student or to enable a career change into UX, thereby effectively becoming indentured servants who can’t even use bankruptcy to escape them.
Even new and career-changer UX folks who have not taken out loans can feel like they can’t afford to annoy the company they’re working for. Given how few entry-level jobs there are — at least in the Boston area — it’s a huge risk for someone new to UX to be taking.
The risk of pointing out ethical problems is even worse when you are talking about an ethnic minority or others who are in an especially vulnerable position, and who may also be more likely to notice potential problem-areas.
Individual UX folks should not be the sole custodians of ethics nor of the commitment to a better user experience. Without buy-in at high levels of the company, neither of these are likely to work out well for anyone.
Who, then, should be the custodians of keeping software from causing harm?
The UXPA organization has a code of conduct, which is excellent. Unfortunately, it doesn’t really have much to do with the ethical concerns that have come up lately. At best, we have the lines “UX practitioners shall never knowingly use material that is illegal, immoral, or which may hurt or damage a person or group of people.” and “UX practitioners shall advise clients and employers when a proposed project is not in the client’s best interest and provide a rationale for this advice.” However, these are relevant to the problem at hand only if a UX practitioner can tell that something might cause harm, or if a client’s best interest matches up with the public’s best interest.
The code of conduct in question may not be specific enough, either: the main purpose of such a code of conduct is to offer practitioners a place to refer to when something goes against it. It is not clear that this code offers that opportunity, nor is it really a UX professional’s job to watch for ethics concerns. We may be best positioned, and we may be able to learn what to look for, but ethical concerns are only a part of the many tasks a UX professional may have.
A better question might be: how do we encourage companies adopt and stick to an ethics plan around digital products? Once something like that is in place, it becomes a _lot_ easier for your employees to take that into account. Knowing what to pay attention to, what areas to explore, and taking the time to do so would be a huge improvement.
Maybe instead of asking UX folks to be the custodians of ethics (also here), we can encourage companies to pay attention to this problem. UX folks could certainly work with and guide their companies when those companies are looking to be more ethically conscious.
I’m not at all certain what might get companies to pay attention to ethics, except possibly for things like the current investigation into the effects of Russian interference in our politics. When it’s no longer possible to hide the evil that one’s thoughtlessness — or one’s focus on money over morals — has caused, maybe that will finally get companies to implement and enforce clear, ethical guidelines.
What are your thoughts on how — or even if — ethics should be brought to the table around high tech?
UX folks may be in the best position to identify ethical issues in their companies. Should it be their responsibility?
In the previous section, I described the state of UX practice at technology companies, and the need for high-level buy-in for successful UX integration.
There is a concerning — and increasingly evident — lack of ethical consideration in the processes of most software companies. In this section, I will describe some of the ways in which this has recently become more apparent.
The software in our lives are not generally designed with our health and well-being in mind. This fact is becoming clear as Facebook, Google, and Twitter are in the spotlight relating to Russia’s interference with our elections and increasing political divides. Twitter has also typically been unwilling to do much about threats or hate speech.
There is too much focus on engagement and creating addiction in users, and not enough on how things might go bad and appropriate ways to handle that.
There’s a proliferation of products in the Internet of Things (IoT) space, many of which are completely insecure and thus easily turned into a botnet, have the private information on them exploited, or hacked to be used as an information gathering device.
Some IoT devices are specifically targeted at kids, but few or no companies have put any effort into identifying how they will affect the development of the children who use them. Concerned researchers at the MIT Media Lab have begun to study the effects of intelligent devices and toys on kids, but this won’t stop the continued development of these devices.
Similarly, it’s unclear how the use of devices that were originally aimed at adults — such as Alexa — will affect the kids in those houses. On one hand, it doesn’t involve screen time, which is no longer completely contraindicated for kids under two but is still wise to limit. On the other hand, we have no idea how those devices will answer questions they were not programmed to handle. Additionally, these devices do not encourage kids to use good manners — one of the important lubricants for the fabric of society. It’s hard enough to teach kids manners without having that teaching undermined by an intelligent device!
Finally, consider how machine learning can result in some truly horrific scenarios (content warning: the linked essay describes disturbing things and links to disturbing graphic and video content).
Someone or something or some combination of people and things is using YouTube to systematically frighten, traumatize, and abuse children, automatically and at scale, and it forces me to question my own beliefs about the internet, at every level.
James Bridle · Writer and Artist
Similarly, we’ve seen the results of a focus on metrics and money over security and sanity. Twitter not only knew that there were spam and fake accounts from Russia and the Ukraine in 2015, but refused to remove them because
“They were more concerned with growth numbers than fake and compromised accounts,” Miley told Bloomberg.”
Equifax stores highly sensitive information about people in the US, and left security vulnerabilities open for months after being told about them. As a result, they had multiple security breaches, basically screwing over anyone whose data was stolen.<figure><figcaption>Yeah, no. You knew you had vulnerabilities!</figcaption></figure>
Even without willful ignorance, thoughtlessness alone can easily be enough to put individuals, communities, and societies at risk.
Considering the breadth of data that many companies are collecting on those who use their products, there is a worrying lack of thought given to the invasiveness of this practice and to how to safeguard the data in question. These companies often make poor choices in what information to keep, how to secure and anonymize the information, and who has access to that information.
Some might say that having conversational devices like Alexa and Google Home are worth the privacy risks inherent in an always-on listening device. Others might suggest that it’s already too late, given that Siri and Google Now have been listening to us and our friends through our phones for a long time now.
However, regardless of one’s thoughts on the timing of the concerns, the fact remains that tech giants have access to an amazing amount of information about us. This information is collected through our phones, through our searches and purchasing patterns, and sometimes through devices like the Amazon Echo and the Google Home Mini.
Some companies are better than others, such as Apple’s refusal to break their encryption for the FBI, but it can be quite difficult to identify which and where companies are making the best choices for their customers privacy, safety, and sanity.
Take machine learning (also known as AI), and the fact that companies are more interested in selling ads than considering the effects their software has on their customers:
It’s not that the people who run, you know, Facebook or Google are maliciously and deliberately trying to make the country or the world more polarized and encourage extremism. […] But it’s not the intent or the statements people in technology make that matter, it’s the structures and business models they’re building. […] Either Facebook is a giant con of half a trillion dollars and ads don’t work on the site, it doesn’t work as a persuasion architecture, or its power of influence is of great concern. It’s either one or the other. It’s similar for Google, too.
Zeynep Tufekci · Techno-sociologist
One of the major problems with machine learning is that we have _no idea_ precisely what associations any particular algorithm has learned. The programmers of those algorithms just say whether the output those algorithms provide is good enough, and often ‘good enough’ doesn’t take into account the effects on individuals, communities, and society.
I hope you begin to understand why ethics is a big concern among the UX folks I follow and converse with. At the moment, the ethics of digital products is a big free-for-all. Maybe there was a time when ethics wasn’t as relevant, and code really was just code. Now is not that time.
In part 3, I’ll discuss the positioning of UX people to more easily notice these issues, and the challenges involved in raising concerns about ethics and ethical responsibility.
User Experience (UX) folks may be in the best position to identify ethical issues in their companies. Should it be their responsibility?
This will be a multi-part story.
In this first part, I’m going explain some of the problems inherent in the implementation of UX practices at technology companies today, to provide the background necessary to make my point.
You can also skip ahead to part two, in which I talk about ethics in the tech industry today.
Businesses are starting to realize that they need to incorporate UX to retain and increase their customer base. Discussions with Boston-area user experience folks suggests that companies have figured out that they need to have incorporated UX years ago, and that they’re behind.
Many of those businesses are so new to UX that they don’t understand what it means. Part of the reason for this is that ‘UX’ is an umbrella term, typically including:
In addition, some UX teams include front-end developers, as it can otherwise be difficult to be certain that the developers implementing the interface have a basic understanding of user experience.<figure><figcaption>User Experience is complicated!</figcaption></figure>
When looking for UX employees, some businesses end up throwing the kitchen sink into their job descriptions, or look for the extremely rare UX unicorn — someone skilled at all parts of UX as well as development. This unfortunately makes it approximately impossible that they will get what they need, or possibly that they will get any decent candidates at all.<figure><figcaption>Often, people expect the UX unicorn to be able to do all aspects of UX and write code. This version is more reasonable: to understand how coding works, even if you don’t do it.</figcaption></figure>
Other employers prioritize visual or graphic design skills over the skills necessary to understand users, because they have gotten the impression that ‘making it pretty’ will keep their customers from leaving. Often the problem is at a much deeper level: the product in question was never designed with the user’s needs in mind.
Unfortunately, UX professionals brought into a company without buy-in at the top level of the company nearly guarantees that the UX person will fail. In addition to their regular UX work, they will also be stuck with the job of trying to sell UX to the rest of the company. Without support from higher-ups in the company, it is nearly impossible for a single person to make the amount of change necessary.
Surveying local people, I learned that being the only UX person in a small company or startup is probably doable, if the company understands the value you bring. There are fewer people to convince, and usually fewer products to deal with.
However, being the only UX person in a big company will likely be an exercise in frustration and burnout. On top of the fact that you’re trying to do too many different things on your own , you’ve also got to try to keep the bigger picture in mind.
Some important long-term questions include:
The second question brings us to the question of “who in high tech is thinking about the ethics of their creations?”. Unfortunately, too often, the answer is ‘no one’, which I will discuss in Part 2.
I’ve been trying to wrap my mind around the fonts section of the “Thinking With Type” book.
I started by hunting for family trees for common font families. Failing to find those — likely because there’s an astonishing number of fonts out there — I started doodling around trying to get something on paper for myself.
Without further ado, here’s my best approximation of the information in the section I’ve read, with some space available for further exploration. Mostly, I think I’m baffled by how one selects a font or font family, in part due to the sheer number of fonts out there, and in part because some require money. I’ll start out playing with with google fonts, because those seem to be specific for the web, and free. Open Sans seems to be a decent default, and Patternfly uses it.
“Thinking With Type” starts out by explaining the history behind fonts, and structures things by that history.
Humanist (or Roman) fonts include what were originally the gothic and italic typefaces — these came from hand-written, script and body-based styles. These relied upon calligraphy and the movements of the hand.
Enlightenment fonts were based on engraving techniques and lead type, and allowed for more flexibility in what was possible. This included both Transitional and Modern typefaces, which began the process of separating and modifying pieces of a letterform. Transitional started with Baskerville’s sharper serifs and more vertical axes. Modern went to an extreme with this, with Bodoni and Didot’s thin, straight serifs, vertical axes, and sharp contrast between thick and thin lines.
Abstract fonts went even further in the direction of exaggerating the pieces of a letterform, in part because of the additional options available with industrialization and wood-cut type.
Reform and Revolution were a reaction to the abstract period, in which font makers returned to their more humanist roots.
Computer-optimized fonts were created to handle the low resolution available with CRT screens and low resolution printers.
With the advent of purely digital fonts, creators of fonts started playing with imperfect type. Others created font workhorses using flexible palettes.<figure><figcaption>This is probably better named Font History!</figcaption></figure>
Humanist fonts were based on handwriting samples.
Gothic fonts were based on German writing, such as that of Gutenberg:<figure><figcaption>https://www.myfonts.com/fonts/alterlittera/gutenberg-a/</figcaption></figure>
Whereas the Italic fonts were based on Italian cursive writing:<figure><figcaption>https://en.wikipedia.org/wiki/Italic_type</figcaption></figure>
These were combined by Nicolas Jenson in 1465 into the first Roman typeface, from which many typefaces sprung:<figure><figcaption>https://en.wikipedia.org/wiki/Nicolas_Jenson</figcaption></figure><figure><figcaption>I don’t have much about the ones after Jenson.</figcaption></figure>
With the Enlightenment period came experimentation.
From the committee-designed romain du roi typeface, which was entirely created on a grid:<figure><figcaption>http://ilovetypography.com/2008/01/17/type-terms-transitional-type/</figcaption></figure>
To the high contrast between the thick and thin elements from Baskerville, no longer strongly attached to calligraphy (the point at which you enter the Transitional period for fonts):<figure><figcaption>http://ilovetypography.com/2008/01/17/type-terms-transitional-type/</figcaption></figure><figure><figcaption>https://en.wikipedia.org/wiki/Baskerville</figcaption></figure>
The Modern fonts from Bodoni and Didot further increased the contrast between thick and thin elements beyond Baskerville’s font.<figure></figure><figure><figcaption>https://en.wikipedia.org/wiki/Bodoni and https://en.wikipedia.org/wiki/Didot_(typeface)</figcaption></figure><figure></figure>
In the abstraction period, the so-called Egyptian or Fat Face (now known as slab serifs) fonts came about. These were the first attempts at making type serve another function than long lines of book text, that of advertizing — otherwise known as display fontfaces.
These took the extremes of the Enlightenment period and went to extremes with them, making fonts whose thin lines were barely there, and whose thick lines were enormous.<figure><figcaption>Egyptian, or Slab Serif, from http://ilovetypography.com/2008/06/20/a-brief-history-of-type-part-5/</figcaption></figure><figure><figcaption>Fat Face, from http://ilovetypography.com/2008/06/20/a-brief-history-of-type-part-5/</figcaption></figure>
Font makers in the reform period reacted to the excesses of the abstraction period by returning to their historic roots.
Johnston (1906) used more traditional letterform styles of the Humanist period, although without serifs:<figure><figcaption>https://en.wikipedia.org/wiki/Johnston_(typeface)</figcaption></figure>
The Revolution period, on the other hand, continued experimenting with what type could do.
The De Stijl movement in particular explored the idea of the alphabet (and other forms or art) as entirely comprised of perpendicular elements:<figure><figcaption>Doesburg (1717), https://zaidadi.wordpress.com/2011/03/09/de-stijl-in-general/</figcaption></figure><figure><figcaption>Forgive the bright pink aspect of this. It’s my lighting!</figcaption></figure>
The low resolution of early monitors and printers meant that fonts needed to be composed entirely of straight lines to display well.
Wim Crouwel created the New Alphabet (1967) font type for CRT monitors:<figure><figcaption>http://luc.devroye.org/fonts-24196.html</figcaption></figure>
Zuzana Licko and Rudy VanderLans created the type foundry Emigre, which includes Licko’s Lo-Res (1985) font:<figure><figcaption>https://www.myfonts.com/person/Zuzana_Licko/</figcaption></figure>
Matthew Carter created the first web fonts in 1996 for Microsoft, Verdana (sans serif) and Georgia (serif):<figure></figure><figure><figcaption>From Wikipedia, https://en.wikipedia.org/wiki/Verdana and https://en.wikipedia.org/wiki/Georgia_(typeface)</figcaption></figure>
With the freedom from the physicality of the medium (such as lead type or wood type) that came with computers, some font designers began experimenting with imperfect types.
Deck made Template Gothic (1990), which looks like it had been stencilled:<figure><figcaption>https://en.wikipedia.org/wiki/Template_Gothic</figcaption></figure>
Makela made the Dead History (1990) font using vector manipulation of the existing fonts Centennial and VAG Rounded:<figure><figcaption>https://www.emigre.com/Fonts/Dead-History</figcaption></figure>
And Rossum and Blokland made Beowulf (1990) by changing the programming of PostScript fonts to randomize the locations of points in letters:<figure><figcaption>https://www.fontfont.com/fonts/beowolf</figcaption></figure><figure></figure>
Also during the 1990s, some folks were working on fonts that were uncomplicated and functional. Licko’s Eaves pair, with their small X-heights, are good for use in larger sizes:<figure></figure><figure><figcaption>https://www.emigre.com/Fonts/Mrs-Eaves (1990) and https://www.emigre.com/Fonts/Mr-Eaves-Sans-and-Modern (2009)</figcaption></figure>
Smeijer’s Quadraat (1992) started as a small serif font, with various weights and alternatives (sans and sans condensed) added to the family over time:<figure><figcaption>https://www.fontfont.com/fonts/quadraat</figcaption></figure>
Majoor’s Scala (1990) is another simple, yet complete, typeface family:<figure><figcaption>https://en.wikipedia.org/wiki/FF_Scala</figcaption></figure>
Finally, at the turn of the century, Frere-Jones created the Gotham (2000) typeface. Among other places, it featured prominently in Barack Obama’s 2008 presidential election campaign.<figure><figcaption>https://en.wikipedia.org/wiki/Gotham_(typeface)</figcaption></figure>
In an effort to better remember various suggestions and terms used throughout the Font portion of Thinking With Fonts, I created a terminology sheet.<figure></figure>
I’m most likely to forget that there’s multiple different items which can be understood to be quotes, and how to use them. Additionally, that larger X-heights are easier to read at small sizes.
I started making a list of common fonts, but quickly realized that this was a complex and difficult task. I’m including what I made for completeness, but it seems like a superfamily (like Open Sans) will be fine for most of my work.<figure></figure>
The book discusses Text next, after an exercise in creating modular letterforms on a grid. I’m looking forward to it, but I do need a break from it for now.
I’ve started trying to mimic existing visual designs (from the collectui.com website), as many folks have suggested it’d be the best way to get a feel for what works and how to do it. I’ll likely talk more about that here, once I’m further along in that process.<iframe frameborder="0" height="400" scrolling="no" src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&dntp=1&url=https%3A%2F%2Fupscri.be%2Ff51076%2F&image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%252F%253Fenpose&key=d04bfffea46d4aeda930ec88cc64b87c&type=text%2Fhtml&schema=upscri" width="800">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</iframe>
A lot of companies out there seem to want UX visual design skills more than they want UX research skills. I’ve often felt like I’m missing something important and useful by not having a strong grounding in visual design, and have been searching far and wide for some ideas of how to learn it.
One of the more interesting suggestions I have had relates to typography: many websites have typography and grid principles incorporated into them, so that is a good place to start. I’ve also had a number of suggestions to just make things, with pointers to where to get ideas of what to make. Below are the suggestions that make the most sense to me.
A helpful fellow volunteer (Tezzica at Behance and other places — trained in graphic design with a UX aspect at MassArt) at the UX Fair offered me a number of useful ideas, including the strong recommendation that I read the book called “Thinking With Type”, by Ellen Lupton. This books is, if nothing else, a very entertaining introduction to the various types and type families. There is the history of various fonts and types, descriptions of the pieces of a piece of type, and examples both good and bad (she calls the latter “type crimes” and explains why they are type crimes). I’m only 1/3 of the way through it, so I’m sure there’s a lot more to it.
Tezzica also suggested that I take the SkillShare course by the same author, Typography that Works. Given that I currently have free access, I am in fact doing that. Some of what we’ve covered, I knew from previous courses (grids, mostly), and some recapped a bit of what I’ve read in the book thus far. Reminders and different types of media are really useful.
I’m unexpectedly bemused by the current section, in which we are to start designing a business card. While I found the ‘business card’ size in Inkscape, I’m not completely sure that I’m managing to understand how to make the text do what I want it to do. I suspect that a lot of visual/graphic design is in figuring out how to make the tools do what you want, and then developing a better feel for ‘good’ vs ‘bad’ with practice! (I’m currently playing with Gravit Designer, which is a great deal easier to use while still being vector graphics.)
I’ve also had a chat with one of the folks I interviewed about getting a job in Boston, Sam, who had gotten a job between me talking to him and interviewing him. He also strongly suggested typography, and seems to have already worked through a lot of the problems I’m struggling with: not a lot of understanding of how visual design works, but a strong pull toward figuring it out.
Another thing that Tezzica mentioned was assignments she’d had in school where basically they had to play around with type. In one, the challenge was to make a bunch of graphics which were basically combining letters of two different typefaces into a single thing, or a ‘combined letterform’.
Tezzica suggested that it would be useful to peruse Behance for students of RISD and MassArt and see where the samples look similar, and potentially identify the assignments from classes at those schools. I have thus far not been successful in this particular endeavor.
Another possible way to find assignments is to peruse tumblr or pintrest and see if any old assignments or class schedules are still there. Also thus far unsuccessful!
Both Tezzica and Sam suggested doing daily challenges (on Behance, since the accounts there don’t require someone else to invite you) using ideas from dailyui.co or dribble. Tezzica also suggested taking a look at common challenge solutions and seeing if there’s an interesting and different way to do it. Tezzica also pointed out the sharpen.design website and its randomized design prompts.
Sam suggested taking a website that I like the look of, and trying to replicate it in my favorite graphic design tool (this will probably end up being Inkscape, even though it’s not as user-friendly as I’d like), and pointed out that it could go onto my portfolio with an explanation of what I was thinking while I did it.
Tezzica suggested a Hand Lettering course by Timothy Goodman and a Just Make Stuff course by him and Jessica Walsh (this one being largely about ‘making something already’). She also suggested Nicholas Felton’s Data Visualization courses (introduction to data visualization, and designing with processing). Both are on Skillshare.
Finally, Sam recommended taking screenshots and making notes of what I notice about sites that are interesting or effective and why.
This reminds me a bit of my periodic intent to notice what design patterns and informational architecture categorization methods websites use.
Mostly, I need to train my eye and my hand, both of which require practice. Focused practice, and I think between Sam and Tezzica, I have a good sense of where to go with it. At the moment, I’m focusing on the Thinking With Type book and course, as otherwise I’ll overwhelm myself.
I’m a researcher and interaction designer who’s been teaching myself UX for nearly two years. I’ve recently started trying to learn IA, and have been looking for jobs in the Boston area for most of that time. I’m not really sure what I’m looking for from a mentor, other than perhaps sympathy for the amount of difficult finding a job has been and maybe connections? (https://suzannehillman.com — for the curious)
I’ve been up to a lot of different things, focused mostly on increasing my chances of getting a job.
I have a lot of UX-related links. They aren’t even all in the same place, as some are in bookmarks, some are in OneTab, and some are in email.
To handle this problem, and to offer others the chance to benefit from them, I’ve been sorting them into Enboard pages:
If anyone has any thoughts on how to better organize these, I’m all ears. Especially the UX Beginners one, as it’s becoming unwieldy.
After I finish sorting the ones I have, I hope to ask some folks about their preferred terms for things and organization preferences (as per Information Architecture, aka IA) and improve the organization that way.
I’ve been taking an IA course on skillshare (https://www.skillshare.com/classes/UX-Series-Designing-Web-Navigation/503660567/) which has been decent. Unfortunately, it appears that the course instructor isn’t paying attention to it anymore, so it’s not possible to get answers to questions or ask for broken things to be fixed. Even so, though, it has been useful guidance and practice.
Skill share is free for a two month trial period, and if you get your friends to sign up, you get an additional free month per friend once they pay for their first month.
I used the two week free trial of O’Reilly’s Safari to get a quick introduction to Sketch (https://www.safaribooksonline.com/library/view/working-with-the/9781491998748/). This was amazing, as it didn’t require me to do visual design as past of learning Sketch, and the instructor is excellent at making sure to explain things, including the need to be organized and prepared before jumping into Sketch.
I also used it for Success Skills for Introverts (https://www.safaribooksonline.com/library/view/success-skills-for/9781491930700/) which was useful for concepts like:
Finally, I’m about halfway through an excellent, concrete and straightforward course which should help improve the user experience of my (and your!) portfolio (https://wispfox.wixsite.com/hillmanconsulting/portfolio — the one I’m working on, not yet official). It costs a bit under $90, which is not bad at all. https://learn.givegoodux.com/courses/enrolled/217467 — I’m at the point of starting to make changes based on this course and on feedback from someone I had a chat with from http://designmentors.org/.
Unfortunately, I’m unable to make the live chat for the course, as I’ll be at AthenaHealth’s hackathon in Watertown (http://athenahackathon.com/).
I’m planning to write up a Medium post about portfolios after I finish this course. Maybe it’ll help others more than most such articles seem to?
I’m also trying to figure out the best way for me to learn Visual/Graphic Design. I’m currently hunting through SkillShare’s offerings, to start something after I finish my current courses. I have some idea of the basic stuff from the Coursera course I took on Design Principles (https://www.coursera.org/learn/design-principles/home/week/2), but I’d like to have stronger skills for contexts like my portfolio and to be able to say that I have experience with basic visual design when job hunting. Many jobs in the Boston area want visual design skills and already have folks who do research.
Similarly, I’d like to better understand how to incorporate my existing quantitative research skills from graduate school into my UX practice. At the moment, I’m perusing a PDF of “Measuring the User Experience” by Tom Tullis. Lots of people suggested it! I have also obtained “Quantifying the User Experience: Practical Statistics for User Research” by Jeff Sauro and James R. Lewis as I suspect that it’ll be useful for someone with a statistical background like myself.
The Recycle Bot toy project I’m mentoring Radhika Sundararaman on is proceeding slowly. Our free Axure licenses expired before we did usability testing, so we translated it to InVision using screenshots from the Axure shares we’d published (you cannot access your Axure files when your license expires).
We’ve since done a pilot test (with each other) and will be making some changes to our scripts and tasks. Due to the expiry of Axure, we won’t be making any of the obvious changes that came up during the pilot test.
If I find time, I may see about adjusting some of what’s in InVision to be less inconsistent with itself. We hadn’t originally figured out how to make it possible for us both to work on the project in InVision at the same time, so I’d been talking Radhika through some of the problems and confusions she ran into (sadly without the option to see her screen and what she was trying to do). We since managed to share her prototype with me, but it’s a lot of work to change the screenshots after the fact.
We’ll be looking for a few people to do usability sessions with soon, and in cases where they are people we know well, will see about having the other person work with them to avoid some bias.
I’ve presented to the board, but they are currently focusing on the UX Fair that’s coming up early next month.
Folks who weren’t at the meeting I presented at offered feedback on the summary I sent to the president of the board. This was a bit awkward for a couple of reasons:
That said, much of what they offered was useful. Some seemed to be assuming that I was focusing only on what I personally could do to get a job, when I’m hoping to help others as well. My current plan is to figure out how to follow-up on those points after the UX Fair.
I’ve also emailed with the XX-UX folks in San Francisco, as they have a mentoring program going. I’m aiming to get an idea of what they are doing, have done, and what has been working for them. They did suggest that I needed two other folks to work with on the mentoring idea (or creating an XX-UX branch in Boston), which has been difficult. I’ve had people say they want to help out with this project, but they end up being too busy for one reason or another. Alas!
The user dropdown research I was doing with Patternfly has turned into research on UI specifications for standard menu design patterns (https://github.com/patternfly/patternfly-design/issues/464). I should be able to use some of the information I gathered on the user dropdown, and the results of this ought to be related to that work.
I’ve been chatting with a couple of guys who are working on a tool called Simmetri (http://simmetri.com/) to help non-developers create VR worlds. We met at MIT’s Reality, Virtually hackathon (http://www.realityvirtuallyhack.com/), which was otherwise not a good experience for me for reasons not MIT’s fault.
I am _so happy_ this tool exists, and spent a couple of hours downtown a week or so ago offering them feedback on the things that tripped me up, and offered suggestions for areas where different organization was needed. The UI was initially based on Photoshop, which isn’t really an interface I’ve ever liked.
I don’t know what the best practices are around designing a design tool, especially a 3-D design tool or one that is meant to connect with VR devices! I also would want to identify their competitors to figure out what their unique contribution in this space might be (and see what others have done for their interface).
They are currently looking for funding (in the art/creative space) from friends and family, and indicated an interest in bringing me on if they get it. I typically would avoid a startup, but I _like_ these two guys a lot, and they seem like they’d be reasonable about the fact that I don’t know all pieces of the UX umbrella.
I’ve not yet started this, in part due to the sheer number of other things I’m working on, and in part because I’d like to finish the IA course I’m taking. However, a friend has suggested that his site isn’t well organized and would like my help. I definitely like the idea of getting real IA experience, so that sounds good to me.
This friend has already found a couple of people in his gaming group (using his system) who would be happy to talk to me. Very nice!
I’ve not forgotten this project! I have been a bit stumped about how to approach it after I finish up with some of the things I’m working on. I have an ok understanding of what it’s about and for, but no strong sense of the users and their needs (which may mean that I need to watch some of the users who are not the developer use it?), nor the best areas to tackle first.
I think part of the problem is that it is a pretty nebulous concept (“support and encourage collaboration about and sharing of information within communities.”), which makes it more difficult to approach.
I shall keep it in the back of my head, but for the meantime it’s on a back burner.
Looks like Red Hat is only looking for mid-level interaction designers, as they’ve got lots of junior and senior level people. At least based on the most recent opening I saw, this appears to mean at least 5 years of experience.
I’ll keep my eye on their jobs, but it’s looking unlikely that I’ll be working in UX at Red Hat any time soon.
I’m happy with Vitamin T as a recruiting agency. They talk to me when I indicate interest in a position they send me, quite quickly.
No idea if it’ll go anywhere, but they’re passing my info along about a contract position in Waltham.
I’m pretty happy with The Creative Group, too. They also want to talk to me when they have things that relate, and the person I most recently talked to specifically suggested that I get in touch if I see something I want to apply to. They may have contacts that I do not, and all.
Job hunting is frustrating. I’ll have the two years most junior positions seem to want as of February. Maybe that’ll help.
And I do need to finish updating my portfolio based on the course and the feedback I got from the designmentor.org guy.
I’ve been going to a decent number of UXPA and Boston Chi events, although not all of either of them. Getting home from Boston proper isn’t easy to do, since commuter busses have stopped by then.
It’s really odd to have the major project I’m working on be the one about finding a first UX job. People ask me what I’m working on, and I find it a little awkward to talk about given that I am myself looking.
I’ve given my card and suggested resources to lots of other newbies, though. I have a lot of info after almost two years of this! Too bad I’m not getting paid to help my fellow newbies. ;)
I’ve also been using the #ux tag more on Twitter after attending the UX Careers Handbook presentation by Cory Lebson. Among many other things, he pointed out that it was a very useful way to be seen as involved with UX. I shall get that book at some point, because it does a good job of helping one keep track of the things involved in the job hunting process.
I sometimes forget. No wonder I feel overwhelmed at times.
I think my focus needs to be threefold: Finish the IA course. Fix my portfolio and make it be the new official one. Finish up the project with Radhika.
The portfolio part is definitely the most daunting piece. I’ve been working on that for so long! I guess it means I have a good grasp of what I’ve worked on?
I’m in the middle of a career change, and turned 40 a week ago. I’ve been working on UX projects in my own time, and trying to get paid work in UX has been quite difficult. I think part of the problem is that there are a huge number of new UXers in the area I’m in, which makes it harder to stick out as worth someone’s time.
Finding a mentor is _hard_!
Then again, I’m not entirely clear on what a mentor is supposed to offer a mentee. I’m currently working on a simple project with someone currently in school for technical communications, which feels like mentoring even though I’ve not yet managed to get a paid UX position yet (I’m a career changer).
Just a strange position to be in!
After a long time it is time for another Inkscape Workshop here in Phnom Penh. This time the audience are young “ecopreneurs”. The environmental situation in Cambodia isnt the best, especially the situation with the trash. It is really a problem, if you drive trough the city, you seeing that Khmer always have a coffee or sugar can juice on their motobike hanging, that is a ot of plastic which ends up directly on the street. The effect of that is it flowing around when the rain comes, the channels are full of them it stinks and it always ends in the chain if you drive with the bicycle during the rain. So not nice!
This young people, want to change that. They do events educating people, what they can do better and founding businesses with an higher ecological impact and sometimes they just going on the street and collect the trash by them self. So a good thing to do.
This workshop shall help them to reach more people. We will do it for two days, the first day will be an introduction to Inkscape, with an practical part where we draw an trash bin. The second day will an introduction to poster design, where we work out the principles for it and design with Inkscape a few posters.
I had a random idea today and wanted to share it in case anybody has thought about this too, or tried something like it, or could add on to the idea.
I onboard, mentor, and think a lot about enabling new contributors to open source software. Traditionally in Fedora, we’ve called out a ‘join’ process for people to join Fedora. If you visit join.fedoraproject.org, you’ll get redirected to a wiki page that gives broad categories of skill sets and suggests Fedora teams you might want to look at to see if you could join them.
I started thinking about this because I’m giving a keynote about open source and UX at Ohio Linux Fest this weekend. One of the sections of the talk basically reviews where / how to find UX designers to help open source projects. Some of the things I mention that have proven effective are internships (Outreachy, formal Red Hat intern program, etc.), training, and design bounties / job boards. Posting UX assistance on say join.fedoraproject.org? Didn’t come up. I can’t tell you if I’ve actually onboarded folks from that workflow – certainly possible. My best success ratio in onboarding contributors in terms of them feeling productive and sticking around the community for a while, though, is with the methods I listed above – not a general call for folks of a certain discipline to come to the design team.
In fact, one of the ways we onboard people to the design team is to assign them a specific task, with the thought that they can learn how our team / processes / tools work by doing, and have a task to focus on for getting help from another member of the team / mentor.
Thinking about this, these successful recruitment methods of new contributors all focus on tasks, not skills:
If onboarding new contributors works well when those new contributors are put to work right away on a specific, assigned task with a well-defined scope, why do we attempt to recruit by categories of skills with loose pointers to teams (that get out of date), instead of tasks? You might have someone fired up to do *something*, but they’re redirected to a wiki page, to a mailing list, to wait a few days for something to respond and tell them “hi, welcome!” without actually helping them figure out what it is they could do.
If you’re with me here, up to this point… here’s the idea. I haven’t done it yet. I want to hear your feedback on it first.
I thought about redoing join.fedoraproject.org as a bounty board, really a job posting board, but let’s call it a bounty board. Bounties are very well defined tasks. I did a talk on how to create an effective bounty a while back, here’s the high-level crash-course:
I was thinking about setting this up as a pagure repo, and using the issues section for the actual bounty posting. The notion of status that applies to bugs / issues also applies to bounties, as well as assigning, etc. So maybe it would work well. Issues don’t explicitly manage the queue of bounty takers (should the 1st claimer fall through) but that could be managed through the comments. Any one from any Fedora team could post a bounty in this system. The git repo part of the pagure repo could be used for hosting some general bounty assets / resources – maybe a guide on how to write a good bounty with templates and cool graphics to include, maybe some basic instructions that would be useful for all bounty takers like how to create a new FAS account.
We do have a great resource, fedoraproject.org/easyfix, that is similar to this idea in that it uses issues/tickets in a manner geared towards new contributors. It provides a list of bugs that have been denoted as easy to fix by project owners all in one place.
The difference here though, is that these are raw bugs. They don’t have all the components of a bounty as explained above, and looking through some of the active and open ones, you could not get started right away without flagging down the right person and getting an explanation of how to proceed or going back and forth on the ticket. I think one of the things that makes bounties compelling is that you can read them and get started right away.
Bounties *do* take a long time to formulate and document. It is a very similar process to proposing a project for an internship program like Outreachy or Google Summer of Code. I bet, though, I could go around different teams in Fedora and find projects that would fit this scope quite well and start building out a list. Maybe as teams have direct success with a program like this, they’d continue to use it and it’d become self-sustaining. I don’t know, though. Clearly, I stopped doing the design team bounties after 4 or 5 because of the amount of work involved. But maybe if it was a regular thing, we did one every month or something… not sure.
Does this idea make sense? Did I miss something (or totally miss the point)? Do you have a great idea to make it better? Let me know in the comments.
The previous post on this topic offered an overall summary of what I’ve been learning in my conversations with folks. Now I’d like to go into a little more detail on some of the topics.
Identifying the best areas to focus is probably one of the hardest tasks, especially for those folks who are not able to afford to get a degree or do a bootcamp like General Assembly. The guidance offered through official programs is not to be underestimated!
You almost certainly have experience in _something_ that falls into UX design. Whether it’s researching how to do something, drawing things in your spare time, talking to someone new, explaining a skill or idea to someone else, or trying to use a new piece of software: these are all applicable to UX in some way or another.
Everything informs everything else, from the information you gather at the beginning, to the analysis with other folks, to the early sketchy design possibilities you create, through to iterating on your design based on feedback you get from stakeholders and users.
When these designs need to be produced in higher and higher fidelity as your team gets closer to something that works well for the stakeholders, there will likely be continued iterations based on what’s actually feasible and plausible. (I am not as experienced in the visual design aspect of the UX process, so I cannot offer as much structure around that part.)
Figure out what you know how to do or could easily learn. With that information, you can focus on what you know how to do and how to integrate it into a project, and then on improving any areas you specifically want to learn.
I personally need more practice in visual design and data visualization: I’m not especially familiar with visual design or otherwise making things visually approachable, and these both seem useful to at least have a basis in.
I’m working on identifying the best ways for me to improve these skills, and found that working on badges with Fedora folks helped a bit. Among other things, it meant that I had the opportunity to ask what people did when they did specific things that I might otherwise not have encountered (such as specific keystrokes in design programs).
For other folks, it might be wise to learn the basics of HTML and CSS. Even if you do not wish to write the code for your designs, it is immensely helpful to understand how programming works.
If you’re not familiar with how to phrase things, maybe you want to work on writing content for your designs. Maybe pretend that you are talking to someone who has never run into the thing you are talking about, or to someone who is too busy to give you more than a 30 seconds to a minute to read whatever you have to say. Figure out the most concise, but clear, way to say whatever you need to say. Even if you don’t want to write the content for your designs, it’s really important to be able to express yourself simply and clearly. Words are important, along with visuals and structure.
If you are looking to get into research, it would behoove you to learn some about quantitative research, not just qualitative. One of the major points that folks looking for quantitative researchers want is the ability to tell if the company is measuring success effectively.
Possible places to get cheap but decent classes include Lynda and Coursera. I’ve done some Coursera courses, specifically “Human-Centered Design: An Introduction”, ”Design Principles: An Introduction”, and “Information Design”.
Whatever it is that you need to learn more about, there is probably a way to do it online (remember to check Youtube!). However, it is often the things one needs the most help in that are the hardest to figure out how to learn on one’s own. Knowing the terminology is important for any successful google search!
(Note: I suspect that offering classes in basic aspects of each piece of the UX process would be a good value for the UXPA boston group, given the content of the previous paragraph. Not everyone learns from videos/written instruction very well)
In my experience, the best way to learn is to find a specific design project — really any design project is fine to start out — and start working on it. If you have friends who write programs, see if they want your help. If you have friends with lots and lots of ideas, ask them to let you help design one of them. If neither of these are the case, consider an area in which you wish that something existed, or in which you wish a piece of software were easier to use. At this point, it matters less if your project goes live — although that’s always preferred if possible — and more that you are working on something.
Take lots of screenshots and notes and keep track of what you’ve tried, what worked, and what didn’t work. These will be useful when it comes time to create your portfolio!
Remember: the point of your first project is to learn, rather than to succeed, and most people learn the best from failure. Failing at something isn’t actually bad. Indeed, it’s almost expected, since you’re new at it. Figuring out where things went wrong is the important part.
That said, it can be difficult to know what to do at any stage of a project, especially if you’ve never tackled one before. This is where having someone you can check in with is invaluable. Not only is UX design not really a solitary activity, but having someone to help nudge you on the right path when you get stuck is fantastic.
If you have a mentor, that’s great. If not, see if you can find other folks who are also job hunting to work with. Chances are good that you are each better at different pieces of the project, and this will provide you both with additional experience.
For a possible mentors, join http://designmentors.org/ (credit to David Simpson for this!) and get in touch with someone who looks useful for your needs.
If you’re still struggling to figure out a design idea, this page might be helpful.
If you’re not sure how to approach a project, this site talks about the whiteboard design challenge that sometimes happens in interviews, and is a decent overview of what a design project could involve.
(Note: Offering folks ways to get in touch with others who are looking for their design projects to work on might be a useful feature. Similarly, ways to find mentors.)
In general, you will need to use a tool of some sort for your design project. Paper prototypes are amazing, no doubt about it. Unfortunately, they are difficult to test out remotely, and rely on excellent drawing skills and handwriting to be easily used for prototypes.
There are a large number of options for tools in the UX design space.
Some are focused on being easy to use to make low and medium-fidelity mockups and prototypes (Balsamiq was my first tool, for example. Axure is easy to start out, but a bit complicated to learn to turn into a prototype). Some are specifically meant to help folks turn their designs into prototypes (like Invision, which is free and supports uploading existing designs) and often support collaboration quite easily. Others are more on the visual design side of things, although sometimes still include fairly easy ways to make mockups and prototypes (Sketch is extremely popular, but mac-only).
Adobe’s creative cloud service includes a lot of commonly used graphic design tools, whether photoshop (for which Gimp is a decent free and open source substitute, if poorly named), illustrator (vector graphics; try Inkscape for a free and open source substitute), indesign (as far as I can tell it’s about design for publishing online and off? Not sure of the best free equivalent) or the recently added experience design (XD beta, again not sure of an equivalent, although I think it may be meant to compete with Sketch).
The ones I’ve listed above are the most frequently mentioned in job applications, especially Sketch and Adobe creative cloud. Axure and Invision are also quite common. There are a _lot_ of other newer (and often free/beta) options, although I’ve not done much exploring of those.
(note: classes/mentors for basic introductions to the most common design tools might be useful, especially for those who are not already familiar with Adobe Creative Cloud. Not everyone learns from videos/written instruction well)
You may also want to investigate tools for mind mapping (I like MindMeister, free for a small number of maps), which can be useful to keep track of relevant ideas and concepts. Or for remote affinity mapping (I like Realtimeboard, free for a small number of boards) and other sticky-note/whiteboard-based activities.
There are a lot of other techniques that could be good to learn, including task flows and journey maps.
Many companies want folks with experience in the agile framework, so learning what that is and the various ways that design folk have figured out how to integrate into it would be useful.
If you are not already familiar with style guides and pattern libraries, getting a basic understanding of those would be useful.
First, congratulations! That’s often the hardest part.
Take a look at what you did with an eye toward improving. What do you want to learn more about? What do you need help with? Where do you feel you excelled?
Take a look at various blogs in UX, as now that you’ve done your first project, you will likely start finding that those start making more sense to you. I found that reading various blogs and watching videos was overwhelming before I’d done a project, because I had no idea what was relevant.
Twitter has a lot of fantastic UX folks, although who you want to follow may be partly location-based. I like Jared Spool, Joe Natoli, Luke Wroblewski, Mule Design Studio, Dana Chisnell, Sarah Mei, and What Users Do.
http://52weeksofux.com/ is an excellent overview site that I really need to revisit myself, now that I’ve got some experience in UX.
There’s also a lot of good books out there!
(note: a curated list of useful links and books would be really helpful!)
Your best bet would be to summarize what you did, whether as part of your portfolio or as preparation for your portfolio. Keep your eye out for things you would have done differently next time, as well as things you think worked out well. You want to describe your process, and at the same time tell a story about what you did and why. Remember to be clear on what you did and what your teammates did: as I’ve mentioned above, UX is typically a team process.
If you want to write the HTML and CSS yourself, that’s fine. However, beware of the problem of running down rat holes to make things look perfect, and never actually creating a portfolio that you can share. That’s a major reason I’m moving away from a static website to Wix.com — it’s so much easier to do good design if I’m not also trying to write the code.
I’ve had lots and lots of people say to tell a story, so I’ll share something about that. I had no idea what that actually _meant_ until I had a chance to a) dig deeper into what specifically folks were thinking about and b) see examples of this. One of my major problems is that writing a portfolio for a UX researcher is _hard_. You tend to have fewer pretty things to show folks than the typical graphic design portfolio might, and you may or may not have the design skills to make your portfolio pretty.
To the best of my understanding, your story needs to include as much guidance for your reader as possible. Like everything else, use your nacient UX skills on your portfolio: guide your reader through it.
Use Gestalt principles to help your reader know where to go next, and I recommend an overview (this links to my in-progress update for my website) of your major goals and results to act as guideposts.
From this page: Include as much as possible of the STAR method in your portfolio to communicate what the situation is (goal of the project), what tasks and actions you accomplished (your UX toolkit of wireframing, usability testing, sitemaps…) and what the end results were (analytics, final designs, customer testimonials).
Note that I’m still struggling with the best way to explain the end results in some of my projects, because they either were one shot things (through hackathons) or are on pause while underlying things are completed.
Get someone to look at it! Just as in everything else, you want someone else to take a look because there will be something you’ve missed, or ways in which you are not as clear as you’d like.
If that’s not an option, take a week or two, and then take another look at it. You’ll probably find typos and brainos (places where what you wrote doesn’t actually make sense), even though you are the one who originally wrote it.
(note: I expect that offering folks portfolio feedback would be really helpful! I’ve personally gotten in touch with someone from designmentors.org and have a review pending)
Find more projects to work on. Now that you have your first one under your belt, this will go more smoothly, and you likely will find it easier to identify areas to work on.
If you happen to be able to find an internship in UX (say, Outreachy), take it! Guidance is amazing.
This will help you get an idea of what the market looks like right now. It may help you decide what tools or skills to learn, or identify things you specifically _don’t_ want to do. And hey, you might find a job that looks good!
Honestly, I should have already said this, but this is easier when you have a little experience. At least in my case, having some basic knowledge makes it easier to talk to folks about UX.
Better yet is if you have a specific goal in talking to folks. For example, since I’ve been collecting data about the hiring process in Boston, I’ve had no trouble contacting folks about interviewing them. You may be able to take the tactic of asking folks about what they do in UX, potentially allowing for the opportunity to learn more about UX at their company.
Business (MBA) folk do something called an informational interview. In some cases, this appears to mean talking to folks about UX at their company. In others, it might involve the possibility of going to someone’s company and actually seeing how it works. As far as I can tell, your best bet is to see if you know anyone working at a company that includes UX folks and see if you can get any of them to introduce you. You can also message people on LinkedIn without a connection, but that may not work as well.
If you have the opportunity to present on a project you’ve done, take it. Presenting skills are very important in UX, and practice does help. Talking in front of a group of people can be scary, especially if you’re also trying to get them to hire you. Practice in a safer space, first, if you can.
If you don’t already exist online, you really should. Start a blog (I’m quite fond of Medium) about your UX experiences/learning/thoughts. Be active on twitter. Be visible in your UXness.
I’ll be chatting with more folks over the coming weeks, and will be speaking to the UXPA Boston board the first week of October. Watch this space!
I’ve been slowly moving my website from the official pelican-based version to an in-progress Wix-based version. I learned interesting things around current web development while using the Pelican version, but I found it difficult to implement the kinds of design choices I wanted to make. I also found it quite difficult to get a responsive design that _stayed_ responsive when I made changes to the CSS file.
Given that I want my page to be welcoming and easy to follow, easily choosing specific design elements is vital.
One of the most important aspects of a UX portfolio is demonstrating one’s UX skills. This means walking folks through your process and making it easy to follow and understand.
One of my major challenges was (and is!) deciding how to structure my portfolio to offer the greatest ease of use without losing too many of the specific details. Upon the recommendation of one of the many recruiters I’ve spoken with, I’ve been adding an overview page to each piece of my projects:<figure><figcaption>In this version, I offer an overview and links to more details of some of the pieces.</figcaption></figure>
If you compare this to the currently official version of my page, it’s a clear and huge difference in usability:<figure><figcaption>This doesn’t show the overall goal, what my role was, or offer much guidance. It’s also not physically structured for easy reading.</figcaption></figure>
One of my major struggles is with offering too much information. Too many details, and too little structure.
I want people to know what I did! Unfortunately, if there’s not enough structure, they won’t read any of it. If there’s too much information, they won’ read any of it. So my major task is to take what I have and create overviews; not just for the main page of a project, but for sub pages.
This is unfortunately not quick or easy! As a result, I’m working on bringing the overviews back to my pelican site as I make them, with the eventual goal of fully transitioning. Sadly, I have been unable to convince my pelican site to let me stack things horizontally. My impression is that this is one of the major improvements to my Wix site, so even though I’ll bring some of the ideas back to Pelican, they are simply not as well-designed there.
I’ll be asking for feedback before I move over completely, of course. In the meantime, it’s pretty clear to me that my Wix site is just _better_. I’ll also be grabbing what I have at the Pelican site before ditching it, as I will worry that I’d lose information otherwise.
I’m also ditching the references to Cambio Buddies. It was a valuable and useful project, but I had very little guidance for what I was doing. I made a lot of mistakes, used techniques poorly, and am generally not happy with that project. Maybe it’s a mistake to remove my first project, but I just don’t like it.
Some folks have suggested incorporating the ‘current’ and ‘complete’ design projects into a single area. I’m reluctant to do this, since the current projects are still in process: I don’t want to be presenting them as if they were finished when they are not.
Similarly, folks have suggested getting rid of the design artifacts page. I’m not completely clear on why: they are in the Projects area, and it seems helpful to let folks get to a specific artifact quickly if they so desire.
One of my early bits of feedback for the Pelican portfolio was a lack of process. I’m still not entirely clear on what was meant by that, although I suspect that the lack of overview may have been part of it.
I’ve been meeting, finding, and interviewing folks at various points in their UX careers. It’s been fascinating, and reminds me that I’m _much_ better at networking when I have a reason to talk to people.
I’ve not yet had a chance to analyze my interviews in depth thus far, but I have noticed some interesting trends.
This is a significant problem. Given that few places are hiring folks without a couple of years of experience, newbies and career changers need to find ways to get that experience.
For those who can afford it and have access, in-person UX programs like Bentley’s master’s in human factors program and Jarod Spool’s Center Centre are an excellent choice. These offer curated and guided information, connections, and practice at design. Unfortunately, these and other programs rely on proximity and available time and money, and are not inexpensive (although Center centre tries to mitigate that part).
There are also online courses which can be helpful, and bootcamps both on and offline, but these again cost money and may or may not offer built-in networking.
So how does one find work, even if unpaid? There’s a few options that I am aware of:
Options 2 and 6 may be more difficult for designers just starting out, as they are much easier to do if one has some guidance for how to approach design problems.
Mentorship is really important, especially if you cannot afford to attend school and get guidance that way. Unfortunately, it can be difficult to find a mentor, and precisely what a mentor can offer or do for you varies by the mentor.
Ideally, I think that mentors should offer:
Beyond this, it’d be lovely if mentors could offer networking help (eg: connections to open positions and folks who may eventually have open positions), and suggestions for projects to work on.
The XX UX community offers a mentorship matching program in some cities, although Boston is not yet one of them. This may be another opportunity for my project to help folks out, whether by working with XX UX (which would mean it’s only available to women), or by building on their example and making our own program.
Given how much information there is out there, a possible way to help folks out would be to offer resources that experienced UX folks agree would be useful to those who are starting out.
These resources could include basic guidance for portfolios for various design specialities, design interviews (including design exercises), and job applications, as well as structure within which to learn design processes.
Also relevant might be instruction on persuasion, on communicating and working within cross-functional teams, and on presentation skills (both creating a presentation and presenting it).
We might want to include specific information such as the use of short-cut keys within design programs (Ctrl d, alt Ctrl shift arrow keys for movement, etc), recommendations for tools to start out with and an introduction to their use, and suggestions for how to use those tools to more easily share and maintain one’s designs (since all good design involves many different folks in various different teams).
Finally, we could offer recommendations for good books for folks in various stages of learning.
One of the most important things for someone new to a field is to keep learning. Be visibly interested in and passionate about your field: it’ll communicate itself to those you are working with, and will help keep you informed and aware of what’s going on.
At the same time, don’t believe everything you read — some folks make things look more clear-cut and simple than actually happens. Reality is messy!
Don’t be afraid to try things out. No one in UX knows everything about it, and mistakes are how to learn.
Remember to mention others who had a role in any design you talk about: design isn’t typically an individual process (collaboration is important!), and hiring managers want to know that you understand and can talk about your role in the project.
If you’re interested in research, learn both qualitative and quantitative methods. Most of your work will probably be in qualitative spaces, but it’s useful to be able to measure success (are we accomplishing our goals?). It’s also helpful to understand basic data visualization techniques.
Remember to take pictures at all stages of your process! This will be hugely helpful when it comes time to make your portfolio.
I returned from Flock 2017, which was in Cape Cod, MA this year. This was my first Flock, largely as a result of my Outreachy project. I will be claiming my Outreachy travel fund for it, and likely would not have gone were it not for that fund. I’m still job hunting, and all!
Fedora folks are very friendly. :) OK, at least the ones at Flock were! Being there reminded me of the aspect of my Regional Hubs design wherein a major goal was to encourage in-person interactions because they’d increase the chances of people remaining engaged with the community. I’d say Flock definitely confirms this goal, given the number of ways in which people — including myself — were becoming more involved simply through chatting with others in the community.
I’d say one of the major effects of my time at flock was making people I’ve spoken to only through IRC and email more real. I do find in-person interaction so much better! Of course, I also really like people and being around people, and lack of a job means I am not really getting a lot of that (I’m one of those weird introvert/extrovert combination people).
I met a lot of people, although being partly faceblind and poor at remembering names made (and makes) that more complex. Hopefully people remember me, even if I can’t remember who they are!
I gave a presentation on my UX work for Regional Fedora Hubs, with the goal of helping others be able to do basic UX work on their own development projects. I did most of the talking, and Mo was helpful for moral support and answering Hubs questions I didn’t know the answer to. The presentation and handout are available on my website, and the video will also be available there once I have access to it. I’m not certain how likely others are to use that information, however. I did find that people asked relevant questions at the end, suggesting that not only did they follow my talk, but they were interested enough in it to be curious about things I hadn’t mentioned.
I appreciated the chance to present to a new audience, and to gain additional practice in presenting and preparation thereof.
I also appreciated the opportunity to attend various sessions on UX, both to see how other people do certain tasks and to add additional tools to my toolbox (microtesting, “SUS” or System Usability Scale, and focus group-based usability testing all come to mind).
I enjoyed learning about various aspects of Fedora that I hadn’t yet encountered, whether specific technical concepts like modularity and project atomic, or being able to attend and contribute to the diversity team’s session. I also liked being able to get caught up on what’s been doing on with Fedora Hubs since Outreachy. I’ve been out of the loop there because jury duty for 3 months and various temp jobs make it difficult to attend the weekly meeting.
I created my first badge, albeit through a very simple change to an existing one. Additional experience with Inkscape with others around to guide me is always appreciated, given that I’d like more experience with basic visual design!
I am not sure yet how I might best continue to offer my skills to the Fedora and open source community, but this conference has definitely confirmed my interest in doing so. Thank you Flock, Outreachy, and the organizers and participants thereof!
We’ll see if I can figure out some way to make the next Flock. :)
I’m really pleased by this idea, and very glad she suggested it. However, before I bring my ideas to the board and get advice and help, I want to have slightly more clue than I currently have.
The best way I can think of to get more clue is to talk to people in the UX space. I’d like to talk to other people who are new, people who do the hiring, and people who are working in UX with other UX team members.
Based on my instincts and some of the suggestions on the FB discussion, I suspect people trying to get into UX full-time struggle with:
Some off-the cuff ideas of ways to help with these:
I have a lot of interesting ideas above, but I would need to know more about what hiring managers are looking for to understand what would be most useful.
For example, in an ideal world, what do hiring managers want to see from candidates? What would be most useful to determine if they want to take a chance on someone? What do they want to see them do, have done, or be interested in doing? What do they _not_ want to see? What do they struggle with figuring out, but very much want in their employees?
Of course, not only do I need to know what hiring managers look for, but I’d like to better understand what people look for in their co-workers.
Such as, what do UXers find most useful when working with other UXers? What do they especially dislike? How well do their hiring practices seem to tease these out? What do you most appreciate in your co-workers?
If you are in UX, or trying to get into UX, talk to me! Comment or email me!
I’m back with more about Patternfly’s navigation bar user dropdown.
I’ve done a brief, remote, contextual interview with the developer who originally asked for this to be researched. With this, I confirmed a few things about what his concerns are:
I’ve started a conversation with the UX researcher at Patternfly, Sara Chizari. In large part, I wanted additional perspectives on the problem. I was also hoping to learn if there is existing research on this topic that I’d missed.
My inclination is that the major goal of this research is two-fold:
I expect that these will also change with the display screen size: limited space constrains what can be at the top level.
I’m not yet certain of the best way to go about figuring this out, which is part of what I’m discussing with Sara.
In this particular case, the dropdown is not expected to contain high-use items. While useful, I wouldn’t expect things like ‘settings’ and ‘log out’ to come up during the course of everyday use of an application or webpage. It’s difficult to be sure what other categories of items people are likely to wait to use here, but the real-world examples I have are suggestive:<figure></figure><figure></figure><figure></figure><figure></figure><figure></figure>
It looks like basically everyone includes settings and sign (or log) out. Many also include help. Of these, I would expect that sign out would be highest use, especially for those folks who access the applications on computers that are not their own.
Because these won’t be high use items, I’m not yet sure how best to create tasks for people to do during a usability session. I don’t think I want to overemphasize actions that they might not otherwise do, as it’ll make it somewhat difficult to identify the highest use items. At the same time, I need to have people try different prototypes of the menu and menu area to see how they turn out in practice.
My instinct suggests that we will specifically want to test the usability of a few different things:
These feel like they will address the ‘dropdown vs not dropdown’ item number cuttoff point on various screen sizes, and the specific menu items that I believe to be the most frequent use.
I may want to identify the most used items in those dropdowns, before I go into more specific testing as per the above list. I’m not yet certain of the best way to approach this, however.
Sara will be doing some literature research this coming week, and will then be busy until mid-Sept on her own projects. I’m hoping to figure out the kinds of things to be testing with the aim of starting usability sessions in September.
In the meantime, due to conversations with the local UXPA group on Facebook, I’ve started investigating both problems and potential solutions facing UX newbies and career changers within the Boston area. The major goal here will be to figure out what types of things are interfering with getting new people into UX jobs, coming up with concrete things to do about them, and figuring out how to make those things available to people locally. I’d love additional perspectives and ideas, since I am only one of many folks trying to get into UX, and will definitely not have thought of all the obstacles (or possible solutions!).
I’ve met with Mark, the owner and developer of Querki, a couple of times now. I shall now do my best to summarize my understanding thereof, with the purpose of identifying any obvious gaps in my knowledge and any clarifications that may be needed.
It is a way for you to keep track of your information, the way you want it, not the way some distant programmer or corporate executive thinks you should. You should be able to share that information with exactly who you want, and it should be easy to work together on it. You should be able to use it from your computer or your smartphone, having it all there when you need it.
Everyone has a lot of information to keep track of, much of which they would also like to be able to share and discuss with others. Querki offers a customizable interface in which to manage, display, discuss, share, and explore small to medium data sets with small to medium-sized groups.
An existing example of this is from the Cook’s Guild in the local SCA chapter: they have recipes from specific time periods, and they figured out reconstructions of those recipes so that they can be made nowadays.<figure></figure>
As you can see in the screenshot above, the recipes are categorized by type of food, period of food, and culture. Clicking on any of those — also known as tags — will bring you to a list of relevant recipes.
Many of Querki’s useful abilities are currently only possible using the Querki programming language (QL, said as ‘cool’) — such as finding a recipe for 14th century French pancakes in the above cook’s guild space. In the future, the plan is to make common tasks easy to do without the use of QL.
To view a Querki space, one only needs a link to said space. Precisely what a space will look like varies depending on the desires of the owner of that space.
One of the topics that Mark and I are currently discussing is the idea of a basic default structure for a space . This would hopefully mean that those who don’t want to spend a lot of time structuring their space will still have usable spaces for people to access, discuss, and interact with the data. For those who want to affect structure, that can be done when one has time and inclination, smoothly allowing the transition from a basic Querki space structure to whatever modifications are desired.
A Querki space is meant to be a place for information to be stored and shared. To do this, however, one needs to tell Querki how you want your information to be structured. A model is how you tell Querki the structure you would like for your information.
For example, a model for a CD might include properties for the album title, author, song lists, genre, and publication date, as well as an auto-generated name of the model. Properties can be added when the model is first created, as well as after the fact.
Properties have types. Types include the tag type, the text type, the photo type, and the views type, among others. Properties can themselves have properties, such as with tags. Tags are both the name of a thing and have the possibility of pointing to a related model. Tags may have a description, visible when the tag name is clicked, or simply show a list of things with that tag.
Views are ways to display models. The current default view shows a list of things with that model associated with it. There is also the possibility of a ‘print view’, which will tell Querki how to print the model.
Models will have instances of that model: rather than the generic properties that models contain, instances contain information specific to the instance of that model. In our CD model example, you might have the CD Zoostation by U2, as an instance of the CD model.
In addition to models and their associated pieces, Querki has pages. These are unstructured, and may be understood as a report from a data base, or a wiki page.
Currently, there is an idea of an ‘easy’, ‘medium’, and ‘hard interface. These largely describe the degree to which one needs to be able to program to get the interface to do what you want.
It is not currently very clear to users what their options are for using QL.
Search is very basic right now, with searches being within a Querki space, on plain text strings. The goal in the future is to include the ability to search across spaces as well as objects, including tags.
There are currently icons for editing a page, refreshing a page (with your changes?), and publishing a page (for those spaces which do not want changes to happen immediately during editing). Are these reasonable things to have as icons? Do they need text also/instead?
Mobile is very important! Consuming a page should be possible even on small phone screens. Editing should also be possible on a mobile phone. Designing a page for a phone isn’t likely due to small screen, but planned for tablets.
Data manipulation/query building talks about the need to do some basic filtering and sorting of the information in an instance. We need to figure out the most common queries of this type, and see how many can be abstracted away from the underlying programming language for use by anyone/everyone.
Specific pages in need of (design?) work: front page, help, contextual help, model design page/advanced editor. The programming UI needs help (see the design page), and likely needs a simple IDE.
Querki spaces are mostly publicly visible, which should help come time to improve the login page/start page.
Tag names cannot currently be the same name as the model associated with them, due to the fact that tags point to a related model rather than containing it. This may need to be invisible to users to avoid confusion?
I’m working on a toy project with a Northeastern student to get us both more experience with UX.
The student I’m working with, Radhika Sundararaman, came up with the idea of a robot that would carry recycling bins from someone’s home to the dropoff point. This is most relevant for people who live in condo associations and other larger housing complexes with the dropoff for trash and recycling at some distance from their homes.
We expect the main users to be folks who are unable to walk, unsteady on their feet, or do not have the strength to carry a bin. We imagine this to be relevant for older adults and differenlty-abled folks.
In addition, we think there is a market here for folks who are too busy or too forgetful to get their trash out regularly.
Our focus for this project is the user interface.
We have done quick interviews of a few different people, and came up with 5 personas.
These include an older adult couple, a single mom with two kids who works full-time, another mom with three kids whose husband is typically away on business, an office manager, and one adult of three whose household often forgets to bring out the recycling.
While exploring the personas, we identified a need for a website, a mobile app, and buttons on the robot itself.
Each persona includes important information about the context of each person’s trash situation. Some of the more relevant points include:
How do they find out about changes in trash pickup?
How far are they from the pickup location?
How much trash do they usually create?
What sorts of difficulties do they run into?
During our task and scenario analysis session, we decided that one of the 5 isn’t a user we will focus on at this time, and another was covered pretty well by the first three users. We used sticky notes and a handy empty wall to organize our thoughts and discussion.
We started the process by writing down what users would do in the case where there were no errors. We made notes of where errors might occur, and things we might like to include as options in the future.<figure></figure><figure><figcaption>Who are we talking about? What are the main points to keep in mind? How might they want to interact? What are the goals?</figcaption></figure><figure></figure><figure></figure><figure><figcaption>The actions that users might need to do, problems they might run into, and ways we might handle those problems. Also a short list of things to keep in mind for the future.</figcaption></figure>
We translated those into step-by-step descriptions of how a user would do their ideal actions with our software. Finally, we investigated those situations where things didn’t work out quite right for one reason or another, and explored how that might translate to our software.<figure></figure><figure><figcaption>What are the situations for ‘things working as expected’? What do we need to have for settings and configurations?</figcaption></figure>
Once we had gotten to a point where we felt ready to start sketching, we also translated our sticky notes to a digital format for greater ease of access and reference. We do not have a centralized location in an office building to leave them, so this is the next best thing.
We will not be creating the robot itself, as this project is meant to complete before Radhika returns to school in September. Neither of us has the technical expertise to focus on construction, and my experience with robots strongly suggests that this is not a simple problem to solve.
We are assuming a few things about the robot as part of our design process:
Our next steps are to start sketching our ideas and discuss what we have each sketched. This will allow us to get onto the same page about our ideas, and come up with more effective and useful interfaces as a result of the exploration we will do.
I’m playing around with Wix for my website, in part because it’s a giant pain to change things around in my (still official) Pelican-based website, and in part because it’s useful to have the very ‘what you see is what you get’ perspective that Wix offers. I’m still deciding where a good point between ‘offer an overview’ — missing from the pelican version — and ‘not enough details’ — true of much of the Wix version right now — is.<figure><figcaption>Pelican version of my site</figcaption></figure>
For the moment, any major changes that I think are important to include, I’m trying out in Wix first, and then figuring them out in Pelican. That which is frustrating me most right now is the apparent lack of grid support in Pelican, since that would make so many things look nicer and be easier to follow — indeed, that’s why I don’t have much overview in Pelican right now.
I’m hoping I can get Pelican-alchemy to work as a theme, as it appears to support bootstrap, which itself supports grids. Unfortunately, I can’t figure out how to get it to stop ignoring the settings I have in the style.css file. And, because it’s not as professional-looking without that, and it’s hard to see what things look like there without publishing them first, it’s slow going to figure out. I just want a clean style and grids!
Alternately, I need to continue to move things over to Wix and just give up on Pelican. But it’s a lot of work. And slow. Which is why I’m trying to get obvious wins over to Pelican in the meantime.
I’ll be meeting up with the person who is working in Querki next week, to get a decent basic understanding of his goals and needs, as well as to figure out the reasoning behind some of the current decisions.
I need to get in touch with people about doing a contextual interview with them about putting their recycling out for pickup. This is for the project I’m working on with the Northeastern student.
I’m also hoping to get a contextual interview with the developer who originally had concerns about user dropdowns. He has provided some screenshots of the kinds of places he runs into the problem, so I need to integrate those into our shared google doc, and figure out some next steps if he’s not willing to do a contextual interview.
I also need to grab some time to continue with my review of the accessibility document in patternfly.
I am thoroughly confused about the status of my RedHat application. Theoretically, I was supposed to hear something after 5 days when I went through Mo for applying. Of course, I was also supposed to have had three applications through her, and only one managed to actually associate with her name. As of right now, it still says ‘manager review’ — whatever that means. That’s better than the other two, which say “no longer under consideration”. Confusingly, the job titles are all very different from what I actually applied for (the one I’m “under review” for talks about doing development, which… not so much).
I’ve also got an application in with Wayfair, whose UX team is fairly large and has openings at multiple levels of skill. We shall see.
I was contacted by someone at Onward Search, yet another UX recruiting agency. He seemed pretty impressed with my background, and optimistic about being able to find me some possibilities. We’ll see — I’m working with a _lot_ of UX recruiting companies at this point.
I’m happy to find time to talk about it; in person or skype work for me. :)
Thanks for link!
That was a long and tiring experience, but now I’m not able to be called in again for it for 6 years.
I’ve been helping out with Patternfly. I started by helping to fix easy bugs in an effort to get a good understanding of their processes. I’m now helping to edit their accessibility document and working with one of the developers on a UX research project.
The UX research project in question is to determine how user friendly the common pattern of the user (profile? settings?) dropdown actually is. For example, see this upper-right dropdown:
After opening the menu:<figure></figure>
Under ‘More options’:<figure></figure>
The developer I’m working with had concerns about the extra clicks required to get to items in the menu, the extra processing time to read and interpret those items, the speed with which the menus actually open, and the quality of the animations for the menus.
This dropdown is very common for tools within RedHat, since they are generally based on patternfly’s pattern library.
My first goal was to get an idea of what, if anything, online research says about this. Curiously, I was unable to find research specifically on the user dropdown pattern, even though it’s everywhere nowadays.
That said, I did confirm my suspicion that it’s generally better not to hide high-use items behind a menu. There were a variety of reasons for this, including the ability to find out what is possible, remember what is where, and the extra time to locate the actions.
This suggests the need to know what, if anything, within the user menu is likely to be high-use. Unfortunately, the example I currently have is not a real example, and I’m hoping to get some real-world examples of what the developer has struggled with soon. This will make it much easier to identify the tasks that might cause one to need to use the user dropdown, and gather information about how high-use those might be.
One possibility I’ve suggested is that if there are some high-use items in there, they might be better off outside of that dropdown. The following example assumes that settings is the highest use option, and that we have minimal screen real-estate (on a mobile phone, perhaps).
For example, instead of the existing top-level controls:<figure><figcaption>Balsamiq version of the controls</figcaption></figure>
Have the settings control be at the same level as the others:<figure><figcaption>Now you can use the settings without the dropdown</figcaption></figure>
On a larger screen, I’d suggest that the settings gear — while in common use — should be the word ‘Settings’ to improve usability.
Once I get some real-world examples, I think the next step will be figuring out what questions we want to get answers for. Since we’re hoping to get an idea of how much this particular pattern affects users — within RedHat and perhaps more generally — we’re going to need to figure out what sorts of tasks are likely to send people into that menu.
I’m also going to want to select some good examples of the situations we’re most interested in. On top of whatever real-world examples we think are most relevant, we’ll want to offer users other options. If, for example, we suspect that settings and logout are the most likely options to use, we’re probably going to want to offer interfaces with one or both of those outside of the dropdown.
Currently, I’m waiting for information from the developer before I can continue.
A friend of mine has been working on a project for a few years now, and it occurred to me that I could offer him UX feedback on it. He’s working on it part-time nowadays, so I’m currently waiting for some background information from him. I need to know where is it so that I can see it, how he would describe it to people, and what he wants people to be able to do with it.
I’m recently started discussing a possible project with a technical communications Masters student from Northeastern. She’s interested in getting more experience with UX, and I figure it’ll offer me more experience and mentoring people isn’t bad.
We’re currently trying to identify areas of UX that we are interested in, both in terms of domain (e-commerce? Machine Learning? IOT?), and in terms of specific aspects of UX (usability reviews? Design updates? Or specific pieces like transitions as related to optimization of interstitial anxiety or hapnotics?). If nothing else, time spent researching some of these should be time well-spent.
And, I’m still job hunting. Which is still frustrating, because a year and a half of experience means people rarely get back to me. Or it could be something else, but because no one gets back to me, I have no way to know.
In the cases where I apply through someone at a company, they usually say something like “we’re going with someone who more closely matches our needs”. Maybe that’s amount of experience? Maybe something else. Who knows?
I’m keeping an eye out for temp and contracting positions, because they can lead to full-time and are at least paid experience. We’ll see.
This year’s Flock is more action-oriented compared to previous Flocks. The majority of session slots are hackfests and workshops; only one day (Tuesday the 29th) is devoted to traditional talks.
The registration system allows you to submit 4 different types of proposals:
There is no session proposal limit. Feel free to submit as many proposals as you have ideas for.
Our CFP ends June 15 so you have one week to get those awesome proposals in!
How can you ensure your proposal is sufficiently strong enough for acceptance into Flock? Here are some tips and guidelines:
Fedora creates an innovative platform for hardware, clouds, and containers that enables software developers and community members to build tailored solutions for their users.
If you can explain the connection between your session and this goal, you’ll make the proposal stronger. Even if you are not directly working on a hardware, cloud, or container effort, you can relate your session to the goal.
For example, say you’d like to propose a Fedora badges hackfest. Task the badges hackfest specifically with creating badges for activities associated with efforts aligned specifically with hardware, cloud, and container to strengthen it.
If you want to propose a Fedora badges workshop, that’s totally cool. You might want talk to Marie Nordin or Masha Leonova, and see what their plans are, give them a heads up, and coordinate or even propose it together with one or both of them.
The committee reviewing proposals occasionally sees duplicate / overlapping topics proposed. Generally, the committee chooses the proposal that has the subject matter experts most involved in the topic. A weak proposal on a topic has no indication of involvement or coordination with subject matter experts most actively involved in a topic.
Think about who you are giving your talk to or who you want to show up to your workshop or hackfest. If you’re proposing a Fedora Hubs hackfest, are there enough Pythonistas in Fedora to help? (Yes, yes, there are. )
Tailor your content for your audience – while you may be able to get folks familiar with Python, they may not be familiar with Flask or how Fedora Hubs widgets work, so make sure your proposal notes this material will be covered.
General user talks are discouraged. This Flock will be focused on empowering Fedora contributors and actively getting stuff done, so make sure your audience is a subset of existing Fedora contributors.
A major focus of this year’s Flock is taking action, so talks that inspire action and hackfests / workshops where action will take place are going to be strong proposals.
The Flock planning committee is looking forward to seeing your proposals!
Measuring things only makes sense if you know what you’re measuring, why, and what you intend to do with it. Otherwise, even if you _have_ numbers, they don’t actually have any meaning. So what’s the point?
I’m trying to keep myself in the UX game, which is complicated by the grand jury thing lasting through the end of June and making contracting positions difficult to do right now. My mentee (who is really only slightly behind me in her UX path) commented that she’ll be looking to work with non-profits and government sites such to get more experience.
She pointed out https://www.catchafire.org and https://www.taprootplus.org/ as possible places to hunt through. A quick glance at catchafire when we were co-working to get an idea of what possibilities there were, and I saw something called a ‘website audit’ for the American Cancer Society.
“Huh,” says I. “What is a website audit?”
Looking at their list of needs, I see that they want a report that includes an outline of the organization’s goals for the site, feedback on the current site’s UX in general (they give specifics, but I think my summary is accurate), and recommendations for improvements to help achieve the desired goals.
Ok, interesting. This sounds a lot like UX research, mostly. With some prep work to figure out what they mean by ‘organizational goals’ and who their users are. Given that these goals could as easily mean ‘goals that someone in the organization thinks sounds good’ as ‘goals that were researched throughout various facets of the organization as well as users’, I think that’s going to be one of the first things I want to figure out.
They already have a site and some goals, which at least means that I should be able to work with them to figure out whose goals those are, and how specific they are. I’m not entirely sure what they mean by ‘built out site’, although I suspect they may mean working prototype. I don’t _think_ they mean the existing site?
They specifically list millennials as a target market, and I’m really curious as to what they actually mean by that. They say they want to engage young professionals, which is… rather non-specific, but certainly better than nothing.
I’ve got a call with them Friday morning to see if we’re a good fit, and I’m going to focus on what they mean by organizational goals and who their actual and prospective users are. I strongly suspect that my QE experience will combine nicely with my UX research experience for this particular project, so we shall see. And hey, it’s a good cause!
I’m also noting that they suggest up to nearly half-time work hours for a month and a half. This may be too many hours what with three days eaten by jury duty, but we’ll see.
I do hope it’s not an SEO website audit (which is mostly what google says about websites audits) as I’ve no strong sense of those, but given that SEO shows up nowhere on that volunteer job description I doubt it. Worst case, I adjust my thinking and do some online research to see what’s relevant. This looks useful in that case!
We’re prepping the regcfp site for Flock to open up registrations and CFP for Flock. As a number of changes are underfoot for this year’s Flock compared to previous Flocks, we’ve needed to change up the registration form accordingly. (For those interested, the discussion has been taking place on the flock-planning list).
This is a second draft of those screens after the first round of feedback. The first screen is going to spoil the surprises herein, hopefully.
On the first screen, we announce a few changes that will be taking place at this year’s Flock. The most notable one is that we’ll now have partial Flock funding available, in an attempt to fund as many Fedora volunteers as possible to enable them to come to Flock. Another change is the addition of a nominal (~$25 USD) registration fee. We had an unusually high number of no-shows at the last Flock, which cost us funding that could have been used to bring more people to Flock. This registration fee is meant to discourage no-shows and enable more folks to come.
This is the screen where you can fill out your badge details as well as indicate your personal requirements (T-shirt size, dietary preferences/restrictions, etc.)
So depending, the next section may be split into a separate form or be a conditional based on whether or not the registrant is requesting funding. The reason we would want to split funding requests into a separate form is that applicants will need to do some research into cost estimates for their travel, and that could take some time, and we don’t want the form to time out while that’s going on.
Anyhow, this is what this page of the form looks like if you don’t need funding. We offer an opportunity to help out other attendees to those folks who don’t need funding here.
This is the travel details page for those seeking financial assistance; it’s rather long, as we’ve many travel options, domestic and international.
This is a summary of the total funding request cost as well as the breakdown of partial funding options. I’d really like to hear your feedback on this, if it’s confusing or if it makes sense. Are there too many partial options?
This screen is just a summary of everything submitted as well as information about next steps.
Do these seem to make sense? Any confusion or issues come up as you were reading through them? Please let me know. You can drop a comment or join the convo on flock-planning.
(Update: Changed the language of the first questions in both of the 3rd screens; there were confusing double-negatives pointed out by Rebecca Fernandez. Thanks for the help!)
Ryan Lerch put together an initial cut at a Flock 2017 logo and website design (flock2017-WIP branch of fedora-websites). It was an initial cut he offered for me to play with; in trying to work on some logistics for Flock to make sure things happen on time I felt locking in on a final logo design would be helpful at this point.
Here is the initial cut of the top part of the website with the first draft logo:
Overall, this is very Cape Cod. Ryan created a beautiful piece of work in the landscape illustration and the overall palette. Honestly, this would work fine as-is, but there were a few points of critique for the logo specifically that I decided to explore –
So here were the first couple of iterations I played with (B,C) based on Ryan’s design (A), but trying to take into account the critique / ideas above, with an illustration I created of the Lewis Bay lighthouse (the closest to the conference site):
So here’s the next round; things I tried:
One more round, based on further helpful Mastodon feedback. You can see some play with fonts and mashing up elements from other iterations together based on folks’ suggestions:
I have a few favorites. Maybe you do too. I’m not sure which to go with yet – I have been staring at these too long for today. I did some quick mockups of how they look in the website:
I’ll probably sit on this and come back with fresh eyes later. I’m happy for any / all feedback in the comments here!
Some bits are easy enough: I’ve got a photo now, and there’s a section about me in which one can take a look at my medium, what I like to do in my free time, and how I got to UX (this is too long and I need to cut stuff).<figure><figcaption>My main page</figcaption></figure>
Tabs, though. Tabs are _hard_.
As I mentioned in my last post, I’m using Pelican to generate my site. I’m using restructured text plus CSS to write most of my content.
I first tried to use responsive tabbed navigation from Codyhouse because it looks really nice. Unfortunately, CSS is _extremely_ picky about order and I don’t even entirely follow what’s happening. Between the responsive Pelican theme pelican-blue I’ve modified (and which apparently is no longer… responsive? I broke something somewhere), and the figures and button code bits that I added, I get really confused as to what’s going on.
I pulled the CSS and HTML into notepad++ to get things lined up nicely and in a larger visible space than in the relevant codepen, which meant that I was more able to figure out what was going on and learned a whole lot about CSS. Unfortunately, although in that instance I got the base theme’s responsiveness working again, it collides with the responsive tabbed navigation.
Right, so the pretty but frustrating responsive tabs took up most of my time yesterday. I looked a few other links which talked about pure CSS tabs, but they looked like they would break if I breathed at them wrong. I did try one of them, and my suspicion seemed accurate in that case, which meant that when I tried to add it to my existing site it basically did nothing at all.
In the meantime, I’ll just make separate pages for my “Completed Projects”, “Design Artifacts”, and “Current Projects” portfolio views. I think I may be able to nest them under ‘portfolio’ in my navigation menu, but I’ll have to poke at Pelican and how it works again to be sure about that one.
After all this, though, I think I know how to make a horizontal TOC for my regional hubs portfolio. Which I need to do.
During a recent conversation during a recruiter technical interview, the interviewer commented that my website wasn’t very welcoming or likely to encourage people to look further.
Now, one of the things she said was that I had no photo of myself. This is actually something I’ve been reluctant to put up, in part because I want it to not matter. But, perhaps, it does matter.
Upon reflection, there really isn’t much there about me as a person, rather than as a QE person turned UX designer. Even that part isn’t especially well described, so someone looking at my site has no real sense of how my background informs my UX skills and processes.
Let me show you what I mean:<figure><figcaption>My home page</figcaption></figure>
This is everything currently on my home page. It’s functional enough, but it can be difficult to decide what to click on and why. And there’s really only professional stuff: contact info, resume, portfolio, and a little bit on accessibility.
My former mentor through Outreachy commented that this page, my resume, and my portfolio don’t really communicate my enthusiasm about UX. This is true, in part because I was trying to be professional, which rarely goes along with enthusiasm. She pointed out that my enthusiasm is clear on this blog, and that I need some way to encourage people to go here and read about my internship.
She also pointed out that I need an obvious link from here to my professional side: my portfolio, and LinkedIn. (Mind you, the description of my internship on LinkedIn needs some work.)
So, task one: decide how best to get people on my website interested in looking at this blog. Perhaps also decide which entry point to offer: maybe there’s an especially good post I’ve got up that I want people to look at?
Right, so getting people aware of my enthusiasm is great. But what’s going to get them connected enough with me to bother exploring further?
Well, I need a photo of myself. Selecting a photo might be simple (use what I’ve got elseweb), or maybe I want to have it _say_ something about me. What it should say, I’m less sure about.
Maybe I want banner images on the approachable pages: my main page, and something about me and my background.
Task two: I need to talk about myself. I likely won’t talk about my relationship structure or anything, since that’s more personal than I want to get. But I could talk about my garden and pond; the cats, plants, and people I live with; my interest in wandering around wooded areas and kayaking. I could mention that I play World of Warcraft. I could probably talk about my general liking of people. And living things, really — if you’re alive, I’m probably interested in learning more about you.
Also, pictures of things. People like pictures of things!
Task three: I need to talk about my background. Starting with a computer science undergrad degree, meeting fellow computer scientists and Linux enthusiasts. Those enthusiasts helped get me into an internship in QE at a Linux company, and from there I continued on to do QE at two other Linux companies. I’ve tested a wide range of things, from drivers to databases to desktop software to wireless networking. I tend to do a lot of writing: it makes it easier for me to have references for things and it makes it easier for other people to be able to read what I’ve written. I eventually left QE in part because of my frustration with usability bugs not being addressed, and the amount of struggle involved in getting people to listen. I was doing QE on Linux software for nearly 10 years, and using it for a few years before that: I’ve got pretty good open source technical skills.
I was interested in psychology research, and after some initial online classwork, I realized that I was never going to get into graduate school without some research experience. Volunteer work at a lab near my home meant that I got into a Master’s program at that school the following year. That Master’s degree involved a great deal of running research studies, collecting data from those, and analyzing that data. As a result of that time, I got a lot more comfortable interacting with participants, and figuring out what to do with the data — often involving other people’s ideas and perspectives on the best approach. After the master’s degree, with a great deal more work and time, I got into a psychology/human-robot interaction Ph.D. program. This was fascinating stuff, and meant that I had even more practice creating a research plan; running a research study; and collecting, processing, and analyzing the data. Unfortunately, I did not complete that program, and had to reorient my career plans.
During that reorientation period, I considered the many people I knew in UX. I recalled how frustrated I’d been when usability issues were closed because “they weren’t bugs”. I thought about how much I enjoy doing research, learning about people, and what they are doing and why. I had a lot of discussions with current UX professionals, and they generally agreed with my feeling that UX was the right way forward for me. At that point, the task was to figure out how to make the transition.
A year and a half later, I’ve attended multiple UX meetups, went to the UXPA conference, read a bunch of books and websites and blog posts. I’ve done a couple of UX projects to help focus my learning, a hackathon, and the recent internship. This is amazing stuff, and it’s clearly taking off.
So great, that’s a lot of stuff up there, even after trying to trim it down. How do I focus my background in a way that helps people see a) my open source, linux, technical background, b) how I got to UX, and c) is interesting enough to keep them reading.
Do I mention that the way I got online in the first place was by constantly asking questions of the local sysadmin at the college I was in at the time? I’d never seen UNIX before, but I wanted to understand it. And he was willing to answer my questions. These were UNIX boxes in the campus library, where I spent much of my time.
This was handy later on, because it meant that Linux wasn’t that foreign an OS to me when people mentioned it and the possibility of using it. Sure, the install process at the time was really confusing, and it was wonderful that friends of mine helped me through it the first time or two.
Do I even mention all the research that I did and am doing on UX, or is that something that belongs in the porfolio section? How does one “show your work” without showing too much work?
What about the fact that my website is itself technical? I’m using the Pelican static website generator, with a theme that I’ve been modifying. This has meant trying to figure out how to do things like make images have captions (the better images and figures plugin plus some modification so that I can set the width in the restructured text syntax rather than having it default to the actual image size), figuring out how I might have my images be expanded inline to full-size on click (still working on that one), and figuring out how to make images be links (“target” apparently). I’m also going to need to figure out tabs (or pills) and buttons, if I want those.
I don’t write code, but that doesn’t mean I can’t modify existing code to do what I want.
So, I’ve mostly talked about content so far. That isn’t all that is involved with being a welcoming website, however.
I’m considering adding buttons to make the bits that I want people to click on more obvious. Everything is currently links, except the overly cryptic social media section on the side which are instead icons.
I’ve not yet shown you the portfolio page, so let’s get to that:<figure><figcaption>Portfolio main page</figcaption></figure>
At least the portfolio has pictures, right?
My mentor suggested adding an alternative view or section at the top in which there are thumbnails of particular design artifacts. She was worried that people might not want to go through an entire project, and might therefore miss the variety of different design methods I have used.
Great. I see how this might be useful. How do I make it not overwhelming, though? There’s already a lot of stuff on this page…
Maybe tabs? Or pills (which term I used when looking up how to do tabs in CSS)? Have the first, default, section be the portfolio organized by project. Have another one which is organized by artifact. Maybe a third for current projects like this redesign?
What about reference statements? My mentor said she’d be happy to provide one, and I can definitely see how those’d be useful. But where do I put it so that it’s visible without being too crowded?
Another reviewer of my portfolio suggested the possibility of a table of contents for my internship portfolio:<figure><figcaption>There’s 11 sections on this page!</figcaption></figure>
This seems like a perfectly reasonable suggestion, given there’s 11 sections on the page, all of which have images and a brief description.
I can’t figure out how best to do it without taking up a ridiculous amount of space, or making it hard to interpret. ToC tend to be a list of items top to bottom. That seems ill-advised.
I was considering trying to create a box in which I have an invisible table that holds the links to the rest of the portfolio. I can’t decide if that’s a terrible idea, though. I probably need to see what other people do for table of contents-like things!
I’m also working on presentations for the work I’ve done, and for About Me. I’m not sure if that’s the right kind of thing to include on my website. Will have to consider on that one.
I’m currently working on my website redesign and presentations, getting involved with Patternfly Design, and was impanelled on the grand jury for my county for the next three months.
Oh, and job hunting. Which is a bit complicated by the grand jury part!
It’s not done, but it’s very close. Certainly close enough for feedback.
If anyone is interested or willing, please check out the Regional Hubs piece of my portfolio at https://suzannehillman.com/pages/fedora-regional-hubs.html
There are just few days left, then the submission period for the Fedora 26 Supplemental Wallpaper ends and the voting will be open. Time for looking a bit behind the scenes. So far we had 94 submissions, that is again the average we had over the last contests.
The quality is also again average, compared to the time we started Nuancier its much lower. I have a strong feeling we have a lot of people just submitting something to get the badge. We have to get to a stage with an higher quality again and I started this time also to reject for quality reasons, from the 94 submissions stay after 83, so 11 rejections. I think thats record, but its not for quality reasons most I had to reject for copyright violations. Its a bit hard for me that some Ambassadors have no idea about licensing, and that they are not the author/creator of a picture even the real creator has licensed it CC0. So this time all this things was direct rejected, no second chance and I think I will keep it that way. Why sould I invest more work as necessary especially it doesnt get honored and I get insulted later on for it.
It cost me an average of 6 minutes just to moderate a submission and award the badge, not to mention that I have to do a legal research for them which costs an average of 2 hours a submission. Not to mention that there is also time needed for the creation of the election, for the article in Fedora Magazine which anounces the start of the contest, the article in the Community Blog which reminds you to go for the vote and and and…. Its more as a full month work just for that.
So for the next election there will be some changes more according to the submitters who submit work of others. I definitely will deny submissions from other wallpaper services/pages. Some other things will follow but require some technical changes in Nuancier, back to quality back to honor the people who create things for Fedora and work for doing it. Not the ones who search for 10 minutes in the internet for a free licensed picture and submit it but later on are the loudest ones, that they have submitted.
Thats all for now and now my usual 5 favorites amongst the submissions
Huh, fascinating. Didn’t occur to me that rectangles had the option to be links. Thanks!
I’ve been working on making a portfolio of what I did for the Fedora Regional Hubs project. Did you know I did a _lot_ of stuff?
I mean, I was definitely busy getting things done throughout. I knew this. Summarizing what I did in a way that someone else can follow is surprisingly complicated. There’s a lot of information scattered around my email, pagure tickets, throughout this blog, and on my latop.
I’m really glad that I was blogging the whole time, because it makes it a lot easier to reconstruct what I did. But boy. This is very time-consuming!
I am glad that I decided to try starting with a presentation outline: while the presentation isn’t done, it’s started, and it helped give me focus for the summarizing I have been doing.
I’m also glad that I am able to ask Alex Feinman for feedback, as it has been very helpful to be able to talk to him about it. And that I could ask a million questions of Mo both during and after the internship.
Even just the high level outline I wrote last night in a fit of comprehension looks like a lot:
Feedback and iteration
I appreciate this! At the moment, I’m still not sure if it’s possible to have an entire line in a table be clickable. I did figure out how to tell people to turn on ‘clickable’, although sadly after my last usability session. Next time, clearly.
My entire life, I have been prone to getting stuck in the details of a thing. It’s one thing to know this, and another to continuously find ways in which it affects me and for which I have developed workarounds.
I’ve learned to recognize that sudden exhaustion means that I’m stuck in the details and need to take a break.
Whether it’s my surroundings, a particular task, or a website, details are likely to distract and overwhelm me. This may or may not tie in with my ability to notice details that others overlook.
I suspect it’s much of why I have trouble with clutter in my surroundings, whether at home or in stores and restaurants. I suspect it may also relate to my difficulty with noisy surroundings.
I was reminded of this tendancy of mine during the recent outreachy project. Of course, I was also reminded of the many workarounds I’ve developed to handle it.
When working on CSS, I started to wonder if the difficulty that I have with writing code is purely about the number of details involved. I understand coding fairly well, and have no problem talking about it with those who do it for a living. At the same time, trying to write code usually results in me being exhausted and frustrated, and not actually successful at creating the code. Modifying code is always much easier, I suspect because there’s simply less to deal with and I am less likely to get stuck.
Using CodePen helped, I suspect in large part because I could see the immediate effects of what I was doing. My strong tendency to break problems into smaller pieces also came into play, as when I was stuck on a particular aspect of the CSS, I’d just clone my Pen and take out the bits that weren’t currently relevant.
Transcribing from audio or video means I’m faced with a wealth of information that needs to be expressed in a written way. For the first in a set of items that need transcription, I always find myself getting stuck and writing down _way_ too much stuff.
I tend to need frequent breaks when transcribing, simply due to the sheer amount of information and the fact that I will start to forget what’s actually important. After I’ve done the first in a set, it is usually much easier for me to identify what’s important and what’s not, so the rest will go more quickly.
Similarly, when working on a task that is part of a larger project — as most tasks are — I can easily get stuck in the nitty-gritty of the task and forget why I’m doing it. This makes it harder to actually perform the task due to being stuck and to not remembering the purpose.
One of my most effective workarounds, in addition to frequent breaks, is to summarize what I’m doing and what I’m learning. Whether it’s in a blog post, as with the Regional Hubs project, or in talking to others involved in the project, summarizing and explaining what I’m doing never fails to get me back out of the details. Of course, it’s also typically useful for the people with whom I am conversing and for my own later use.
It is typically easier for me to write than talk my way out of being stuck, as long as I write as if I have an audience. And Medium’s interface is _fabulous_ for this. It doesn’t get in the way of what I’m trying to say, and is minimal enough to not itself act as a source of distracting details.
It’s also helpful to have written logs of conversation, which can be harder to get with people I’m speaking to in person. I retain what I read much more easily than what I hear. For this reason, having a remote job can be useful, because most conversations are written and often easily logged. This is also why I tend to try to take notes during conversation, or ask people to send me written reminders. Similarly, I’m trying to add the habit of sending a written summary of what I understood from spoken conversations when I am concerned that I missed something.
I strongly suspect this need to summarize and explain to get out of the details is why I am good at explaining things. Lots and lots of practice, plus that being how I understand things better.
I also strongly suspect this is why I so badly want other people to work with or near: other people and the need to explain what I’m doing help me stay grounded in the overall purpose of what we are doing.
Like discussing what I’m doing with other people, brainstorming with others is fabulously useful, especially if they know something different about the topic than I do. While I might get stuck in the details when investigating something on my own, having someone else there means that they might not get stuck, or at least we can work together to pull ourselves out of rat holes.
Of course, brainstorming also brings in the wonderful thing called ‘other people’s perspectives’. No one can think of everything, no matter how hard they try. Involving other people means that together you have a good chance of coming up with things that work better than what either of you would come up with alone. People are very good at building on each other’s ideas, and often find it enjoyable, as well.
Analyzing data typically involves a great deal of detail work. There is usually a great deal of data, and it’s all too easy to lose track of the big picture of why the data was collected in the first place and what the goal actually is.
I _love_ that analyzing data in the UX world is often a group experience, whether through affinity mapping, brainstorming, various methods of prioritizing, and other things that aren’t currently coming to mind. It means that I don’t get stuck as often.
In grad school, analyzing data was often an exercise in figuring out ways to not get stuck in the data and remembering what I was there for. Analyzing data alone is not good for my mental health, as I’ve not yet found useful ways to keep myself on track for long periods of time. Statistics are hard for me, not because of the math, but because I have trouble remembering what to do when or why.
I also love that in UX there are often diagrams to remind you what research methods are most useful when. I’m sure that’ll come more easily to me with practice, mind you.
Speaking of research methods…
I think the biggest problem that I had when trying to learn UX on my own was the sheer amount of information. Having an internship and people to work with means that I had a way to focus.
Pre-internship, having had projects that I was working on didn’t help enough in terms of focus, because there were so many options.
I tried to write blog posts about what I was learning, as you can see early in this blog. Much of the time, writing the blog posts meant that I kept finding out how much I didn’t know yet, and how much trouble I was having figuring out what to learn first.
There is a _lot_ to UX. I have the skills to do it, I know for certain. It can be daunting navigating the sea of possibilities to identify what I should focus on.
I suspect the trouble I have with figuring out visual design is that it’s full of details. At least when I was trying to do things in Inkscape, the sheer quantity of things that you can do meant that I often had no idea where to start. Even once I understood that there were sample style patterns in the hubs design github, there were still a lot of possibilities.
I have no idea what’s important to pay attention to in visual design. I don’t know how to tell what’s a thing that needs to be the same always (nor do I know how to make sure that’s true), and what the range of ‘reasonable’ is. And the number of tools in professional drawing programs is absurd. If I don’t know what I need, how would I possibly know what tools to use, when?
I’m sure this is a tractable problem to solve. At the moment, though, it’s an especially daunting one. It is probably not aided by my lack of visual imagination or memory.
I think this is why I’m so happy that Balsamiq exists. The number of tools available is much more limited, and rather than trying to guess what something should look like, there are a number of items that already have a template for you to use. Indeed, working in Balsamiq is kind of like having a lot of small templates that one can use as building blocks, rather than making it up as you go.
I worry that Sketch will be too flexible. I won a license for it, and I should have access to macs in my household that I can play with it on. Indeed, after this internship, I am somewhat more comfortable with the idea of playing with it. I have some visual design knowledge just by frequently referring to the protoypes that Máirín Duffy made.
At the moment, I am trying to distill what I did in this internship into a portfolio format. I keep finding myself stuck in details, so I’m thinking that perhaps it makes more sense to create a presentation, first. I’ll need one regardless, and those force you to stay big picture.
The world is full of details!
Getting the in-person stuff to work was crazy complex. One thing for remote testing: it’s a lot easier to organize!
Thanks for being willing!
Overall, I loved it. Sure, there were annoying bits, but there are always annoying bits no matter what the job is.
There were lots of good things!
First, I had the best mentor. It helps that I already knew her, and that she offered to be my mentor when she suggested Outreachy to me. She’s been unfailingly helpful and kind, and very supportive.
At the very start, she offered me the choice of working on small scale existing UX tickets in Fedora, or doing a full-fledged project. The former would have been easier, in some ways, but not nearly as useful for progressing my career. The former would probably have been easier, if less useful, for her as well.
Second, the fedora-hubs team is a good group of people. Welcoming, helpful, and unfailingly polite. I may have only been there for a few months, but I will miss them.
Fedora people as a whole were similarly helpful; I had nothing to offer my interviewees and participants but my goodwill, and everyone I asked was happy to help out when they were able.
Third, the task was an interesting one. I think at this point I’d probably describe Fedora Hubs as a whole as an interface that consolidates and filters information about and from many different places so that an individual can find what’s important or interesting to them within Fedora. I probably need to throw something about making it easier for new Fedora users to get involved, although it’s hard to say if that’s Hubs as a whole or specific to the Regional Hubs that I was working on. Or both! Probably both.
I’d say the overarching goal for Regional Hubs was to encourage and support community within Fedora. Some of the problems that we were trying to solve were as simple — but not easy — as helping new users more easily get involved with the Fedora community, encouraging in-person social interaction to help people become and remain connected, and helping people find each other and events. Some of these we knew were problems ahead of time (like new users getting and staying involved), and some came up during the interviews (finding people and events).
As some of you likely saw while reading along, locations are hard. This made for a very interesting discussion to figure out how we wanted to handle that, and there are still aspects of it that I suspect need more attention. However, if we want people to be able to find people and events near them, locations are also really important.
I most enjoyed the discussions in which we were exploring the bounds of what we needed to know or do. This included brainstorming in general, the aforementioned complications around locations, and the conversation around the feasibility of the mockups in which we touched on how Hubs might suggest new regional hubs.
I didn’t really get a chance to learn more about visual design and how to translate from a mockup to a higher fidelity design. This was as much about available time as the difficulty of explaining it. I do have an example of the before and after versions of this for one of my mockups, and Mo has sent a screencap of creating mockups in inkscape. Hopefully these will be useful!
I didn’t finish creating the CSS for the high fidelity visual design that Mo had already created. I got stuck on translating from table to div, and needed to focus my attention elsewhere.
First, I really don’t like working remotely. I like people, and having people around is good for me. I also like being able to talk to people about what I’m working on and have them already have the context and knowledge to have productive conversations. This is still possible remotely, but there’s something missing from it in that context.
Second, and relatedly, I feel like remote usability tests and interviews are not as good. They do the job, for sure, but I feel like I missed out on stuff by not being _there_ with the participants. This is likely not helped by the connection to some of the locations participants were in being slow or intermittent.
Unfortunately, I was not able to do any local, in-person usability tests due to snow and other troubles.
This may actually be showing my bias from having done psychology graduate work: all our participants were in-person.
Third, transcription of interviews and usability tests are _annoying_ and really time and brain-power consuming. I knew this already, from my work with video and audio of people’s interactions with robots and with each other.
On the plus side, interviews and usability tests have less content to deal with, since I don’t need to identify and describe every gesture and every word spoken. Nor do I need to parse through 32 different recordings to try to find and appropriately label the right data to plug into statistical software to find patterns.
Fourth, Git and github and pagure have a higher learning curve than I’d like. This is not helped by the need for ssh keys in all sorts of places. I still wish it were possible to put my public key in _one_ place and have all the tools needed in Hubs work use it. A lack of communication between tools is a very common problem in all sorts of industries, and not just around ssh keys.
Fifth, having my internship include Xmas and New Years early on meant that I was rather less productive than I’d have liked around then. I needed a fair bit of guidance at a time when people weren’t around. Annoying, but not awful.
Good program, A+++!
Seriously, I’m glad Outreachy exists in both a theoretical ‘getting more diversity into open source’ sense, and in a practical ‘this was fabulously useful to me’ sense.
I do wish I could see this project through to fruition. But alas, that is not how Outreachy — and many other internships — works.
Now, to put this project into and otherwise update my portfolio!
(As a reminder to myself and others: the ‘story’ that people talk about when creating portfolios is a combination of providing context for the photos and graphics and screenshots you include, and showing what you have done vs what others did, what you were trying to accomplish, and your thinking about it.)
Previous, usability testing and analysis wrap-up.
Outreachy ended yesterday, so I’m working on cleaning things up for others to use.
I have completed my summaries of the initial interviews for event creation/planning and ambassadors as resources. I did not manage to translate the CSS from table to div, as things were behaving very oddly when I tried. However, I did pass along the CSS/HTML work I had done to Máirín Duffy.
Mo also has access to all the recordings of my interviews and usability sessions, the survey which ended up with 140 responses, and the MyBalsamiq instance for the Fedora Design team in which I put my mockups. I have put the anonymized transcripts and spreadsheet for the usability testing into the User Research and Analysis ticket shortly.
I hope to use the travel expenses for Outreachy to attend FLOCK in Cape Cod this summer.
Here, I’ll summarize how the usability testing went overall, what sorts of things I found, and some of the things that Mo and I discussed in our analysis. Due to time restrictions, we did not make it through everything I found for analysis purposes, but I will be available for questions and clarification as needed.
As I said in my last post, I ran remote usability sessions on my prototypes with 5 people. The major time sink for this was creating transcripts, although mostly not word-for-word. As I went, I highlighted the things that seemed relevant so that they would be easier to find when I was summarizing the findings. I ended up using a spreadsheet to organize the findings, first by prototype, and then by content to make reviewing it easier. For more on this, please see the attachments to the research and analysis ticket.
I then met with Mo to discuss my findings and to start preliminary analysis of them. We initially focused on the things that multiple people reported, with some side conversations around related problems when necessary. In many cases, the decision on what to do was pretty simple (often because it was effectively a paper prototype and thus not as interactive as it could be). However, some of the problems my participants ran into were not simple fixes and required a lot of discussion.
One of these related to the problem of deciding who to contact first in a filtered list of people. As it was, the prototype did not show anything about your relationship with those people. Even when you clicked on someone, it was not obvious that the hubs and friends listed started with the ones you had in common:<figure><figcaption>Do I know Jen Smith better than John Holsberg? Who knows?</figcaption></figure>
When I asked people to find someone to contact, whether because they were visiting an area and wanted to find local Fedorans to meet up with, or because they needed more information about an upcoming event, they had trouble deciding who to talk to. In this prototype, only one person was clickable (Jorge), but my participants had no idea if that was who they actually wanted to talk to.
Some suggestions people made included having something signalling if they have an existing relationship with the people in the list. In talking with Mo, however, that can get very complicated, very quickly.
We can decide that people who are following each other are friends. However, what if you think someone is fabulous, but don’t need to know about their activity within Fedora, or don’t have the time to add that to what you are paying attention to. At the moment, following someone means that you see what they are doing in your stream, so perhaps mutual following is insufficient information.
Maybe you’re on a team with someone so you’re theoretically interacting with them regularly. This is more likely to be useful information about how you are connected to that person, except possibly if you’re on a huge, geographically disperse team.
Maybe you talk to someone on IRC regularly. That probably means you know them, right? Maybe work with them? Sure, but that may not mean you want to meet up with them.
It absolutely would be helpful to Fedora members to know their relationship, if any, with people they are considering contacting. Precisely how to do this remains to be seen.
Supposing we use team affiliation, following, and conversation frequency. How do we signal this kind of information at a glance without making the information too overwhelming and difficult to process? Icons can be good _if_ they are some of the very few that are quickly understood. Text can get unwieldy. This will have to go unanswered for now, but requires more thought.
It’s helpful to know if someone is online right now. It’s probably not as helpful to know precisely when someone was last online when you’re looking at a long list of people.
Lots of applications show that someone is online using a simple blue (or green) dot near their picture or name. This may be the best way for us to do the same, and will also free up some space in the search results for affinity signalling. At the same time, we probably want to make it clear who hasn’t logged in recently. Since this will be pulled from a list of people with FAS account, there may be people in the results who have never logged into Hubs, and we need to show that somehow. We can easily show more precise information about when someone was last online in the dropdown, and from the perspective of too much information, that definitely makes the most sense.
Another frequent problem was that my participants didn’t especially want to be contacting random Fedora people out of the blue. Most said that if they knew someone liked meeting strangers, or were interested in helping others out in some way, this would reduce that barrier to contact.
So, instead of having the ability to select only ambassadors — who may or may not actually want to be contacted right now — make it possible to select people who are interested in meeting new people or answering questions or otherwise welcome random contact. Of course, what this needs to be called is an entirely different question. It might be as easy as an ‘Open/Closed’ sign like some businesses have, but that may be too easily misinterpreted or daunting for other reasons. More research is definitely needed here!
In looking at the major search and filter areas of the list of people and events, it can be difficult to determine what is valid.<figure><figcaption>People search and filter</figcaption></figure><figure><figcaption>Events search and filter</figcaption></figure>
When asked to search for people in Berlin, many tried to use the ‘all people’ search to look for Berlin. The actual intent is that they can change ‘you’ to a specific location other than where the system knows they are. The ‘all people’ search box is for searching by people’s names, nicknames, IRC nicks, and email addresses.
Similarly, when asked to find events in Las Angeles, the ‘all events’ search box was very tempting. Again, the ‘you’ box is there to allow you to change the location away from your own location.
So how does one make this clearer?
We had a few thoughts on how to best handle this one. Mo pointed out that a common pattern is that searches are along the top, and filters are along the left side. In that case, why not let people search by location in the search box?
We also considered that this might be a lot clearer if it were possible to actually type into those fields: once you start typing, type-ahead would quickly make clear the sorts of things the search box was expecting.
Another, similar, problem was that the contents of ‘10’ miles and ‘you’ (different for events and people) were somewhat unclear on what they were able to take as inputs. My mockup had dropdowns for these, since we wanted to not only allow people to start typing in those boxes, but also to make clear the kinds of things that were possible in there. However, in no case did people realize that they could simply start typing, rather than only selecting from the dropdown options.<figure><figcaption>events near [place] or in [place]</figcaption></figure>
You can pick near ‘you’, near a specific location, or within an area. The latter case wouldn’t need the ’10 miles of’ piece, though.<figure><figcaption>People near [somewhere], including everyone</figcaption></figure>
I wanted to have the option of everywhere because otherwise actually specifying something in ‘all people’ makes no sense. At the same time, perhaps you _do_ care where. This one confused me and I failed to explain my reasoning to Mo.<figure><figcaption>Events or people within [miles of somewhere] or [a place]</figcaption></figure>
How far from the place you specified? Or, maybe you just want to say within a place?
This is likely an even more complicated problem than I suspected, but hopefully it was largely due to the fidelity of my prototype.
But what do we do?
We did not come to an agreement on the best way to handle either of these cases, in part because we suspected that this was a problem with the fidelity of the prototype.
Some of the problems I ran into were fairly easy to solve. Others need additional investigation and consideration. There are findings from the testing that have not been reviewed, and I hope that Mo will be able to find the time to go through them and contact me as needed.
I have no question that the usability testing was valuable, and hope that the existing team will be able to continue the work that I started. I wish that I were able to continue to work on this project, and shall see if there is any time available while I apply for jobs and hopefully start a full-time job soon.
I found this to be a fabulously useful experience, and want to thank Máirín Duffy and the Fedora Hubs team for being helpful, approachable, and friendly. And of course, to thank Mo again for having mentioned the possibility of Outreachy to me.
Previous, usability testing.
I promise. Got a nasty cold, so wasn’t making as much progress, but still here.
Brief catchup, since I’m in the middle of trying to get a bunch of wrap-up stuff done.
As I said a few posts ago before I dove into CSS, I needed to do some usability tests with my mockups. I was unable to get any of my original set of interviewees to do this, and due to sickness on my own and Mo’s part and weather interfering, was unable to do any in-person usability testing.
I did get 5 people using my prototype, with a good spread among the tasks I had available.
As mentioned previously, my tasks included what we identified as the most immediately relevant aspects of the project, and the mockups I made for those.
The first page of each of my prototypes and their associated tasks are shown below, with a link to the prototypes themselves in the short description below each mockup.
After two usability sessions, it became pretty clear that any one individual should do one, not both, of the two tasks in people, events, and join or create. Those were much too similar and were causing confusion to be done in a single session.
Similarly, in the initial prototypes, the top-most bar was too realistic-looking, having been from a screenshot of a more visually designed page. As such, to better determine the source of confusion with multiple search bars on the same page, I replaced the search bar with one from Balsamiq.
Some small issues with Balsamiq came up. First, MyBalsamiq did not show what items were linked on the prototypes my users saw. If I looked at them myself, I saw the appropriate markings.
Second, I was unable to have an entire line be clickable, which added some unnecessary confusion. As far as I could tell, this is simply not supported.
I suspect strongly that this experience would have been greatly improved by a note-taker. It’s taking a lot of time to go through the sessions after the fact, identify and gather the relevant information, and come up with a good way to summarize what I found. I do also appreciate the experience and viewpoints of others when collecting and interpreting information.
Once I’m finished collecting together the information from the usability sessions, I will be discussing what I found with Mo, likely doing more affinity analysis, and creating some sort of summary of the results and of the entire experience. I’m not yet clear on what that all will involve, and sort of suspect it’s not likely to be complete by the 6th. Frustrating, but that does happen.
My internship will be coming to a close on March 6th. I would like to leave things in as clear a state as I can, both to allow others to continue my work, and to make it easier for me to pick it back up when I’m no longer able to work full-time on it.
In addition to the collating, analysis, and summary of the usability testing, I will be finishing up a number of other things. This includes summarizing what events/event planning needs to include, what ambassadors tend to be doing as resources), and making sure all the raw data (transcripts and recordings) are available to Mo.
I’m still pushing people to take the survey, and it looks like some work that Mo and I recently did improved our numbers significantly (from 28 responces to 121!). I’m not sure that I’ll have time, but I’m hoping to do some analysis of that, as well.
I’ve not really had much chance to really understand how one goes from prototype to visual design, which is unfortunate. That is one area that I definitely need more experience with! I may see about working more on that post-Outreachy.