When you’re a small business doing well with great walk-up business, who needs to bother with a website. Perfectly reasonable question; that is, until you get stuck with a stay-at-home order, your business is required to close, through no fault of your own and your walk-up business isn’t even able to leave the house.
Lansing small businesses need a website
Building a website, to most small business owners, seems like an unnecessary hassle. I’ve walked many small business owners through this process. I can make it easy, pain free and inexpensive. It doesn’t have to cost an arm and a leg to have a great website.
Lansing small businesses need a website because it can create an extra revenue stream.
A website used to be optional, in 1998, but many kept thinking right on through until the present day, that they were optional. A website is optional if income is optional. For my clients, income isn’t optional; a steady stream of income is critical, the most important thing after great service. Great service and income are hand-in-glove. An upset and financially strapped business owner isn’t going to have great service at the front of their mind.
A small business owner could have made a compelling case for not needing a website, until the stay-at-home order of March 24, 2020. Now, though, everything has changed. Websites, electronic services and email marketing are the basics for doing business in the isolation economy. You’ll note that I didn’t mention social channels like Facebook, Twitter, Snapchat, etc. Why? Because I’m getting increasing feedback that folk are terrified of what they’re reading on these social channels and don’t believe much of it anyway, so they’re staying away for their mental health. This creates an unprecedented opportunity for small businesses to connect one-on-one with their customers through their websites.
We would love to help you get your website and your electronic communications up and running.
With the first way you do research, build personas, do user interviews. You’re constantly testing, measuring and making adjustments. With this way, you know your users, your audience, your customers, etc… With this way, they use the design, and they appreciate the work you’re doing for them. They might even be extremely satisfied with your site, app or product and return time and again, with enthusiasm, because they know you care and are trying to make the most of their time.
User experience can go another way.
The second way is the one that has no design.
People need to use your site, app or product, but you do no research and give no consideration to the user; there are no personas, or user interviews. You don’t know your users, you underestimate them and you don’t value their time. You know that they can get the tasks done, because they’ve found workarounds, and for those that can’t, we chalk it up to “user error” and write it off.
Nobody wants to do it the second way, but sadly, this is still how many Lansing and Michigan organizations operate.
Because UX design puts users first, a time is coming when these kinds of organizations will be discarded. They will be moved to the margins, and eventually replaced entirely, by others that are more enthusiastic, more energetic and more service-oriented, in fact it’s already happening.
Which way do you want to take?
If you’re looking for the best way forward to put your users first and to integrate UX design into your organization, contact us today:
As a web designer working in Lansing for 20 years, I’ve been asked this question thousands of times. I’ve answered this question thousands of times. The answer isn’t usually very satisfying. It’s kind of like walking up to a comedian and saying: ‘Make me laugh.’ It doesn’t really work like that.
That’s why when I get the question: How much does a website cost?
I immediately begin asking my own questions:
Why do you you need a website?
What do you want to do with a website?
Do you have experience running a website?
Do you have content for a website?
Can you provide content for a website?
Generally, I don’t need much to get started. Usually, a high level vision or some sketches on a napkin will work. However, I always try to ask as many questions as possible to give my clients a sense of what’s involved.
Additionally, for many, web design is a creative, artistic endeavor meaning that the top priority is that it look good. “Good”, like beauty is in the eye of the beholder. As a website designer, my goal is to bring together form and function. I want to create something that looks great and works great.
Specifically, the 2 factors determining how much work is involved are the size and complexity of your site.
The two most important aspects to website cost are size and complexity. A good web designer, is going to get into this at the beginning. With a good understanding of size and complexity, you’ll have a strong foundation to work from to determine cost.
Website Design vs. Website Development
These terms are often used synonymously, but they’re two very different things. Website design is like working with an architect to create the blueprint for your house. Website development is like working with a contractor to actually build your house. The 2020 pricing estimates listed above are for website design *as well as* website development (i.e. the complete, all inclusive cost).
Website design and web development are different. These two disciplines often work together, but they require different skills, different tools and, arguably, a different sides of the brain. There is the rare creature that can do both well, but generally speaking, that’s not the case. Great designers are usually not great developers and vice versa.
The Shortcut To Building A Great Website
Creating a modern, professional website that generates leads and sales for your business is way more difficult and time-consuming than most people realize.
As Mark points out, building a website is more difficult and time-consuming than most people realize. For this reason, when I have a plumbing problem, I call a plumber. When I need electrical work, I call an electrician. In both instances, they can save you time, money and hassle because they’re experienced professionals who want to get the job done cleanly and quickly. Professional web design is no different.
If you’re thinking about creating a website and want to know how much a website costs, let me help you out. I work, individually, with all my clients, to figure out their needs, their goals and how to make it fit their budget. I’d love to learn more about your website needs and I’m happy to go over the cost with you, in person — Get in touch today:
UX design in Lansing is no different. UX design, or user experience design, isn’t particularly new, but it’s something that’s gotten buzzword status over the last few years, so design, and design-adjacent business, folks throw the term around a lot. That’s really too bad, because the UX design process is super useful; it focuses on user needs. And what’s the downside to focusing on the needs of the user?
User experience (UX) design is the process design teams use to create products that provide meaningful and relevant experiences to users. This involves the design of the entire process of acquiring and integrating the product, including aspects of branding, design, usability and function
Additionally, this diagram that shows the iterative process of UX design is pretty good, too:
I’ve been doing website design in Lansing for a long time. I’ve seen many trends come and go. Specifically, I remember spring 2007, when the iPhone was about to come out and I saw a bunch of people standing in line outside of a Sprint store across from the Lansing Mall. I won’t lie, this seemed a little crazy to me. I had already been through many Apple hype cycles and this seemed to be just another marketing scheme from the mind of Steve Jobs. It was, kind of, but also:
However, initially, folks didn’t know what to do with this technology.
Right around the same time a series of Apple ads began running with the tagline ‘there’s an app for that...’
See one of the original ads here:
Lansing’s 5-10 years behind
As with so many things, Apple was ahead of the curve and as one of Lansing premier design entrepreneurs once told me, ‘Lansing’s about 5-10 years behind the national trend.’ So, for website design, and it’s outgrowth, mobile design, that put Lansing like 10-15 years behind where Apple was.
‘Bummer…’ I remember thinking. But then, as now, he wasn’t wrong and Lansing website design and mobile development has been trying to catch up ever since.
See, nobody told Lansing that they were 5-10 years behind the national trends, so when people saw ads for apps, they wanted one. Those of us who were doing website design in Lansing at that time saw many apps come and go. That first wave, theVersion 1.0 app period, as I sometimes call it, generated a lot of money, a lot of hype and a lot of really useless apps. Version 1.0 of anything often suffers from this type of thing.
‘There’s an app for that’ became the new: ‘If you build it, they will come‘
As a proud skeptic, I steered many of my clients away from the money pit that was mobile app development at that time. Within a couple years, m-dot and then mobile responsive websites were able to do much of the work that apps had promised without the development cost. Also, there was no need to submit apps to a Google/Apple approval process and no need to maintain two different, independent codebases.
However, being skeptical wasn’t the big reason I steered a lot of folks away from apps. The real reasoning was that I knew their users would never use them, because through statistics and user research I could see that their users often didn’t have a user-base that possessed the technology to use a mobile app.
If, as your service provider, I know that something won’t get used because I have the data insight to prove it, I would be an unethical crook to take your money to create it. I want long-lasting relationships with my clients. I’m not looking for a quick pay-out and to move on to the next town. This is old fashioned, probably, but it’s very, very important to me. I want my website design clients in Lansing to be satisfied and well-informed.
And that gets us to the point of this article: Mobile development and design is expensive. Sometimes the expense is worth it, sometimes it’s not, but you won’t know until you do your user research. If your user research shows that there’s a hunger for an app, now you know, build on. If your user research says that they want a website for use over a slow rural DSL, build that. Either way – Start with user research.
What do you know about your users? Do you want to know more about your users. Please get in touch here. I’m fortunate to be one of a few website designers in Lansing who’s also experienced in leading and designing user research. Let me put my experience to work for you.
I love doing web design in Lansing. Many folks think of it as a creative act. On some level, that’s true. However, web design is all about meeting user needs. Non-profit associations have members, small businesses have customers and web designers have users; these are the groups that we aim to please with our work. Pleasing them comes in many forms: Great service, reliability, affordability, ease of use. It’s the last one that I want to talk about.
For years, ease of use, or what we know as ‘user friendly’ was hard to nail down. You knew it if you saw it, but you might not be able to explain it. Human-centered design, or user-centered design, as it’s sometimes known, gave us a guidebook to making websites that were easy to use. These days folks call this user experience design. Some use the terms web design, user experience design and UI (user interface) design interchangeably. Words matter, but what’s important is that we’re thinking about the user’s needs when doing web design.
For me, when I’m doing web design, I’m always thinking about the user and the user’s experience with the website I’m designing. Are they going to be seeing the website at their desk or on their mobile phone, are they older or younger? Users vary, as they do in most locations, but you can always count on a mix of ages, demographics, mobile and desktop users. My experience doing web design in Lansing has shown me that I have to aim for the middle: How can I create a great web design and user experience for all types of users?
This is where I practice user-centered design.
Here’s a diagram of how it works:
Is your Lansing web design firm focusing on user-centered design? Are your members, customers and users their focus when they’re doing web design for you? If not or you’re not sure, get in touch today. Your users are our #1 priority.
I’ve been doing web design in Lansing for over 20 years. I take a user-centered approach to all of my design work and that has allowed me to help many small businesses and non-profits realize the potential of their websites and their online presence. But what good is a great website if nobody can find it? By applying SEO-Search Engine Optimization best practices, I can help my clients improve their search engine rankings and their online visibility.
I’ve worked my entire career in Michigan’s capital city of Lansing. Because of this I’ve gotten to know the people, local vendors, what works, what doesn’t and how to keep things simple and moving forward.
Keeping a website current, fresh and relevant is my specialty. I have all kinds of tips and tricks for making a great website.
Over the years, I’ve worked on and created many kinds of websites, including:
Small Business Websites
Social Media Websites
Event and Event Registration Websites
Family Reunion Websites
If you’re looking for an honest and reliable web design partner to get your project off the ground, look no further. I love working on new websites, breathing new life into old ones and generally talking to folks about their web needs. Please contact me today about your web design needs.
Website design types vary, but in my 20 years of doing web design, I’ve worked on all of them. Blogs, eCommerce sites, event websites, online magazines, business websites, nonprofit websites, web forums, portfolio websites. You name it and I’ve probably worked on a few.
Because many of my clients are new to website design, I wanted to create a list of popular website designs. I don’t consider this an exhaustive list. However, 90% of my work falls into one of these categories.
The brochure-style website is the most popular style of website that I’ve worked on; think of this type of website as an online brochure or virtual business card. It’s usually short and to the point. This type of site is under ten pages and usually focuses on a product or service. Typically, you can make contact via the website, learn about hours and locations. I include restaurants, auto repair shops and other ‘mainstreet’ businesses in this category. I also call this style of website design “brochureware”.
Informational (Small Business and Non-profit) Website
The informational website design is for small businesses and non-profits. While this website design is similar to the brochure style it contains more information. This website could include information around bylaws, financials, organizational mission, vision, locations and ways to connect with officers and staff. This website design is kind of like a grown-up brochure website; more responsibilities and user needs to serve.
The eCommerce website can be standalone like Amazon or eBay or it can be integrated into larger informational website. For instance, a small business website for a restaurant might also have eCommerce functionality to purchase gift cards. A non-profit website might sell things related to their mission, such as a construction safety organization that also sells discounted safety equipment to its members. The eCommerce website style varies, but it’s always transactional with the buying or selling of goods and services as its core call-to-action.
Event and Event Registration Website
At the intersection of the eCommerce and informational website is the event and event registration website. I think of the event website design as one that showcases events and provides a way to register online. Event websites can be standalone such as for music festivals or religious gatherings. I’ve also integrated event websites into eCommerce and informational websites. For example, a small business could sell trainings, where a user could register to attend. A non-profit might hold retreats or seminars where a user can register and buy tickets online.
Blog/Online Magazine/Content Website
The blog, online magazine or content website(i.e. Vice, YouTube or Pinterest) is designed for users to engage and interact with content. Content takes many forms: Watching funny cat videos, looking at retro interior design photos, reading about putting Ikea furniture together or just the daily news. These are the oldest kinds of websites: People going online expressing their views, perspectives and life experiences and sharing them with others. These types of sites have been around for a long time, but they haven’t changed. ‘Content is King’ and creating fresh content is central to getting website visits and good search rankings.
That’s it, in a nutshell.
When I work on a website design, the goal is always the same: Help the user complete a task quickly. In order to help the user, you have to understand the user and which kinds of website designs work best.
Jonathan Walter has written a great article, Navigating Ambiguity, at UX Matters. It’s part of a series of columns that focuses on enterprise UX, or as he puts it ‘designing experiences for people at work’ – That’s what drew me in, initially because there’s much written about new development and design from a UX perspective, but enterprise work is often the overlooked and neglected ‘other’ that’s not considered very glamorous and doesn’t get the attention it deserves where UX is concerned.
As I began reading the article, thought, I realized that he was a kindred spirit of sorts, because I use the phrases: “Navigating ambiguity” or in jest, “parsing the nebula” just about every day when solving problems with digital experience and software functionality development, roadmapping, etc. We, individually, and as a team, have to understand what we’re trying to do before we can map it, plan it, work on it, but particularly, deliver it. Jonathan provides some great insights on that.
Get comfortable with not knowing everything
“Even in situations in which you feel alone in your lack of knowledge, you must become comfortable with saying, “I don’t know.” In his Forbes article, “The Power of Saying ‘I Don’t Know’,” Gaurav Gupta states: “We are conditioned to having and providing quick, confident answers as a sign of competence and leadership. We behave as though any gaps in knowledge should be hidden at all cost. But is this desire to have an answer—and have it quickly—actually helping you? How often do we trade factual accuracy and thoughtfulness for immediacy? Why do people find it so hard to say, ‘I don’t know’?”
Ask (the right) questions
I would say, just ask question, as you don’t know what you don’t know. It’s a journey of a thousand miles, start with one step. Additionally, Jonathan adds:
“…ask the following W questions to reduce ambiguity and approach a problem from a higher-level perspective:
What problems does this product or capability solve?
Who will use it?
Why will they use it?
When or in which context will they use it?
“…Once you understand this high-level information, you can ask progressively more specific questions.”
Provide a vision
This has been hugely important for me. I never had any idea how often I’d have to repeat, dramatize, articulate and visually represent my vision for product or experience. Jonathan puts a finer point on this that I really appreciate:
“…your vision—even if it is overly aspirational or flawed—provides a North Star that product-team members can keep in sight as they develop a product. It can also serve as a useful artifact for identifying which features are in scope for early releases and which you should defer to later releases.
“Just take care to avoid leading stakeholders to believe that the vision is final.”
I’ve only scratched the surface on Jonathan’s great article, but I highly recommend you give it a read; if you’re interested in UX and process, you won’t be disappointed and the information is as practical and steeped in experience as it is easy to understand and put into practice. Again, you can find that article here.
Great article here that makes a clean and straight forward explanation of the difference between UI, UX and the role that you’re Lansing web design professional should be considering when working on your website.
“Simply put, UI is how things look, UX is how things work. UX is a process, while UI is a deliverable.”
Agile Software Testing and Development Talk at Techsmith with Pam Weil and Mark V. Alexander of Techsmith from October 2017 as part of the MMUG – Mid-Michigan Agile Group and LAST – Lansing Area Software Testers… This event took place at the Techsmith headquarters…
“Put it in the backlog and we’ll get back to it (never)”
Sadly, Guy’s not far from the mark. Frequently what goes into the backlog just doesn’t get revisited, mostly because it’s the non-priority, non-MVP (minimum viable product) options that get left behind (See the ‘Backlog Iceberg’ above). Movie editors will talk about losing parts of a story to the cutting room floor; Product manager’s lose stuff that isn’t a priority in the backlog. Backlogs are intended to be living and breathing documents that, especially during the critical start up phase, get much attention, but as market priorities shift, new products are released and organizational focuses evolve, older but not less useful backlog items get neglected. More than once, even right now as I type these lines, I can think of great functionality and features that didn’t make it into a releases I had hoped… the ones that got away… Well, maybe not ‘got away’ because as a Product Manager you have to hold on to those ideas, functionality and features for the right time.
Guy further writes:
“We hear lots about doing the best for the customer and in lots of cases we do, at first. The problem lies when we don’t get back to iterating on designs when delivering becomes more important…”
Again, Guy’s not wrong. As a product manager, you have to always be on your toes — Thinking, grooming and prepping the backlog, because iterations and sprints move quickly and they won’t wait for you. Nailing your cadence, watching the team’s velocity, negotiating stories, etc. are all the things that will keep you prepped and ready to hand off wishlist features and functionality that might not have made it into to early releases. If used consistently, the backlog can be the product manager’s best friend. If we’re doing our jobs as product manager’s well, there will be very few features that ‘got away’…
As far as web design in Lansing goes, I consider myself one of the most vocal advocates for user experience design. When I saw Ian Armstrong’s article on the evolution of UX, I was sure that other folks doing web design in Lansing would want to learn more – Check out Ian’s article here. Additionally, I will add a few of my own points based on my reading of the article, but a full read is a must.
Ian states that “in its purest form, UX Design is waterfall based.” These days, in most circles where folks are talking about UX, ‘waterfall’ is a dirty word that hearkens back to rigid PMBOK processes and exhaustingly long requirements gathering sessions, but Ian’s absolutely right. You have to get a sense of requirements, gather perspectives, mock things up, test out assumptions, wash, rinse, repeat. It’s waterfall. There’s no way around it.
Ian nails one of the key problems with being outcome based, what we work towards with agile vs. requirements based. This is a conundrum that many of have faced and still work to reconcile: “Whereas classic UX is requirements based, Lean UX is outcome based… Designers found themselves under immense pressure to fill a sprint backlog before they really understood what they were building. As a result, a lot of development cycles got burned on features that never made it into the final product.”
So much development and rework lost trying to anticipate product needs… <sigh>
I’ve read a lot about the Google Ventures Design Sprint, and attended a session at an O’Reilly Design conference where they talked about it, but even then, Ian’s explanation is as succinct and spot-on as any I’ve come across:
“Google Ventures conceived the design sprint, which allowed teams to rapidly define and test a low-fidelity prototypes. This jump-started the Lean UX cycle on emerging product teams and effectively eliminated the waste and rework problem.”
I’ll put a pin it there. Check out Ian’s original article.
If you’re looking for web design in Lansing that puts your user’s experience at the center of their work, then get in touch today.
“…We need more product thinking, and less product managing.
You don’t need a product manager to:
“Get work done”, and keep the team focused
Manage projects, and give status updates
Manage a team, and advocate for the team
Have “accountability” for shipping features/projects
Facilitate standups, planning meetings, and retrospectives
Talk to customers and users
Measure the impact of work, and design experiments
Write user stories and requirements
Test work with customers and users
We have roles (hats) for these things: project managers, UX, researchers, data scientists, business analysts, team managers, coaches, etc. Do product managers often wear these hats? Sure. Do you need a product manager to wear these hats? No.”
John’s exactly right.
We have roles for these things, for these many and varied disciplines. Of course, especially in the beginning, there’s usually one evangelist wearing a lot of these hats, but as an organization matures towards a product-centric approach, the role typically known as the product manager, rather organically, becomes that of the product thinker. I’m confident that, in time, the natural evolution that brings together, seemingly disparate, disciplines like UX, IT and business needs will be thought of as a whole instead of separate parts. This is the natural outcome of truly undergoing a digital transformation. That evolution is happening, albeit slowly outside of software development organizations, but it is happening.
Some may find this controversial, disagree or just find it to be utter rubbish, but I believe, in the venn diagram of product management, it’s the background in user experience that truly makes the best product manager. I believe that in time, it will be UXers and UX designers or folks who came up through design that will eventually come to be the best product managers. You can have an understanding of the business. You can have an understanding of the IT. In both of those cases you’re removed from what the user are looking for and what they’re hoping to achieve with the product, and focused on the other facets of the respective discipline.
I also believe that there will be a time, when those designers have to tuck their design experience in their back pocket (design and UX thinking are likely second nature at this point or maybe that was just the case for me) and start to learn about the business and the technical aspects. This pivot is the thing that will leave some designers disinterested, some may even find it unsavory, and because of that I think that many designers will stick with their respective discipline of design, but for those who have that broad-ranging curiosity about all of the moving parts of their product I think it will be the UXer/designer that will be the discipline to lead product management.
Sounds like he works in a very empowered environment…
In my experience, I have found that a point person is required to manage the process, to play the roles of mediator between ‘tech’ and ‘leadership’, explaining ‘impact’ and budgetary concern in both directions –Providing the information each needs to integrate and inform decisions on moving forward; this is in addition to playing the ‘operational’ role of supporting and monitoring the structured change processes required to maintain the production environment, while facilitating the integration and mediation of customer ‘wants’ by managing expectations of internal and external customers. This must be done by providing meaningful information, this becomes the corner stone of future success.
High quality requires support from all sides, that is gained by gathering input from all stakeholders and providing the information each needs in a way that they can use…
No easy task, but when it is humming, there is nothing better.
Radical / disruptive innovation is high risk and it has a high likelihood of generating black swans. Continuity and disruptive event planning and response work is many and varied and involves every aspect of a service. The up side is that the work returns value daily to the customer, the work place and to the bottom line. An article from the Incremental Innovation team elaborates on this further.
So you’re organization wants to get started with UX? Maybe your CMO heard about it at a buzzword-filled session at some marketing conference or as a designer you’re tired of designing, by committee, things that don’t meet user’s needs, or maybe, you’re somewhere in between? Whatever the case, you’ve found yourself at the front lines of advocating for this new approach and all that comes with that. Ok. So do you want the good news or the bad news first?
Alright. Like me, you like to get that out of the way. Understood.
The bad news is that it’s going to take a lot of time, a lot of passion and a lot of energy. However, you might also find yourself here, because I learned that I liked promoting and talking about UX as much as I liked sitting down with a Brian Eno/Harold Budd record and a hot cup of Kona blend to design (actually, maybe even a little more).
The good news is actually pretty great news.
UX has a value proposition that’s pretty hard to argue with, at even the most change-averse organizations.
As with everything, though, there’s a balance. How do you evangelize for the value of UX without overwhelming the organization?
With all of the day-to-day activities it can be hard to introduce new processes, especially if an organization doesn’t think that there are any issues with the current processes and it looks like you’re adding a greater degree of complexity for no apparent value. No worries, but do keep this in mind: Organizations, like people, generally resist change, so like with any kind of change, the less scary you can make something, the better.
Before doing anything with UX you have to establish what the problem is. And even though, you, as a designer, are most familiar with the users, and most sympathetic to their needs, and all of your education and experience tells you what the problem is, you have to make the adoption of UX, not about your opinion, or your feelings, but about user problems based on usage data.
Hopefully, you’ve been tracking stuff with Google Analytics, or an occasional survey or maybe some other voice-of-customer feedback tool; if not, no problem, there are a variety of tools you can use to get started. A few examples are: Google Analytics, GoogleDrive surveys, do-it-yourself user interviews, and A/B tests based on paper prototypes. These are quick and dirty ways to begin collecting data on your users, but usually, it doesn’t take a ton of data to begin to see issues, patterns and the areas of discontent for users. Start collecting the data.
Now that you have some usage data it’s time to highlight the issues and to talk about the solution, which is building the UX discipline into your organization.
Evangelizing for UX in organizations that already understand it and think it makes a lot of sense are not really the target audience here, so we’re going to focus on the other kind: The organization that doesn’t understand UX and finds any kind of operational change suspect.
Getting an organization interested in UX is a journey of a thousand miles, with each conversation about user data, each shared interaction on user pain and each reference to the concept of ‘user experience’ being a single step. For my mind, the slow-grow approach of evangelizing for UX is the only way, because an organization that goes too fast will get operational whiplash. We don’t want that.
As I stated at the outset, UX creates a value proposition that’s hard to argue with, but people don’t know what they don’t know, and it’s your job to teach them.
With that said, some folks will still try to argue the value of UX. You’ll hear things like “Why would we do this? The users are happy.” Or, “the users don’t care.” Or, perhaps, my favorite “This is the way we’ve always done it, why should we change?” These are not qualitative arguments, these are barely opinions, mostly they’re smokescreens meant to discourage you. Don’t be discouraged. You have your data, you know where the users are struggling and best of all you have a solution to fix it.
Often, there’s the question of where one should start with UX and I believe that you should start right where you’re at.
First and foremost, you can talk a lot about UX, but if you can show the results that’s even better… as the saying goes, ‘show, don’t tell.’ Look at ways to integrate paper prototypes into design discussions. Conduct A/B tests internally with fellow employees and organizational leaders. Use low-res mock-ups or wireframes and talk through the interactions. Getting started with UX can be very low-tech and yield incredibly satisfying results, as well as creating positive experiences/stories that will be shared throughout the organization.
At work here, also, is the idea of creating ambassadors for organizational change. I originally heard Eric Quint, Chief Design Officer of 3M talk about this at an O’Reilly Design Conference and it really stuck with me.
The idea is this: The square root of an organization’s employees equals the number of ambassadors needed for organizational transformation. So, if you have 1,000 employees, then you need 31 ambassadors/influencers talking about an idea to effect organizational change. While I never heard of an equation for organizational transformation put just this way, it’s darn accurate in my experience.
The funny thing about the actual practice of UX is that somewhere between getting started, unofficially, just to ‘see how it works’ and full-blown processes being established the discipline of UX takes root. I’m sure it could go the other way, but that’s just never been the case for me. When organizations start to see the positive results of UX and the empathic consideration of a user perspective, it’s as if some area of our lizard brain is triggered, with even those most opposed to the change, getting involved in serving the user. It’s radical and adoption of UX slowly takes hold.
I’m sure there are other, top-down ways to introduce UX. There can be mandates given and directives written, but UX, like any organizational change works best if it happens organically. Whether we’re talking UX or picking a new office supplies vendor, there are varying levels of awareness, acceptance and adoption. In this regard, organizational change works best through gradual repetition and iteration. The worst thing that can happen is that an organization gets overwhelmed by change, UX or otherwise. UX can be a lot of fun, and mostly, folks want to help one another, the user-centered perspective of UX makes it a great practice, not just for making better products, but for bringing people together to solve a common problem.
Collect usage data (web analytics, DIY surveys, voice-of-customer feedback)
Show, don’t tell whenever possible
Have fun spreading the word of UX with fun exercises
It’s probably because it’s something I do everyday. I don’t think much about it. Or, maybe, I don’t want to think much about it, because day in, day out, it’s where my focus is. However, I do think that it’s supremely important… I’m talking about integrating UX into agile.
One day I’ll probably write a book about it. I love giving practical advice and sharing my experiences, in fact, that’s one of things about agile that I really love, the community-based, open source aspect of the community around agile. Whether you’re looking at scrum, kanban, scrumban, or something else, agile is a great way of working with your development team and it’s also excellently positioned to take advantage of UX practices.
…most teams don’t conduct user research on a consistent basis, if at all. People cite tight deadlines and staffing shortages as reasons for deficiencies in user-centered activities.
Research and user testing are two areas that are very difficult to integrate into agile UX. Lean UX, on the other hand, considers this, and in some ways is really an agile UX 2.0. This is important, because the need for that research and testing to happen in real time is super important to the ongoing design and development process. Unlike a waterfall approach, there usually haven’t been requirements or JAD (joint application design) meetings; instead, you start with a basic road map, some use-cases, a couple user stories and get to work. Lean UX thrives in this situation.
Ok, I say, Lean UX thrives… yes, that’s true, BUT… teams have to get used to working with one another and they have to round off the rough edges and bad habits, whether of the development or the interpersonal variety. Lean UX and agile don’t leave a lot of margin for getting mired in unnecessary details and some of the interpersonal issues that may pop up when a team is just getting started. Nevertheless, when it comes together, and when the gelling starts, the team’s pace and work can be exceptional!
I find Lean UX or the idea of UX that can work at the speed of agile to be very exciting, especially if you’ve ever been involved in a waterfall development project or something that was just slow moving. Lean UX and agile are the one-two punch to quickly knock out great work!