<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Erratic Connections - Medium]]></title>
        <description><![CDATA[Sometimes 1 + 1 = 3. Sometimes not. - Medium]]></description>
        <link>https://medium.com/erratic-connections?source=rss----d2e6ccdd9d7e---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Erratic Connections - Medium</title>
            <link>https://medium.com/erratic-connections?source=rss----d2e6ccdd9d7e---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:59:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/erratic-connections" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building Team Rapport]]></title>
            <link>https://medium.com/erratic-connections/about-that-team-bond-exercise-5d9c3f57bc54?source=rss----d2e6ccdd9d7e---4</link>
            <guid isPermaLink="false">https://medium.com/p/5d9c3f57bc54</guid>
            <dc:creator><![CDATA[Mike Rivera]]></dc:creator>
            <pubDate>Thu, 07 May 2015 17:55:46 GMT</pubDate>
            <atom:updated>2017-04-05T17:17:07.498Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TqXio0Ti_RJCrYYGhJbHsg.jpeg" /></figure><p><em>Promote better interpersonal relationships and understanding at work</em></p><p>You’ve all been there and done that: the company “team bonding” extravaganza. The ones that might be held off site and include facilitated exercises, games and the like. You’ve had a front row seat to the awkwardness that can ensue — “forced fun” as I’ve heard it described in the past. Why is it that people who spend a good deal of their lives together, yet often only know one another superficially, are asked to build or express team spirit next Wednesday between 10am-2pm at Dave &amp; Busters?</p><p>A common problem with these events is how contrived they can feel. They lay a veneer of ‘team-ness’ over real and often deep seated cultural issues and company problems. They sometimes only succeed in fueling the cynicism that already exists rather than getting people to work proactively for the benefit of all.</p><p>Recently, we experimented with an idea that turned out to be enlightening, empathic, informative and fun. The idea is straightforward: know your coworkers beyond their résumé and work personas. Get personal, but not <em>too</em> personal. If you can tap into people’s life experiences, big or small, you can glimpse how they shape attitudes, incentives, motivations and preferences. You get a better sense of what makes them tick and that’s useful when you’re working together day after day.</p><p>For us — a group of creative problem solvers — the proposition was simple:</p><blockquote>Present your past creative work.</blockquote><p>Using design as a storytelling canvas, coworkers highlighted the milestones they felt most shaped who they became in adulthood and which culminated in their employment at this company, with these people, at this time.</p><p>Each presentation was half an hour in length and open to interpretation. We had two people present back to back on a bi-weekly basis over a lunch hour. The cadence gave people time to prepare, time to digest other presenters’ stories and still have plenty of time to tackle their day jobs.</p><p>An obvious boundary question between work life and personal life came up. <em>How personal is too personal?</em> After all, you don’t talk about your personal life at work on a routine basis. There was also the hurdles that shy or introverted people always face in light of an exercise like this. <em>Would people judge me?</em> It can be nerve wracking to talk about yourself in front of others. One colleague told me “… I was a little uncomfortable … because I tend to be pretty hard on myself when it comes to things I’ve produced,” and “Having it based on your past art work was pretty intimidating.” As a counter balance, however, I also heard, “This is going to be a lot of fun” and “It’s interesting to hear about people’s influencers and how they’ve helped create pivot points in people’s lives. It was a fun way to get to know someone!”</p><h4>Results &amp; Reactions</h4><p>You’ll be fascinated, impressed and surprised by the people you sit next to day after day. And they, in turn, will be blown away by your stories. You’ll have insight into your colleagues that can foster empathy, respect and trust — all the things that team bonding is supposed to generate.</p><p>Colleagues come into focus as you connect the dots between their past and present. As one of our staff participants wrote, “I think it’s incredible to get a peek inside our co-workers lives. It’s very cool to see where they came from and how they ended up doing what we do. We work with a lot of talented people!”</p><p>Another participant told me that the sessions evened the playing field. “It wasn’t about titles or skill sets or years of work experience and instead about knowing the people around you by exposing a side that’s rarely on display in a work setting.”</p><p>Coworkers followed up with one another to talk at length about certain topics, events and past design samples included in their presentations. Connections were made. “I’ve actually been thinking about how to produce more ‘art’ since we’ve begun this whole exercise. I guess you could say it’s been another source of inspiration for me.”</p><p>This exercise won’t take a team from dysfunctional to functional overnight, mind you. Good working relationships and a dynamic, well functioning culture take effort and intention. This is just one tactic we discovered to be effective.</p><h4>An Example</h4><p>Below is the presentation I made to my team as part of this exercise over a GoToMeeting. Others followed the same basic path, but reinterpreted and reformulated it to suite their needs and the stories they wanted to tell. Note my hesitancy and vulnerability, but also (hopefully) insights into how my mind works that probably wouldn’t arise in ‘normal,’ everyday work interactions.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F126196181&amp;src_secure=1&amp;url=https%3A%2F%2Fvimeo.com%2F126196181&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F516643168_1280x800.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="640" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/903b98ac7c57995a6faff599ff420bbf/href">https://medium.com/media/903b98ac7c57995a6faff599ff420bbf/href</a></iframe><h4>Tips for Success</h4><ul><li>Team building should not take place during off hours. People have a life outside of work and it should be respected. If anything written here is important to you, then it’s important to dedicate the work day to it.</li><li>Don’t make it mandatory. It only works if people desire a deeper connection with others or who want to invite people in for a closer look. Leave what to share and how to share it to each person. The interpretation is, in itself, a window into the person.</li><li>Go back in time as far as necessary or desired. It will take time to think through what is, at first glance, a simple question. Allow enough time for people to craft their story, find representative things to highlight and to prepare a presentation (the fidelity of which is theirs to decide). As one colleague voiced it, “I approached the presentation as how I got to where I am. Basically a life history picking out the things I thought had an affect on me becoming a creative.”</li><li>Be a model. If you introduce this concept, be willing to go first. Initially, no one was quite sure what this exercise was going to be or what the expectations would be for them if they chose to participate. As the person who pitched the idea and the first to go, I too wasn’t sure where I’d end up. Mine was likely the least autobiographical and, having seen where others took their presentations, I would personalize it to a greater degree than I did.</li><li>Allow for a short Q&amp;A at the end of each presentation. Let the seeds of further connection take root with a short follow-up period.</li><li>30 minutes per person worked well as did scheduling two people every other week.</li></ul><h4>Forming, Storming, Norming, Performing</h4><p>I’m reminded of a <a href="http://en.wikipedia.org/wiki/Tuckman&#39;s_stages_of_group_development">group development model</a> from business school days that describes the stages any group goes through as they develop:</p><ul><li>Forming groups are new to one another and things are polite as relationships are built.</li><li>Storming groups have built strong enough ties to express criticism and divergent opinions.</li><li>Norming groups are able to get past conflict to rally around common goals.</li><li>Performing groups are those that are self reliant, proactive and well functioning on all levels.</li></ul><p>An exercise like the one described in this article can fit into any of these stages. It can be used as a means to connect people in early stages and as a means to build trust and self sufficiency in people during later stages. What your team gains is contingent on many factors, some of which are beyond this article’s scope. Nonetheless, our team found it beneficial and yours can too.</p><p>I’d be interested to hear from groups who try this or something similar. Leave your feedback!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d9c3f57bc54" width="1" height="1" alt=""><hr><p><a href="https://medium.com/erratic-connections/about-that-team-bond-exercise-5d9c3f57bc54">Building Team Rapport</a> was originally published in <a href="https://medium.com/erratic-connections">Erratic Connections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What NASA Knows About Great UX Management]]></title>
            <link>https://medium.com/erratic-connections/what-nasa-knows-about-great-ux-management-bafdd1f8883c?source=rss----d2e6ccdd9d7e---4</link>
            <guid isPermaLink="false">https://medium.com/p/bafdd1f8883c</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Mike Rivera]]></dc:creator>
            <pubDate>Wed, 28 Jan 2015 03:25:58 GMT</pubDate>
            <atom:updated>2016-02-02T18:29:54.670Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*upocE1seB-PG6n8Wmxnk3w.jpeg" /></figure><p>In the 1970s, NASA undertook an assessment of airline pilot performance. They needed to understand why pilot error had become the leading cause of airline accidents. <a href="http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19790006598.pdf">What they learned</a> helped make commercial air travel one of the <a href="http://www.rita.dot.gov/bts/sites/rita.dot.gov.bts/files/publications/national_transportation_statistics/html/table_02_04.html">safest modes of transport</a> in the U.S. today. Their research shed light on the importance of workload, leadership and communication — integral aspects of running successful UX engagements. What can we learn from this seminal research?</p><h3>Balancing Workloads</h3><p>Research found the best performing airline captains kept tabs on their crew’s workload. Interestingly, pilot error wasn’t typically due to lack of skill or knowledge of proper procedures. Instead, the important factor was how their skill and knowledge was applied. The best performing crews had captains who managed how many tasks each crew mate was asked to perform. When workload became an issue for anyone, they delegated, relieved or rebalanced everyone’s duties such that each crewmember could better concentrate and focus for optimal performance.</p><p>Captains who didn’t manage their crew’s workloads consequently had worse performance. The study found that when anyone had too many duties, they became overtaxed which lead to performance problems and finally to errors.</p><p>While errors in a UX project don’t have immediate life and death implications as they might in commercial aviation, they can have negative consequences. When people are overtasked, they cut corners, consciously or not. They can overlook or be blind to problems, they can experience delays identifying and handling problems, they can fall back on assumptions when objective data is available, and they can develop tunnel vision causing an inability to assess the entire project as a whole.</p><p>I’ve been witness to engagements where scope outstripped the ability of a project team to deliver the best work they could in the time allotted. In these cases, morale sank as individuals realized they couldn’t deliver the quality they expected (and which they knew they could provide). They left projects feeling the end result could have been better — sometimes in explicit terms when they knew gaps existed and sometimes with vagueness when they had a general feeling that problem definition, exploration or execution could have been pushed further.</p><p>Ensuring each contributor on a team has a manageable workload helps keep people engaged, performance and morale high, and stress at manageable levels. All of these characteristics contribute to fewer errors and, ultimately, less rework since time and effort are being used more effectively.</p><p>But how do we balance workloads effectively? As NASA’s research suggests, keeping tabs on workloads is one of the captain’s primary duties. If the captain assigns himself too many tasks, he essentially causes tunnel vision for himself, unable to judge his crew’s workload. The lesson is to have one teammate delegate enough tasks so they can effectively evaluate workloads and make decisions concerning them. Failure to do so jeopardizes overall performance and risks errors big and small.</p><h3>Leadership</h3><p>NASA found that during simulations of emergencies it wasn’t clear who was in control — the captain or co-pilot — during times when one or the other looked up information, communicated over the radio or discussed courses of action. This is in stark contrast to how captains typically lead in the 70s — which is to say they were authoritarian. As an <a href="http://www.vanityfair.com/business/2014/10/air-france-flight-447-crash">Atlantic article</a> put it, researchers found “…a culture dominated by authoritarian captains, many of them crusty old reactionaries who brooked no interference from their subordinates. In those cockpits, co-pilots were lucky if occasionally they were allowed to fly.” Also, “It all depended on the captains. A few were natural team leaders — and their crews acquitted themselves well. Most, however, were Clipper Skippers [authoritarians], whose crews fell into disarray under pressure and made dangerous mistakes.”</p><p>We in the user experience world would likely agree that the best outcomes don’t come from a strict hierarchical and authoritative environment, but one where collaboration is encouraged. In an environment like this, colleagues lend critical eyes, stakeholders provide context, and customers pass judgement via their attention and wallets. These feedback loops are meant and encouraged to pinpoint problems and signal possible solutions.</p><p>Authoritarianism, by definition, is counter to this culture. It doesn’t encourage teamwork, critical analysis and experimentation nor does it tap <a href="http://en.wikipedia.org/wiki/The_Wisdom_of_Crowds">the wisdom of crowds</a>. In a business world that increasingly sees UX as the critical difference between success and failure, authoritarianism will likely produce worse results. The era of the lone visionary (if, in fact, it ever existed) always loses ground to an active, diverse group. Our world changes too quickly and the Internet has largely removed the ability for any one person to take advantage of <a href="http://en.wikipedia.org/wiki/Information_asymmetry">information asymmetry</a> for long.</p><p>While an authoritarian approach proves to be problematic, NASA did find a need for clear decision making. While collaboration brings benefits, all projects will require decisive calls (typically from someONE) when multiple and equally good options exist. Teams need leadership, products need leadership and companies need leadership. The trick is to avoid dictatorship in preference for leadership flowing from a collaborative environment where all input is sincerely taken into account.</p><p>At <a href="http://www.sliceoflime.com/">Slice of Lime</a>, we ask clients to provide a project owner (PO) — someone on the client side who can answer questions, prioritize workloads and make decisions quickly. The role requires authority and accountability, authoritarian characteristics to be sure, but tempered by the environment in which it exists. Our team gives recommendations, provides a reality check and influences the direction the team and project take. We push our clients, they push us and our client’s customers push everyone. The PO’s job within this dynamic is to weigh the work output and the insights from customer research against their internal culture, priorities, timelines, and budget. As a team, we all have the same goals, but since everyone’s contribution has a particular focus we can run into forks in the road where multiple paths forward appear. These paths may be relatively equal in terms of their chance for success. The PO, in this situation, is empowered to make a decision on behalf of the entire team.</p><p>This approach works without it degrading into a ‘do it my way’ mandate because the team worked to provide the options within a collaborative environment. If research proves the chosen direction to be poor, the team can course correct without finger pointing or ‘I told you so’s.’ The idea is not to empower the product owner to be a dictator, but to empower them to choose rationally knowing the tradeoffs and risks as surfaced by the team. The group acknowledges and supports the PO’s ability to make hard choices when needed because they are the source of those choices and will be full participants in any course corrections that may materialize.</p><p>On our side, we too have a team lead who acts in a similar vein to the PO although primarily being decision maker for our team. This role also weighs factors at hand in order to plot a course for our team’s efforts that will meet the needs of our client while also ensuring we are doing the best work we can. Again, it’s about making rational choices knowing the tradeoffs and risks at hand. Communicating these judgements and any recommendations from the team falls on the team lead’s shoulders while others move ahead with the next set of priorities. Because trust has been established through good communication, our recommendations will likely heavily influence the PO’s decision. In effect, we help guide the project even though the client retains decision making powers and the overall vision for the project.</p><h3>Communication</h3><p>As you probably already know, good communication is the key to the smooth choreography of a project and project team. NASA discovered “…that teamwork matters far more than individual piloting skill. This ran counter to long tradition in aviation but corresponded closely with the findings of another NASA group, which made a careful study of recent accidents and concluded that in almost all cases poor communication in the cockpit was to blame.”</p><p>Advising people and teams to ‘communicate better’ is certainly easier said than done, not to mention a bit lazy on my part. It masks a lot of dynamics that pose roadblocks (an article all its own), but the advice nevertheless stands. In <a href="http://www.sliceoflime.com/">our company</a>, we work very hard to prioritize communication. We’ve adopted <a href="http://agilemanifesto.org/">Agile</a> as our preferred workflow and one of its principles is “individuals and interactions over processes and tools.” We apply this mantra both internally and externally.</p><p>For example, once a month, our entire company gathers to talk through issues good, bad and somewhere in between in a safe environment where open and honest conversation can be had. Action items spill out of these conversations and we work to improve as a group. Externally, we do the same. We hold regular meetings with clients to ensure the project is running smoothly and any brewing problems are dealt with before they become impediments or interpersonal baggage. We do other things as well, but you get the point. If you consciously make communication a priority, then it’ll be a priority. It’s that simple.</p><h3>Putting It All Together</h3><p>Many of the examples I’ve given from Slice of Lime have taken time to implement. We didn’t arrive at our current process overnight and I wouldn’t expect it from other companies. Tackling these topics will, I believe, result in positive change for you and your organization. Your priorities and culture will influence the end result however. I don’t wish to say that our way is the right way. It’s the right way for us at this time. Tomorrow is another day and we’ll evolve to meet the challenges and opportunities we encounter.</p><p>You will find what works and doesn’t through trial and error, as we have. We still find ourselves on rickety rails from time to time, but they don’t completely derail us. Our communication feedback loops help ensure we spot and deal with problems as early as possible.</p><p>You will also find that all three aspects discussed — leadership, workload and communication — work in tandem. A change to one affects the others. This is inevitable as all three blur into one another to some extent. Be cognizant of your organization’s particular links between these areas and be mindful of disruptions that may snowball from any one change. Again, an iterative and collaborative approach will help.</p><p>We find, for example, that our tight communication with clients builds trust. Trust enables workload issues like scope creep to stay in check. Our tight collaboration ensures that the client (and the PO in particular) is aware of the impact of new features, priority changes and insights from research. Since they ultimately have decision making power within the team dynamic over what to do and in what order, they are acutely aware of how scope change will affect the project. We inform them day to day on our progress and that, in turn, allows them to better manage workload within their cost and time constraints. And it’s all made possible by the importance we place on communication.</p><p>Has your organization found good tactics around these topics? If so, please leave your thoughts. I’d love to hear them.</p><p><em>Originally published at </em><a href="http://www.sliceoflime.com/what-nasa-knows-about-great-ux-management/"><em>www.sliceoflime.com</em></a><em> on January 27, 2015.</em></p><p><a href="http://www.vanityfair.com/business/2014/10/air-france-flight-447-crash"><em>William Langewiesche’s “The Human Factor” inspired this article</em></a><em>. Highly recommended, especially if you’re an airplane junkie.</em></p><p><em>Photo by </em><a href="http://commons.wikimedia.org/wiki/File%3AAirbus_A380_Cockpit.jpg"><em>Steve Jurvetson</em></a><em>, via Wikimedia Commons</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bafdd1f8883c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/erratic-connections/what-nasa-knows-about-great-ux-management-bafdd1f8883c">What NASA Knows About Great UX Management</a> was originally published in <a href="https://medium.com/erratic-connections">Erratic Connections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Agencies Sell (and Clients Buy) Informed Decision Making]]></title>
            <link>https://medium.com/erratic-connections/ux-agencies-sell-and-clients-buy-informed-decision-making-a9d925fbe725?source=rss----d2e6ccdd9d7e---4</link>
            <guid isPermaLink="false">https://medium.com/p/a9d925fbe725</guid>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Mike Rivera]]></dc:creator>
            <pubDate>Wed, 07 Jan 2015 15:28:56 GMT</pubDate>
            <atom:updated>2016-02-02T18:27:08.031Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vGl73I0sQoFTKBhbZNw2Iw.jpeg" /></figure><h4>What is User Experience (UX)?</h4><p>UX is a process, an approach, a way of thinking and an outcome. Outcome, in particular, is the key aspect to UX’s value. Are you solving a real problem? Are you tackling something meaningful to people? Are you bettering the organization, the system, the… <em>whatever</em>? I hope so. Otherwise, you’re selling an inferior product (be it a physical thing, a service, an idea, etc.).</p><p>Let’s also be clear that outcomes are not journey maps or competitive analyses or any number of other artifacts that will be generated during the course of a project. As much as possible, we want to <a href="http://www.smashingmagazine.com/2011/03/07/lean-ux-getting-out-of-the-deliverables-business/">get out of the deliverables business</a> within agency/client relationships because artifacts aren’t valuable outcomes. They’re indeed important stepping stones in the value creation process (especially internally for the project team), but they are not the final outcome where customers will benefit from real, tangible value in the form of solutions to their problems.</p><h4>How Can UX Be Sold?</h4><p>If you’re a UX practitioner (agency or otherwise), you will inevitably need to pitch clients and craft proposals to win work. In doing so, you want to avoid selling the constituent parts of UX — the deliverables you may or may not create and the methodological details employed to complete the job. These things introduce complexity into the discussion and clients may associate complexity with greater cost, longer timelines, hard to manage processes and bigger headaches all around.</p><p>As an analogy, Benedict Evans made the case <a href="http://bloom.bg/1EKOD2p">in a presentation</a> that software isn’t eating the world so much as tech is outgrowing the tech industry. By this he means that new companies are being created that use technology but are not technology companies per se. Similarly, a user experience agency uses UX methodologies, produces needed deliverables, and employs professionals with highly refined skills, but those are not the things it sells outright. Buyers need solutions to problems, organizational silos bridged, existing products and services analyzed, customer insight, recommendations and more. All of these UX details amount to stepping stones that get your client to whichever outcome they need (and which may change as the project evolves).</p><p>In essence, <strong>UXers sell informed decision making and clients buy the value those decisions bring them</strong>. Talking about anything else only serves to confuse and complicate. Go into details if requested. Otherwise, tread lightly.</p><h4>What, Exactly, is Informed Decision Making?</h4><p>Some clients will think a completed, ‘tangible’ product like an app or redesigned feature set is being bought. They are, after all, the easy things to spot and are likely the things they brought up during the sales process. An argument that these things are valuable outcomes can be made, absolutely. They’re the things the client’s customers will use and derive benefit from. And the client will also claim value in whatever form the final project takes — they can point their bosses to it and say “we bought that.”</p><p>From the UX agency’s perspective (and the companies that share the same vision), informed decision making is what’s on sale. <em>The</em> <em>thing</em> (app, site, etc.) is the inevitable product that materializes in a UX process where we don’t (and can’t) know ahead of time what exactly needs to be created. Agencies ask questions, unravel problems, advocate for people, and make sense out of chaos. They consider context, bring stakeholders together, adapt as change occurs, and continuously learn. Agencies facilitate the ability for clients to make good choices for themselves, their customers and their stakeholders. The research, analysis, synthesis, exploration and iteration is what drives a team from point A to point B. A thousand decisions will be made during the course of a project and adding those up is the true value a UX agency offers to clients— making the right decisions at the right time for the right person.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9d925fbe725" width="1" height="1" alt=""><hr><p><a href="https://medium.com/erratic-connections/ux-agencies-sell-and-clients-buy-informed-decision-making-a9d925fbe725">UX Agencies Sell (and Clients Buy) Informed Decision Making</a> was originally published in <a href="https://medium.com/erratic-connections">Erratic Connections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Fundamental Higher Ed Website Issue: Centralization vs. Decentralization]]></title>
            <link>https://medium.com/erratic-connections/the-fundamental-higher-ed-website-issue-centralization-vs-decentralization-3ae14ee613aa?source=rss----d2e6ccdd9d7e---4</link>
            <guid isPermaLink="false">https://medium.com/p/3ae14ee613aa</guid>
            <category><![CDATA[higher-education]]></category>
            <category><![CDATA[higher-ed]]></category>
            <dc:creator><![CDATA[Mike Rivera]]></dc:creator>
            <pubDate>Mon, 08 Dec 2014 16:00:40 GMT</pubDate>
            <atom:updated>2016-02-02T18:35:03.407Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/desat/multiply/blue/60/overlay/blue/1*sKSzHemDB4LM4Z6b3kXTfw.jpeg" /></figure><h4>What ails higher ed website experiences and what would make them better make two sides to the same coin</h4><p>You can’t talk about centralization unless you first talk about how things currently work under a decentralized system. So I’ll address that first.</p><p>Many traditional universities (most? all?) take a decentralized approach toward their websites, both in terms of creation and maintenance. It’s thought that a decentralized structure where each division, school, college, department and administrative unit effectively controls their space and content on the web is the best way to manage the overall site. Core web teams tend to be small given the size of a university’s online presence so the thinking is “why not shift maintenance of each section of the site to their respective owners?” With a content management system in place, this becomes a matter of simplicity and smart workflow. The core web team creates the initial site based on each unit’s needs and wishes, the site is developed within the CMS, each unit gets trained on how to make updates through the CMS, and then the web team is freed up to go through the same process for the next unit on campus. Conventional wisdom would say this is a rational and reasoned approach, right?</p><p>Maybe, but I think the opposite approach — centralization — reaps greater rewards. I’m not against decentralization completely, however. There’s a place and time for it, but to revolve your web efforts around the promises of decentralization will only lead to trouble. There is a happy medium. I’ll cover the benefits to centralization in a moment, but first, here’s a list of issues decentralization wittingly and unwittingly creates:</p><ul><li><strong>Inconsistent experience</strong>: With so many different units within the organization, the umbrella website amounts to a consortium of marginally related sub-sites. Each unit independently decides what their needs and wants are and isn’t required to consider other units or the overall experience of the umbrella site.</li><li><strong>Little focus</strong>: When a site communicates to a diverse range of audience needs within the same space, it becomes schizophrenic at best, confusing and frustrating at worst. Should information that satisfies one need sit next to information for a totally different need? Separation along people’s jobs-to-be-done could clarify an organization’s message and offer a better overall visitor experience.</li><li><strong>Poor navigation, Part I</strong>: Since every unit gets a semi or completely custom made site, consistency of navigation isn’t ensured. Decentralization allows even similar units to offer completely different sets of links even though their audiences’ goals are relatively homogenous. Take a centralized view of audience needs, build a navigation system that speaks to it (and do it only once) and then roll it out to the necessary sites.</li><li><strong>Poor navigation, Part II</strong>: The kind of navigational inconsistency above can be remedied relatively easily. What’s harder for the organization is to break away from the idea that navigation should mimic its org chart. Our research has found that students largely don’t know and don’t care that psychology is to be found via the Psychology Department’s site which is itself found via the Arts, Humanities &amp; Social Sciences site. Furthermore, why would we expect them to know the difference between the Psychology Department and the Professional School of Psychology? People think in terms of subject areas, so let’s use a navigational scheme that works with that in mind.</li><li><strong>Disjointed marketing efforts</strong>: In effect, a decentralized world creates barriers between internal groups. Since units are largely independent from one another, it’s difficult to see, let alone create, symbiotic relationships. The web offers an alternative where all internal groups can cross promote events, programs, people, research, etc. to maximize the impact of communications. Some level of centralization is needed, however.</li><li><strong>Reactionary processes</strong>: If the web team is utilized as a simple vendor who delivers websites for each unit of the larger organization, then the team’s expertise is never fully brought to bear on the broader, umbrella site. Centralization allows a web team to proactively make the site better for all since it’s the only group that’s cognizant of the overall experience.</li><li><strong>No accountability</strong>: A decentralized structure spreads accountability of the site’s overall success or failure among a large number of people- so many that the site is effectively unaccountable to anyone or any group. Global decisions or mandates that would introduce economies of scale (as outlined in this very list) are impossible to enact in this climate. Centralization places control and responsibility in the hands of a few. It’s not a power grab, it’s efficiency (see the next point). Accountability creates the motivation to continually create high quality work.</li><li><strong>Inefficient use of resources</strong>: Content might be needed in several places on the site. In a decentralized world, that content is likely duplicated in the system as people in different units post the information to their independent sites. Duplicated content = duplicated efforts to maintain = inefficient use of people’s time.</li><li><strong>Slow turnaround time</strong>: To create and maintain independent sites causes longer timelines than necessary compared to a centralized world where there is only a single visitor experience to manage. Build it once and then reuse. If you make a change, it’s globally deployed.</li><li><strong>Unsustainable, Part I</strong>: As internal groups begin to harness the web’s power beyond static pages, the web team becomes ever more strained to keep up with individual, unit level requests. Centralized efforts allow the web team to prioritize requests and projects based on institutional goals and customer input. The most important projects with the greatest overall impact get the attention they deserve, while less important projects are accomplished as time allows, if at all.</li><li><strong>Unsustainable, Part II</strong>: Another aspect to consider are the ongoing costs of maintenance. As sites grow, so too does the effort to keep them up-to-date. The big advantage to decentralization revolves around just this problem — allowing the masses to create and maintain sites after the web team gets it launched. But it’s not without pitfalls in terms of ensuring consistency of content, keeping links from breaking, ensuring new content is created often enough and so on. Are the resources in place to realistically accomplish this?</li><li><strong>Decades of expertise go untapped</strong>: The web team, in aggregate, probably has decades of web experience under its belt. Decentralization empowers relatively unskilled web workers to affect the site’s overall visitor experience in potentially negative ways. While it makes sense to decentralize some aspects of a site’s maintenance, why not tap the breadth and depth of the team’s skills and knowledge for major decisions?</li></ul><p>Next, I’ll discuss the advantages of centralization. But before I get into it, let me provide context to the discussion.</p><p>I have no issue whatsoever with decentralization in terms of content. What I do have an issue with is decentralizing the management of other aspects of the web effort — strategy, IA, design and code. Decentralizing those aspects result in the pitfalls I outlined above. Now there’s always an exception to the rule, but those should be few and far between and that mantra holds true in this case.</p><p>In a nutshell, centralizing a site’s management should manifest itself in the opposite ways already outlined. Here’s the quick rundown:</p><ul><li>Greater consistency in design, navigation, functionality, overall experience</li><li>Better focus and clarity in communicating the organization’s messages and goals</li><li>A more symbiotic effort toward marketing the organization to a diverse set of audiences</li><li>A systematic, proactive approach to improving the visitor experience</li><li>Single source accountability for many of the site’s performance metrics and marketing goals</li><li>Greater efficient use of time, effort and resources</li><li>Faster project turnaround time</li><li>Generally, a more sustainable approach</li><li>A happier web team/better morale</li></ul><p>However, all that said, centralization does raise issues. Most prominent is the fact that it’s a huge break from the past. The university has long given individual units large latitude in terms of how to run their groups. So much so, that the bigger units don’t even bother with the web team. Instead, they hire outside agencies to knock out whatever it is they need to accomplish. That’s just decentralization by another name though. Our biggest hurdle is the perception that centralizing the site will mean an inability to uniquely market each unit. The argument will go something like: the anthropology department will look like the political science department which will look like the music department and so on down the line.</p><p>That’s where the decentralized approach to content comes back into the picture. Content is the best, most efficient way to make your pitch. Yes, design, layout, colors, etc. influence decisions, but (and this is coming from a designer) it matters less that photos are floated left versus right compared to what those photos depict. It matters less that copy is Helvetica rather than Georgia than what the copy says. The ability to determine content <em>is </em>the ability to market.</p><p>What centralization ultimately allows is efficient, planned out efforts to roll out improvements and functionality in a consistent, controlled and timely manner based on visitor and university needs. The organization and visitors benefit while the web team stays sane.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ae14ee613aa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/erratic-connections/the-fundamental-higher-ed-website-issue-centralization-vs-decentralization-3ae14ee613aa">The Fundamental Higher Ed Website Issue: Centralization vs. Decentralization</a> was originally published in <a href="https://medium.com/erratic-connections">Erratic Connections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Design and Congress are More Similar Than You Think]]></title>
            <link>https://medium.com/erratic-connections/what-client-services-can-learn-from-an-outgoing-congressman-2360731cac8b?source=rss----d2e6ccdd9d7e---4</link>
            <guid isPermaLink="false">https://medium.com/p/2360731cac8b</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[congress]]></category>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[scientific-method]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Mike Rivera]]></dc:creator>
            <pubDate>Sun, 07 Dec 2014 04:59:48 GMT</pubDate>
            <atom:updated>2017-04-08T05:00:56.994Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aV03h565L3OQQRd-ZbLk5g.jpeg" /></figure><blockquote>tl;dr</blockquote><ul><li>Your company’s cultural ethics — both official and unofficial — affects your client relationships. Be intentional in what they are and how they’re applied.</li><li>Stalled projects need a jumpstart even if the catalyst isn’t perfect. Simply moving forward allows the team to become ever more perfect through iteration.</li><li>Research can combat the downsides of ideological intraction. Confidence in research, the process of acquiring it and how it’s used is paramount.</li><li>A willingness to be wrong or to make mistakes is not a character flaw if it’s used to learn and grow. You must start somewhere or else you won’t start at all.</li></ul><p>I listened to this interview with retiring US Representative Rush Holt and it struck me how well his viewpoint could be applied to UX agencies.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Fvisual%3Dtrue%26url%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F160092264%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fdecodedc%2Fepisode-44-exit-interview-rep-rush-holt&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000086097835-ces9sh-t500x500.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="500" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/7fa3bd40a8528722f57abdc846fe38e3/href">https://medium.com/media/7fa3bd40a8528722f57abdc846fe38e3/href</a></iframe><blockquote>“Politics is applied ethics.”</blockquote><p>Holt makes the case that his time in Congress was one where he would apply his ethics publicly (and he admits that he came up short from time to time). Similarly, UX design is also an arena where you apply your ethics. Ethics can, of course, encompass how you treat people, your business practices, etc. but they should also encompass your principles and convictions. The process you use, your client interactions and your company’s culture reflect what you stand for while they guide teams and set expectations for your clients.</p><p>Ethics tend to be black and white issues, but applying them is often not. Knowing whether you’re willing to adapt your principles and convictions (and to what extent) is a key internal discussion. This isn’t easy work. Are you willing to lose a client in support of your ideals, are you willing to bend your ideals, or are your ideals in need of an overhaul? It’s one thing to say you work under an agile methodology, for example, but how strictly? In the land of UX, customer feedback is key, but if the client hesitates or declines, do you take on the assignment in hopes of convincing them of its value over time or do you simply say no, we don’t work like that and decline the revenue?</p><p>Do you know your organization’s non-negotiables? Who has authority to manage difficult situations and negotiate trade-offs? Is it an empowered person or a result of a process? What implications does it have on timelines, budget, morale, etc.? These aren’t easy questions to answer, but knowing your boundaries sets expectations for all involved and formalizes when and how to deviate from the norm.</p><blockquote>“…a more perfect union…”</blockquote><p>Holt talks about how the founding fathers aspired to a more perfect union — i.e. they knew they didn’t have all the answers and therefore created a system that could evolve to meet the needs of a dynamic country. Because of this inate ability to change, he rejects the idea that government is incapable of progress, of making things better for its citizens.</p><p>Most UX agencies would agree with those sentiments. After all, progress defines iterative design, right? Why are UX agencies hired if not to make improvements? As an agency person, I often see organizations hire outside teams even though they already have internal resources capable of accomplishing the work. What the agency has that internal teams don’t is often a “fresh perspective” or an “objective viewpoint.” That can be taken as code that internal teams are not capable of progress on their own. Maybe that’s true, but I don’t think so. Instead, I believe organizations sometimes need an outside force to create the momentum for a more perfect union that can then be sustained internally. The hard work is in getting off the ground, simply getting something, anything, accomplished. It may not be the right thing or the best thing, but it’s what’s needed to get on the path to greatness.</p><blockquote>“…ideology has trumped evidence.”</blockquote><p>Holt, who was a physicist before New Jersey’s Congressman, lays out two important scientific principles:</p><ul><li>Evidence- Every position or answer posed should be substantiated with facts.</li><li>Verification- Ideas need to be open to scrutiny in order to know whether it’s correct or not.</li></ul><p>“Scientists want the evidence first and consensus later. Politicians tend to look for consensus first, and look for the evidence to match. That has set up a bad precedent in the current Congress,” Holt says.</p><p>In UX design, as in politics, ideology thwarts data driven decisions. Opinions and anecdotal evidence can turn out to be true, no doubt. But to rely on them as a consistent source for good decisions is risky at best. Holt uses the example of cigarette smoking to make this point: you can find an old person who smoked their whole life and conclude that smoking doesn’t kill. But that’s one person. Statistically, there’s no doubt that smoking shortens lives. Single points of data do not give you a full picture.</p><p>Our agency takes a hypothesis driven approach. We take the initial thoughts and discussions that take place early in a project as a starting point — something to work from. We then conduct research in order to support or deny those hypotheses. We may also just as easily find that parts of the hypotheses are correct, but other parts are not. Whatever the case, though, we’re able to define problems, see opportunities and begin to piece together a strategy that allows us to progressively move forward on solid ground. Additionally, once a solution is envisioned, we can test it too. Does it actually solve the problems at hand? Are the opportunities we discovered real? Is the strategy well formed? All these questions can be tested and improved upon with further thought and research.</p><p>One myth about science, which Holt addresses, is that science is not “cut and dried and definite.” The idea is not to throw your hands up and pronounce that research may be flawed therefore we shouldn’t take it into consideration. Rather, the research at hand should be acted upon because it’s the best information available at the time. As new research or better theories about what the research means comes to light, then you can change course appropriately. But to not act at all is a recipe for poor performance or, worse, outright failure.</p><blockquote>“…people are not allowed to change their mind.”</blockquote><p>An interesting topic during the interview, and the last one I’ll comment on, is the discussion of how politicians are almost to the point of being unable to change their minds for fear of being labeled flip floppers, weak leaders, or worse. Holt is convinced that being open to change as new information is gained is the hallmark of good governance. As previously brought up, the lack of 100% certitude that comes with a scientific approach should not be grounds for falling back on ideology. Some things simply have more evidence in support of them than other things.</p><p>UX design is predicated on finding common ground betweeen the client and agency in this regard. If either side sticks to ideology when research can be put to bear, the project is placed at risk, especially if a data driven methodology is among your core principles (i.e. part of your ethics). Agreement on how decisions will be made (and on what grounds) is central to getting things done. It not only will remove one point of frustration, but will also set the client up for success as the agency inevitably ends their engagement and the client must take stewardship of the project on their own.</p><p><em>Photo: “</em><a href="http://commons.wikimedia.org/wiki/File:United_States_Capitol_west_front_edit2.jpg#mediaviewer/File:United_States_Capitol_west_front_edit2.jpg"><em>United States Capitol west front edit2&quot; by United_States_Capitol_-_west_front.jpg</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2360731cac8b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/erratic-connections/what-client-services-can-learn-from-an-outgoing-congressman-2360731cac8b">UX Design and Congress are More Similar Than You Think</a> was originally published in <a href="https://medium.com/erratic-connections">Erratic Connections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Invest in Research?]]></title>
            <link>https://medium.com/erratic-connections/why-invest-in-research-52a88d285687?source=rss----d2e6ccdd9d7e---4</link>
            <guid isPermaLink="false">https://medium.com/p/52a88d285687</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Mike Rivera]]></dc:creator>
            <pubDate>Sun, 07 Dec 2014 04:59:38 GMT</pubDate>
            <atom:updated>2016-02-04T15:11:35.228Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t9X-NYNgbuUq1jdrs2dyIg.jpeg" /></figure><h2>5 Reasons to Invest in Research</h2><h4>Arguments to help you promote research within product design and development</h4><p>Customer research (also known as user research) is a powerful business tool to understand people’s behaviors and the cause and effect those behaviors have on purchase decisions and usage patterns. The business world instinctively grasps this value on a fundamental level, yet sometimes skips it anyway. Some common reasons they choose to skip include time, cost and a belief that the factors for customer success are already known. While I wouldn’t dismiss any of these reasons outright, my experience tells me they’re often myths. Research needn’t be a speed bump, budget buster, distraction or inconvenience. Rather, it’s a practice and mindset that comes with the following positive benefits.</p><h3><strong>Make better decisions</strong></h3><p>Whatever your skill set and role, researchers collectively bring strategic thinking, tactical skills, best practices and intuition to the table. Research brings another voice to the conversation — your target audience’s — that is objective, free of organizational bias and able to surface ideas that may otherwise not be seen or considered. These outside perspectives can profoundly change how the world is understood and, therefore, how it needs to be approached.</p><h3><strong>Reduce risk</strong></h3><p>Research allows project teams to better pinpoint where attention, time and money are best spent. A team that has a comprehensive understanding of problem(s) will also be a team of effective problem solvers. And while research does come with financial and timeline implications, it reduces or completely eliminates the greater costs incurred building problematic or failed products and services (not to mention the costs needed to fix them).</p><h3><strong>Fill knowledge gaps</strong></h3><p>Intuition, experience and personal observations get teams far. Research, in combination, takes them farther. It brings more voices to bear, more subtlety and nuance to what may otherwise be broad generalizations, and pointers when the path ahead is unclear. It also helps surface biases and cultural norms that may negatively impact the project’s success.</p><h3><strong>Improve organizational dynamics</strong></h3><p>Research can provide a framework to align people and departments through collaboration and a shared understanding of customers, their problems, and how well the organization is positioned to serve customers and address their problems. Research can rally a team by injecting it with purpose and inspiration.</p><h3><strong>Speed development</strong></h3><p>Some perceive research as slowing down a team’s progress. If speed to market is the goal, then this perception may be correct. But if the goal is to build the right product or service for the right people and for the right reasons, then research actually speeds the development process. Teams will ultimately reach success quicker with research than without it and will do so with fewer public stumbles.</p><p>If space for research is included in the design and development processes, teams gain an ability to effectively manage and apply their time, money and attention. The results are more likely to be exceptional products and services that customers are willing and happy to buy and use.</p><p><a href="https://flic.kr/p/8VZw5L"><em>Image ©2007 Zion National Park</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52a88d285687" width="1" height="1" alt=""><hr><p><a href="https://medium.com/erratic-connections/why-invest-in-research-52a88d285687">Why Invest in Research?</a> was originally published in <a href="https://medium.com/erratic-connections">Erratic Connections</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>