Josh Evnin

"Pretty" Software Applications

One of the most difficult expectations for me to overcome with respect to my coworkers is the idea that I’m here to simply make the software look pretty. It’s difficult for so many to understand. I do understand principles of typography, layout, color, and design in general…and yes, I do have the ability to decorate an app to make it seem “prettier” to the untrained eye.

The thing is, I’m not necessarily here to apply typographical, layout, color, etc. changes to a system. Before that can happen, the tool has to have a logical flow. Input fields that are displayed have to make sense. Everything that has been placed on the screen up to this point must be there for a reason. I take it as my first job to understand exactly why you’ve placed that input box above that drop-down menu, for example. Sometimes this part of my job is easy. Other times it is not.

My point is that I will not (and cannot) make your system look nice unless the basic interaction part is already taken care of. In fact, having a cordial interaction with the user is core to the system looking nice. Sorry to burst your bubble, but the colors themselves don’t matter if the user can’t figure out what he’s supposed to do.

The UI needs tending, and it can’t just be fixed at one point in the process…beginning, middle, or end. It needs attention throughout the design and implementation phases. Each development iteration can also be an interface design iteration. Slowly but surely I’m learning that it’s not a good idea to just try to save an interface in one fell swoop. Everybody involved in the software development process should take this lesson to heart as well.

For now, I’ll keep busy on projects chugging away at finding interactions that make little sense from a user’s perspective and helping to ameliorate these issues. It’s my hope for each project that one day I’ll get to the point where I can help the user have an experience that is not only easy, but fulfilling and emotionally pleasing as well.

July 10, 2007
Taxi-cab confessional

I almost missed my flight this evening. Nearly every Sunday for the past few months I’ve taken a flight to Raleigh, NC. This flight is preceded by a trip in a taxi from my house to the airport.

Except tonight it didn’t go as planned.

As routine turned to complacency, I wasn’t alarmed when the cab wasn’t there 5 minutes early…nor was I alarmed that it still hadn’t shown up 10 minutes late. Then 20 minutes late. Finally at 23 minutes late I picked up the phone.

Me: Um…I ordered a cab for 7:15 and I just wanted to check the status of my ride.

Operator: Oh, he should have been there a while ago. Let me contact the driver.

…Waiting…

Operator: Yeah, he’s right down the street. You should go outside…he should be there any minute.

Me: Great! I’ll be out there.

…10 more minutes pass…

Me: *Muttering* I better call again… (This time was same as before, just with a new operator.)

Operator: Yep, my system shows that the driver is right up the street. He should be there any minute.

Me: Great! I’ll be out here. (I don’t know why I’m endlessly positive with people in service industries. I have patience well beyond my needs…)

Eventually Karen noticed that I was still outside and offered to drive me to the airport. I took her up on it…and it’s a good thing I did. The cab never showed.

But why did all this miscommunication occur in the first place? Perhaps it has something to do with the communications systems that the cabs are using. This technology is a likely culprit. If you look around at the driver’s seat in any cab in the US, you’ll find that it’s a mess of wires, screens, and sounds…and this is before you take into account the fact that the driver has to drive. Of course the driver says he’s right up the street…that’s how he gets the operator to leave him alone, so he can get to his destination/talk on his mobile phone (by the way, who do these cab drivers talk to on their phones all day? My guess is that they talk to each other. It couldn’t be their family members…could it?).

All of this is turning into one big rant. The point is, a cab driver’s seat holds endless opportunities for innovation. It is ripe and ready to be tapped. So, somebody, please (pay me to) do some ethnographic research and redesign this workplace. I’m sure us regular taxi riders would benefit immensely.

July 8, 2007
On the Misleading Lexicon of Agile Development

Whatever happened to clear, consistent language? Why do we use words that have inconsistent meaning in contexts where they’ll be unfamiliar? Why, oh why?

Day in and day out I work with clients in an Agile development setting. I use words that have been trained into me, that I’ve been taught over and over again. But when I sit back and think about these words, they just don’t make sense. Let’s look at two of my favorite examples. First, some standard definitions:

