shift+control

76design's blog

Archive for the 'Staff' Category

Lost Characatures

Posted by Jeff Young on January 27th, 2010 Comments 1 Comment

Sometimes, to keep myself sane during long work days, I tend to doodle and draw — it’s just what I do and have done since a wee lad.
I was going through some old notebooks and found a few characatures of some co-workers I sketched.
More to come …

Judging a Holiday CD by its Cover

Posted by ryan on December 18th, 2009 Comments 2 Comments

For the second year in a row some coworkers and I have decided to be thrifty with our holiday gift exchange by designing and creating personalized CDs filled with music that we think the other person will like.

It started off with a hat, tiny pieces of paper, and the Christmas Party. It was then that we drew the name of our sucker, err, recipient. The hardest part, in my opinion, is trying to figure out what the giftee will like on their CD. There are several people in the office who are extremely transparent with their choice of music, but then there are others who never leave their iPod alone long enough to take a peek.

We’re lucky enough to be a tight knit crew, so the CDs always seem to have a personal touch that ends up being a big success. Our collection of disc cover designs this year included favourite fonts, colours, even condiments (images, and believe it or not, actual fresh pepper).

76design/Thornley Fallis Holiday CD Exchange

For the past few hours it’s been pretty quiet in the office except for the headphones of everyone listening to their CDs. Well, that and the munching of Brett‘s mom’s delicious cookies.

76design helps to make wishes come true

Posted by Brett Tackaberry on November 27th, 2009 Comments 1 Comment

091025-m4k09-8x11-72dpi

Campaign design by our very own Ben Watts.

A strange yet mysterious veil falls gently over the 76design office in Ottawa every year in the month of November. It is a veil but more accurately it is a mustache – many mustaches. Yes, Mustaches!

We grow mustaches not only for the style and sophistication but for a truly greater purpose – the enhanced visual appeal is just the icing on the cake. We are growing for Mustaches for Kids (M4K) to raise money for Make a Wish Eastern Ontario. Our mustaches make wishes come true – read more on how the helped some local kids in need of a wish.

M4K has grown and matured within the walls of 76design. Legend has it that M4K was in fact brought to Ottawa and nurtured to greatness by the shameless dedication of 76designers. Over the years we’ve seen many a stache. Including our fearless leader, Joseph Thornley, who is growing with us yet again – and matching any donation to him. But all fun aside, we’re proud to have contributed to M4K and Make a Wish.

M4K is now in its 5th year in Ottawa and we’ve raised a combined amount of $50,000. Last year we raised $20,000 and this year, with over 100 growers, we are aiming at $25,000.

Help us make our mustaches worth more than they look. You don’t need a mustache to help.

Skunkworks Project 1: Twitter API Applications

Posted by 76design on September 15th, 2009 Comments 1 Comment

76design skunkworks

Our skunkworks Twitter applications are complete!  Over the past eight Friday afternoons our team has been working feverishly on experimental design & development projects using the Twitter API.  Why?  To learn and explore!  The web is a constantly changing landscape, and to be on top of our game it is necessary to research and explore. Not to mention, we are a creative and ingenious bunch who crave experimental projects to work on.

Skunk works or skunkworks is widely used in business, engineering, and technical fields to describe a group within an organization given a high degree of autonomy and unhampered by bureaucracy, tasked with working on advanced or secret projects.
- Skunkworks definition on Wikipedia

76design’s Skunkworks Recipe:

76design donates time each week (usually Friday afternoon), and the team donates an open mind, fresh creative ideas, energy, and finally a working demo. The projects are intended to encourage exploration, therefore the skunkworks recipe itself is iterative and malleable. Through skunkworks we will be testing new approaches to web dev with the hope of integrating the findings into our daily work. That said, the following was a guideline for our first project, but we expect this recipe to change over time.

Week 0: Preparation of project Theme & Constraints
Constraint breeds design. Therefore we present the team with a challenge while leaving plenty of room for creativity. The challenge also centers the  experimentation around a particular area of interest. For this project the Theme was Twitter, and the main constraint was the web application had to use the Twitter API.

Week 1: Brainstorming & Team Selection
The team gathered for a single large brainstorming session where everyone threw ideas at the whiteboard.  This generated a large quantity of ideas, and encouraged the team to be creative, critical, constructive, and considerate.  Following the brainstorm we broke into teams of 2 and selected the concepts we wanted to experiment with for the next few weeks.

