Scott is a top-performing creative professional with extensive experience in human-centric design, strategy development, target marketing, brand management, buyer behavior analysis, digital design and process development. He is recognized for passionate interaction with high-end clients and is highly talented in managing the entire process, from initial concept to executable insights and ongoing account maintenance. He has a consistent track record of generating new business, positively impacting bottom-line profitability, ensuring client satisfaction and penetrating new markets. Past client successes include Golfsmith, Kimberly-Clark, Kmart, Kraft, Nabisco, Nextel, Nike, Nokia, Safeway, Sears, True Value Hardware and other industry leaders.

Scott regularly falls into the position of translator between the camps of design and business – equally speaking visual balance and swot analysis. His varied background from pipeline laborer to art director has allowed him to experience seemingly disparate experiences and unite unforeseen commonalities based upon the user. Scott’s love for continuously learning and sharing knowledge with others in ways that are tailored to the individual follows a personal objective that information should unite (not divide) as a catalyst for action without overload or condescension.

My personal mission statement is to be a net creator, not a net consumer. While easier said than done, my mindset is primed and my focus is sharpened in order to leverage my unique experiences into a sustainable future.


Recent Tweets

@getmetacos: The power of unintended positive consequences

@getmetacos: There's more at play than the simplification of tech vs social entrepreneur, but the point stands cc @AC4D

@getmetacos: @kevinrose there can be only one ultimate warrior

@getmetacos: Absolutely next level work from @jkolko and his talented crew at @Blackboard

@getmetacos: RT @BenedictEvans: Very roughly, therefore, half of all photos taken ever will be taken this year

Recent Blog Posts


Pocket Hotline Pitch – AC4D Q3 Recap

The impetus for Pocket Hotline lies deep within the research Chap and I conducted at the Austin Resource Center for the Homeless (ARCH). After 8+ weeks of observing, interviewing, listening and testing, we learned that there were a few breakdowns in the ARCH client service system. One particular breakdown centered around the front desk. It was always busy, no- swamped. Homeless clients were repeatedly asking the front desk staff the same group of questions over and over. As staff were repeatedly answering these questions and the phone kept interrupting the conversation with similar repeated questions. The staff was spending its time doing the same rote tasks while preventing themselves from accomplishing the tasks in which they were highly trained.
“Getting that information when you are the only one sitting at the desk and there are five people yelling at you is tough.”

FindingsWe realized that the ARCH staff was in no way incompetent. They were the figurehead for problems that were felt but not wholly acknowledged. Organization was loose at best. All the resources a homeless client or a caring individual needs to address most questions is available online and via 20+ sheets of nondescript 8.5 x 11 sheets of paper hanging on wall racks behind the desk. Answers were difficult to find and many sheets listed out-of-date information. No one knew who developed some of the documents. No one knew when some were updated. Some documents were updated but the revision date was left alone. No one knew what was right until they were told it’s wrong.

One person inherently creates a bottleneck by his or her limited reach. Getting pulled in different directions by people who have a crisis and want an answer at that exact time was commonplace. Service suffered. Perceived empathy suffered. The staff cares a great deal about helping their clients but a barrage of constant stimuli lowers the level of service for everyone involved.

As we observed, the front staff spent around four hours per week addressing redundant requests. While this time wasn’t necessarily wasted, it was misspent. We formulated the idea of a call center –  a way to free up the staff to do what they were trained to do and not answer the redundant requests. ARCH uses an automated call service to answer the exact questions that were still being asked. When we inquired, we discovered that the City of Austin set it up (ARCH is city property) a few years ago, but left ARCH with no easy way to change the information or understand what sort of information was being requested. Callers became frustrated with the automated answers and wanted a real person to answer questions. A help line became a hindrance.

Almost everyone has a mobile phone. No, really. About 70% of the clients at ARCH had their own phone and the remainder either had access through sharing the phone or using their own SIM card. Communicating on the go was no longer a luxury, but a near necessity.