Story – the plot or succession of incidents of a novel, poem, drama, etc.

Narrative – a story or account of events, experiences, or the like, whether true or fictitious.

Sounds pretty familiar, no?

Well in Agile these words take on a whole new meaning. A story is the encapsulation of some sort of requirement, based on a given user’s needs or wants. It generally takes the form of:

As a [user]
I’d like to [some action]
So that [resolution of need]

But wait, is that really a story?

A narrative is the document that describes this story in detail. Chock full of high level objectives, UI prototypes, test cases, and other minutae. If you asked a person on the street what a “narrative” is, there’s no way they would describe it this way.

So why do we insist on using these terms, with their off-the-mark definitions? I don’t know. They probably seemed all cutesy and different at the start, something that sounds fun and light when compared to heavier terms like REQUIREMENTS DEFINITION DOCUMENT. When it comes down to it, “Story” just sounds less beefy than “Requirement.”

Damn Agile, You Just Stole My Words

Aside from the simple misappropriation of terminology, I have a bigger issue with the use of these terms. In the Design world, “Story” and “Narrative” have real, relevant meanings that align with the standard definitions of these terms.

Both of these terms are used to describe, in detail, a user’s experience, either today or in some envisioned happy future. The Narrative is generally a more detailed version of the story, which includes a narrated scenario in the context of the tool’s use.

I might be splitting hairs, because I think the Agile use of these terms tries to get at the same thing…but they just don’t. An Agile Narrative generally doesn’t tell a real story in detail, it describes a requirement in detail. Likewise, an Agile Story describes a requirement, not a user’s journey.

In Conclusion

We have to be careful with the words we use. In the end, we’re all trying to build software that solve real human problems. Surrounding these problems is real human drama that can, if described well and designed for, be turned into happier situations. I believe the use of words with alternate definitions muddies the water, but certainly doesn’t get in the way on a day-to-day basis.

Whatever words we use, we have to be sure that our solutions fit into the contexts of our users. We must ensure that our software fits into our users’ everyday stories.

June 17, 2007
Agile Design, a response to my friend’s quandary
This evening Kynthia‘s thoughts got me thinking. Among other things, she said:

“[W]e design heads get in this place where, just because we wouldnâ€™t be caught dead releasing something into the wild, we think there is nothing to learn from it.”

My brain took her thoughts on a tangent and went this way:

So since I started my job at ThoughtWorks, my role has pretty much been defined by this exact issue. See, we use agile development methods, which often means that the stuff I’m designing might be built tomorrow, or at the latest in the next few weeks, which leads to some pretty interesting questions, such as:

If I had to hand over my design in the next [time limit], what would be the most important part(s) to get across? So what should I spend my time on?

How can my design(s) make the greatest impact in the short run?

How can my design(s) be flexible enough that they’ll support more advanced interactions and further redesign (without simply adding features) in the long run?

How much does my design cost, in terms of real dollars and development time? Is there anything I can do to make it less expensive without hurting the users (too much)?

Will the brilliant, awesome, amazing design I’ve just created embrace change if it turns out users really don’t like something about it? Or will it fail miserably…which might be a good thing if it motivates the product owners to spend more money to fix it.

Indeed, I believe us “design heads” need to wrap our brains around the idea that the “ideal design solution” can be super-difficult, and sometimes impossible to implement, if for no other reason than the person with the money doesn’t feel like splurging for a great user experience. Given this situation, it’s important that we release our ideas into the world early and often, even if they aren’t perfect. Putting our ideas out into the world lets them get stomped on, beat up, and improved to the point where while they may not be ideal, they’ll at least be better.

Iteration, baby, that’s the name of the game. It turns out when we designers draw and write and specify and prototype and mock-up our designs in our oh-so-ritualistic way, we end up with an unintended by-product: intimidation. See, even if our brilliant, perfected ideas aren’t intimidating to the teams of programmers that have to build them, they’ll often be super-intimidating to those who have to pay for them. See, the more realistic/difficult/etc. our designs look on paper or other prototyped form, the higher the perceived cost. Let’s look at a formula to really help this sink in:

C(p) = -I(L)