Week 2: Research, Concept Refinement & Work plan
Now that the team has had a full week with their concept, they refine it into a concrete plan. Week 2 is all about editing  the ideas & features down into a reasonable plan which can actually be accomplished within the short time line. This exercise involves documenting each task’s level of effort and priority. At the end of the project the teams are asked to compare the outcome to their initial plan.

Week 3, 4, & 5: Design, Code & Test
These weeks are all dedicated to designing and coding the project. The teams check in briefly every week to discuss their progress and help each other with challenges. Inevitably, unforeseen issues or fresh ideas will cause the plans to change, therefore the teams are encouraged to work iteratively using agile methodologies. Teams are graded on their ability to define project scope and manage scope change.

Week 6: Present working demo to the entire team
The projects are now ready for a functional demonstration, and everyone gathers in the boardroom for a short 5 minute presentation and Q&A period for each project.

Week 7: Followup
The teams will write a reflective blog post about their project which includes an overview, the challenges faced, the outcome, and the potential next steps for their project.  Teams will also share the insights they gained from the skunkworks experience.  Furthermore, teams will post relevant information to our company wiki for future use. The Teams are free to continue the projects if they wish, or publish them online as they are.

So stay tuned. The first round of skunkworks twitter applications are complete and we will be posting the team’s project followups over the next week or so.

The Candy Bowl Theory or Tragedy of the Commons or Glucose Rage

Posted by mindorff on September 11th, 2009 Comments 13 Comments

A couple weeks ago I was randomly inspired to do something kind for my fellow colleagues. Not having any actual hypothesis in mind, I referred to it as a “social experiment”, hoping it would yield some sort of result or impact – and that it did.

I filled a small white bowl from our kitchen with jujubes and placed it at the end of my desk. I felt good about it. As people started coming into my office, they would notice the candy, be pleasantly surprised and indulge.  Making them happy, made me even happier and gave me incentive to continue to fill up my bowl (at this point, the bowl was being emptied after about 5 – 6 hours).
shutterstock_26625250

People were showing up in my office for no apparent reason, making up all kinds of excuses to be there, all the while, feeding like vultures from the bowl.  In true Pavlovian fashion, the mere sound of a bag opening or treats filling up the bowl, would create a response from the team (at this point the bowl was being emptied after about 2 – 3 hours).

The happier people were, the more excited I was to go out of my way to get more rubbery-textured confectioneries into that bowl the next day. Every day I would fill the bowl with something different – jujubes, pistachios, Clodhoppers, chocolate covered almonds, swedish berries, M&M’s (by the time the M&M’s hit the bowl, it took 20 minutes to empty).

Then, somewhere between the chocolate covered almonds and swedish berries, something started to happen. People started verbalizing preferences and complaining. Several “facts” about free candy and nuts began to emerge; apparently pistachios are “too much work” and chocolate covered almonds are “boring”. The more complaints I received, the less incentive I felt to fill up that stupid little white bowl.

As I stopped filling it up, the expectation for the candy became apparent. People were actually getting upset that there wasn’t anything in the bowl.

“Oh, the bowl is empty again?”
“Where the f&*% is the candy??”
“I’m not very happy about this empty candy bowl situation.”

In hopes of cutting down on the comments, I ended up taking the bowl out of my office altogether.

So, my theory is this – the candy bowl is just like life:

Unexpected pleasantries = satisfaction
Expected pleasantries = dissatisfaction

So the next time life hands you a gummie bear, just eat the friggin’ thing and be happy!

76design’s Aural Design Challenge

Posted by 76design on February 19th, 2009 Comments 3 Comments

Have you ever wondered what 76design would do if there were no rules? no boundaries? Nothing in the way? What would we come up with? Would it be capable of flying? Would the result rival silly putty on the coolness scale? or perhaps pogs?

Well we wondered. We decided to take the first step towards answering that question with the first ever 76design Aural Design Poster showdown.

here is a snippet of the original project brief

“Take a Song, Listen to it, Design!…” “…Pitcher of booze for non-delivery is standard penalty.”

But where to begin? What song would provide suitable poster fodder? Well, according to one Steve Lounsbury, Brain of J by Pearl Jam would do the trick. And by golly – I dare say he was right. Well done Steve old chum.

Sure, its a “design” project…but this project was not meant for designers alone. No, this project was for all. Designers, developers, account managers, and project managers alike. With only a few abstaining from participation (and 1 poor sap that failed to meet the 2 week deadline) it was a full team endeavour. Fun? Probably. The results? You be the judge.

[nggallery id=2]

And 2 of our developers took the opportunity to create their submissions in processing – 1 of whom also decided to give us a glimpse at “the making of”. Enjoy.