Above all, we learned that when people have a crisis, they want need to talk to someone. People think that their problem is the most important at that exact time. They want to talk to someone to get the answer that best suits their immediate needs without having to sift through numerous options that all appear identical. People in crisis have critical questions that require a curator to provide unique answers.

Our Solution We had to sift through the gad/bad and the old/new. We had to organize the information into useful chunks of data that could be found easily. We had to provide a method to get an actual person to answer the phone instead of a prompted recording.

We had to free up the staff to do what they were trained to do. We had to bring more volunteers into ARCH. We had to find empathetic people that cared about helping others.

We had to find a way to let everyone provide the best service possible with less barriers. We had to make the new system fit seamlessly into the existing system.

We wanted to develop a way that volunteers could answer the ARCH telephones off-site and expertly answer these redundant requests using the service resource library. When we presented our outsourced call center concept to the front desk supervisor, his initial reaction was “ok.” As Chap and I watched the idea wash over him, he realized the simplicity of our concept. He immediately gravitated towards the organization aspect and said that would be the biggest win- a way to digitally collect and edit all the service information. If we did one thing at all, this would be it.

Many signs pointed to Pocket Hotline becoming a reality. We planned to leverage cloud telephony (Twilio and more), ubiquitous mobile phones and generally inexpensive technology (cloud storage). We wanted to provide a way that the community could conveniently volunteer while quickly building empathy and expertise.

Prototyping After concepting the behavior, function, flow and many aspects in between, Chap and I developed wireframes. Testing tour wireframe was easy with Kolko’s concurrent class segment covering design evaluation. Over the next two weeks we employed Think Aloud Testing and Heuristic Evaluation to test varying aspects of the design- all of which illustrated breakdowns that led to actionable revisions.

Neither of us code iPhone apps (yet). However, we found that a recent revision to jQuery mobile exhibited iPhone-like behavior and Chap can code Rails like no one’s business. After outsourcing the data entry (cheap and totally worth it), we developed an interface that provided critical functionality on a mobile phone. The mobile web app totally worked. Now we needed to test it in the wild.

Enter serendipity. Chap heard about an organization (OK4RJ) that could use our help. They were a small grassroots organization in Norman, Oklahoma that wanted to create a hotline amongst volunteers. Their original thought centered around grabbing a Cricket phone, passing it around and creating an ad hoc information source. We thought this opportunity would be perfect. After a mad dash of inputting the data and setting up a number on Twilio, Pocket Hotline was ready to help.

We received feedback immediately. OK4RJ using the app amongst 15 volunteers. They added new data and the feature requests poured in. It was coming together just in time for our final presentation. As Chap fine-tuned the app, I worked on our pitch. We revised the deck week after week but it was finally becoming real. We had to make decisions. We had to say Pocket Hotline is this and not that. We had to make a stand.

The underlying model is applicable to people in crisis finding answers to their questions, but it’s also applicable to others finding answers to their product/service questions. Chap’s example in the presentation centered around his experience changing the brakes in his new VW bus. He read the instructions but needed a little more guidance. Unfortunately his VW friend was unavailable during the critical moments and Chap figured it out nontheless. But what if Chap could call a hotline that connected him with a VW expert- a guy who knew the VW bus inside and out and could articulately answer questions on-demand? Replace “passionate volunteer” with “avid user” and we could provide a service rivaling (and exceeding) customer service help lines. We could facilitate people with critical questions connecting with on-demand experts.

The slide deck below is the presentation we delivered at last week in a pitch symposium with fellow AC4Ders. Be sure to check out the other great concepts as soon as they’re posted to this blog.

Pocket Hotline Slideshare

Making it REAL In Q4, we’re working on the business side of things: structures, funding, road show pitch decks and so. much. more. But more importantly, we’re figuring out how to help the most people possible. As the deck will illustrate, we are toying with a hybrid business model that will help non-profits and function as a revenue-generating business too. What if the for-profit business portion subsidized the non-profit portion? Could we do more “good” with that?