Now, I haven’t taken a math class in years, so that formula probably means nothing at all. Ignore it for now. What I mean to say is that the higher the perceived cost, the lower the likelihood of implementation. This all seems pretty simple, and it is, but sometimes it’s hard for us designers to break away from the idea that we need to perfect everything about our concepts. In fact, when we do this, it can be to our disadvantage.

Oh, and don’t think we’re not intimidating ourselves either! When was the last time you decided not to take on some project just because you knew it would take too long to really “do it right?” Yeah, it happens to me all the time too. We designers know how to intimidate ourselves as well.

So rather than perfecting, why don’t we try biting off just a little bit at a time? Design in terms of small, implementable, simple solutions to the problem at hand. Then expand on the concepts, and build them all the while…just a little at a time. Sure, some of that implementation will have to be redone as you go, but if it truly improves the end design, do it.

Of course, when you’re designing and building an enterprise level application, there’s a lot more structure and process that has to be involved in design, but I think for Kynthia’s case, an Agile development process is somewhat ideal. It gives you the opportunity to take a stab at a problem, implement something simple, learn from what you built/pondered/etc., and iterate.

Anyway, sorry for taking your thoughts on a tangent, Kynthia, but thank you for getting my brain cranking this evening. 🙂
June 5, 2007
Agile anti-pattern: Developer-focused retrospectives
On most software projects, there is a far higher percentage of developers on a team than any other role. In general, this works to the team’s advantage. The developers, after all, are the ones who make what everybody else works for come alive.

Best CBD Gummies for Sleep in 2023: Top Recommendations and Reviews

Quality sleep is crucial for our overall health and well-being. It’s not just about getting enough hours of shut-eye; it’s also about the quality of sleep we get. When we don’t get adequate rest, it can lead to various sleep disorders that can impact our daily lives click timesofisrael.com.

Insomnia is one common sleep disorder characterized by difficulty falling asleep or staying asleep. It can leave us feeling tired, irritable, and unable to concentrate during the day. Another disorder is sleep apnea, where breathing repeatedly stops and starts during sleep. This can cause loud snoring, gasping for breath, and daytime fatigue.

Restless leg syndrome is another condition that causes an irresistible urge to move the legs while resting or sleeping. This constant movement can disrupt our ability to fall asleep or stay asleep throughout the night.

Understanding the science behind sleep can help us find effective solutions for better rest. Numerous studies have been conducted to analyze the effects of sleep on our health and well-being. For example, research has shown that lack of quality sleep increases the risk of developing chronic conditions such as obesity, diabetes, cardiovascular disease, and even certain types of cancer.

Sleep also plays a crucial role in mental health. Insufficient sleep has been linked to an increased risk of depression and anxiety disorders. Studies have found a strong association between epilepsy and disrupted sleep patterns.

The American Soul – July 4,1776 – January 22,1973

We’ve witnessed too may human atrocities in our great land since our birthday back in 1776. Unfortunately, this is the human condition and unfortunately we’re not alone. Most are caused by deranged individuals acting independently to the disgust of a decent people everywhere. This is no longer the case. What once was considered an atrocity, is now law.

Legal Consequences: Termination or Legal Action

Attempting to cheat a drug test can lead to severe legal repercussions. Many companies have strict policies in place regarding drug use, and if an employee is caught trying to manipulate the results, they may face termination or other disciplinary actions. In some cases, cheating a drug test can even result in legal action being taken against the individual.

It’s crucial to understand that tampering with a drug test is considered fraudulent behavior and is often viewed as a breach of contract between the employee and their employer. Employers have the right to maintain safe working environments for all employees, which includes enforcing drug-free policies. By attempting to cheat a drug test, individuals are not only jeopardizing their own positions but also potentially putting others at risk.

Ethical Implications: Undermining Trust and Compromising Safety

Beyond the legal consequences, cheating on a drug test raises ethical concerns. Organizations rely on trust among employees to foster collaboration and maintain productivity. When someone cheats on a drug test, it undermines this trust by demonstrating dishonesty and deceitful behavior.

Moreover, compromising safety measures is another significant ethical concern associated with cheating on drug tests. Certain professions require individuals to be sober while performing their duties for the well-being of both themselves and others. For example, pilots operating aircraft or doctors performing surgeries must be alert and focused without any impairment from drugs or alcohol.

By attempting to cheat on a drug test in these professions or others where sobriety is crucial, individuals are not only endangering their own lives but also risking the lives of others. It is a matter of responsibility and accountability to ensure that one is fit for the task at hand and not under the influence of substances that could impair judgment or performance.

Deterrence: Understanding the Risks Involved

Understanding the risks and consequences associated with cheating on a drug test can serve as a deterrent for individuals considering such actions. By comprehending the potential legal implications, termination, and ethical concerns involved, individuals may think twice before attempting to manipulate their test results.

Instead of resorting to cheating, it is advisable to address any underlying issues related to drug use by seeking help from professionals or support groups. Many organizations offer resources such as employee assistance programs (EAPs) that provide confidential support for employees dealing with substance abuse problems.

How to Beat Drug Testing Legitimately: Safe and Valid Strategies

To pass a drug test legitimately, there are several safe and valid strategies you can employ. Keep in mind that abstaining from substance use is the most reliable way to ensure success. However, there are additional steps you can take to increase your chances of passing a drug test click https://www.ndtv.com/.

Abstaining from Substance Use: The Most Reliable Strategy

The best and safest way to pass a drug test is by abstaining from using any substances altogether. This means refraining from drugs, alcohol, and even certain medications that may trigger positive results on a drug test. By avoiding these substances entirely, you eliminate the risk of failing the test.

Staying Hydrated and Maintaining a Healthy Lifestyle

Staying hydrated is an important aspect of passing a drug test. Drinking plenty of water helps flush out toxins from your system, including any traces of drugs that may be present. Maintaining a healthy lifestyle can contribute to faster elimination of substances from your body.

Pros:

Drinking water is easily accessible and affordable.

Hydration supports overall health and well-being.

A healthy lifestyle promotes better physical condition.

Cons:

Overhydration can lead to water intoxication or hyponatremia.

Urine dilution due to excessive hydration may raise suspicions during testing.

Allowing Sufficient Time for Elimination

Depending on the type of drug used, it takes varying amounts of time for substances to leave your system completely. It’s crucial to allow sufficient time for elimination before taking a drug test. Different drugs have different detection windows, ranging from a few days up to several weeks.

Pros:

Giving yourself enough time ensures that any traces of drugs will be eliminated naturally.

Waiting allows you to avoid resorting to potentially risky methods such as detox products or adulterants.

Cons:

Timeframes for drug elimination vary depending on factors such as the type of drug, frequency of use, and individual metabolism.

Waiting too long may not be feasible if you have an upcoming test.

Seeking Guidance from Healthcare Professionals or Employee Assistance Programs

If you’re uncertain about how to pass a drug test legitimately, it’s advisable to seek guidance from healthcare professionals or employee assistance programs. These experts can provide valuable advice and support based on your specific situation. They can help you understand the detection windows for different substances and offer recommendations tailored to your needs.

Pros:

Healthcare professionals can provide accurate information about drug detection times.

Employee assistance programs are designed to assist individuals facing workplace-related issues, including drug testing.

Cons:

Consulting with professionals may incur additional costs.

Not all workplaces have employee assistance programs available.

By following these safe and valid strategies, you can increase your chances of passing a drug test legitimately. Remember that abstaining from substance use is the most reliable approach, but staying hydrated, allowing sufficient time for elimination, and seeking guidance when needed are all important steps in ensuring success.

Since that day in 1973, over – Now stop and think real hard about this – over 40 million, that’s 40, 000,000 babies have been butchered. That day the name of the Court should have been changed to The Barbarian Court of The United States.

On January 22, 1973 America lost its soul. Seven lawyers that day decided that fucking without responsibility was more important than life itself. Seven lawyers that day, not Gods, not preachers, not doctors, not anyone elected by the people of America, just nine lawyers. Seven lawyers whose greatest challenged in the real world was to pass the bar exam, which just about anyone can do. Seven lawyers decided to cut the backbone out of a civilized society and crack the foundation upon which was built the greatest country in human history.