There are MANY more facets to this concept that we need to articulate. Here are a few:

  • How do we train volunteers quickly? Scenarios? Guided training?
  • How do we rate the experts? How do we filter the pseudo experts and less empathetic volunteers?
  • How do we keep volunteers engaged with the client? How do we keep volunteers engaged and identified with the larger volunteer group and/or organization?
  • How much do we charge? Where are the revenue opportunities?

We’re diving deep to explore these options and many others. We’re figuring out ways to meet the user where they are and help them in more meaningful methods than currently available. We’re figuring out how to do the most “good” while answering critical questions on-demand.

We welcome your comments regarding the Pocket Hotline concept and suggestions for organizations that could use this service.

Posted in ARCH, Social Innovation | Leave a comment

More Architects, Not Firefighters

Throughout our ongoing research, Saranyan and I observed that successful teams are architects. They make plans. They lay the groundwork and build ideas. All too often we slip into reactionary mode- too busy putting out fires to realize that short-sighted focus of “getting things done” may be the biggest distraction from actually accomplishing meaningful actions. There is a degree of recklessness in following a bold directive through to the end. Goals are meant to inspire- to light a spark and orchestrate a conflagration of ideas and actions. An architect may see it through (or change course) but a firefighter will extinguish the momentum before it ever starts. Foresight gives way to formula.

In conjunction with ARCH, my group is researching an ideal client management system from both the organizational and client perspective. In doing so, we’ve learned that a good team makes a huge difference but prescience let’s you quit reacting and start planning. Anticipation isn’t just a gut feeling, it’s the culmination of experience and practice.

A parallel can be drawn to the homeless population in Austin. How does one transcend living for today when they don’t know where they will sleep tonight? Do they want to? Can they succeed even if they tried? Is the hope that tomorrow will be better than today enough to sustain or is there a foundational need to calm the mind before taking a step past survival mode? There has been considerable discussion in class and on this blog regarding whether Maslow’s Hierarchy of Needs is outdated. I was reminded of this point again as I reread a portion of Guns, Germs & Steel where Jared Diamond concludes that humans jumped from hunter/gathering to farming due to predictability and a temperate climate.

With a hefty amount of assumptions baked-in, do we need to make homelessness predictable in order to break the cycle? Aside from the knee-jerk reactions, just think about it. How can we facilitate enough familiarity with the current situation to unveil the next rung of the ladder? How can we change the paradigm and teach architecture to firefighters?

Posted in Social Innovation | Leave a comment

Finally Done (With Scott’s Final)

Below is my final presentation for IDSE 103: Rapid Prototyping.Music: “ShakeShakeShake” by White Denim

Posted in Social Innovation | 2 Comments

An Inquiry Into Water Usage

As a final deliverable for Lauren’s fantastically useful Design Research class, we presented findings for our self-directed projects that focused on recycling. Our team (Alex Pappas, Saranyan Vigraham & Scott Magee) chose water recycling due to the fact that it is often overlooked when thinking about recycling in the general context and it is an issue of active consciousness in Austin due to our water supply and occasional droughts. While our initial interest centered around greywater systems, we readjusted our focus to include water usage at restaurants with and without attached gardens.

Throughout the quarter we applied our newly acquired research techniques from affinity diagramming to contextual inquiries to participatory interviews with our participants. Afterward we transcribed hours of video and immersed ourselves in all the glorious data. We visualized our findings with work models and synthesized new ideas via concept models as we developed solutions for conserving water at Austin-area restaurants. Everything Lauren taught us made sense and this was a real world assignment to prove it.

The following PDF is a slightly modified version of the deliverable we presented in class.

An Inquiry Into Water Usage

Posted in Design Education, Methods | Leave a comment