In a retrospective, however, it is important that no one group of team members is favored over others. This is harder than it may seem, especially when the developers make up more than half of the team.

The way most retrospectives I’ve been a part of have worked is some variation of the following:

Individuals think of a few things that have gone well, and a few things that have gone less well over the past set time period

These thoughts are put on post-it notes, then placed on a wall

Individuals read all the thoughts and vote for the ones that they agree with (each person has a limited set of votes)

The retrospective facilitator tallies the votes and discusses the highest vote-getters with the team, and discusses ways to fix problems and continue successes

Now, as you can tell this is a quite democratic process. The problem is, when the ratio of developers to business analysts is 4:1, you start to see the topics discussed err towards the technical. If you’re lucky, you have a facilitator who realizes this and steers the conversation in a direction that helps the entire team, not just the developers.

Moral of the story: Make sure you’re paying attention to the distribution of people on your teams, and the topics that are covered in your retrospectives. Sure, the idea is to make software, but the process is only going to improve if the entire team is learning from their steps and missteps.
May 29, 2007
Meet Josh: Allergy Edition
Josh is officially allergic to the following allergens:

Grasses:

Rye

Redtop

Timothy

Bahia

Johnson

Trees:

Ash

Birch

Maple

Oak

Walnut

Cottonwood (Popular in Chicago!)

Cats (Not all, but some)

Weeds:

L. Quarter

Ragweed

Thank you, Dr. Rogers, my new allergist for shining a light on the status of my allergies. Let’s hope the new prescription gives the rough Chicago air a run for its money…
May 25, 2007
Linux for the Creative Type?

Call me a Design+OSS fanboy, but UbuntuStudio looks awesome. Finally an Open Source operating system aimed at us designerly folks. I know, I know, all that software has been around for a while, but it will be nice for it to be all wrapped up in a tightly wound package. I’ll let you know if I love it or hate it after I give it a try…

May 14, 2007
FYI: Free Stuff for Mother’s Day

Skype

CoPilot

May 13, 2007
It’s been a while
While perusing a friend’s new site this evening, I realized that it has been a long long time since I last blogged. That’s just no good. A lot has been going on…so let’s play catch-up.

Karen’s sister had a baby! That put me in New York City for a few weekends in mid April. Welcome to the world, Matthew.

I missed out as a bunch of my friends headed to San Jose for CHI2007. From the pictures, it looks like they had a great time. I’m sad that I missed out.

I’m on a project for work in North Carolina, and I even get to work with some real designers. Generally, I’m the sole designer on a project, but on this one I’m just one of four. It’s great because we get to bounce ideas off of each other. Still, the design bit is tough for me because I have less context in the design space than they do. But I do get to play with some new technology…the jury is still out on whether I’m a fan. It does look cool though. The problem is that I’m really interested in Open Source stuff now that I’m a real life contributor to a project…so we’ll see how far this goes.

I’ve started to use Twitter. You can follow me through my days & nights.

Last weekend I was in Denver for ThoughtWorks Away Day. I did a talk about Contextual Design…it was pretty well received. But more on that later.

In the last 38 days I’ve been at home for roughly 48 hours. (And some of those hours are distributed among separate days…) One could say I’m homesick. Oh what I’d give to sleep in my own bed.

I’m sure there’s more.

Right now I’m getting psyched for some visitors, it seems that’s what May is all about. Sarthak, Sejal, Puneet, Scott, and sister Tami are all coming out to Chicago, and in that order. I can’t wait to see all of them.

All right, I think we’re caught up for the moment. More later.
May 9, 2007
Even Apple is not Immune

to a poor design. I stumbled across this newish area of the Apple site this morning. I won’t go into details, just because I’m lazy, but from this designer’s perspective this page is U-G-L-Y. So many gradients and colors and flashing boxes. Not to mention the fact that it has slowed my computer to a grinding halt. Painful. Wake up, Apple…don’t lose your fabulous eye for detail.

April 7, 2007