<?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[Stories by Todd Zeigler on Medium]]></title>
        <description><![CDATA[Stories by Todd Zeigler on Medium]]></description>
        <link>https://medium.com/@toddzeigler?source=rss-7fa631982c8d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_txszP8_erkTzv54.jpg</url>
            <title>Stories by Todd Zeigler on Medium</title>
            <link>https://medium.com/@toddzeigler?source=rss-7fa631982c8d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:24:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@toddzeigler/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to create a members only section people will actually use]]></title>
            <link>https://medium.com/@toddzeigler/how-to-create-a-members-only-section-people-will-actually-use-197eb5910178?source=rss-7fa631982c8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/197eb5910178</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[nonprofit]]></category>
            <category><![CDATA[membership-sites]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Todd Zeigler]]></dc:creator>
            <pubDate>Wed, 24 Aug 2016 13:26:39 GMT</pubDate>
            <atom:updated>2016-08-24T13:26:39.598Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NBtddL_fIUShV1CanBfkWQ.jpeg" /></figure><p>If you work at a membership-based organization such as a professional society, trade association or nonprofit, the situation below may sound familiar:</p><blockquote><em>Your members have periodically asked you to provide them with ways to collaborate with each other. You decide to act on the request and build a new members only section on your website with frequently requested features such as a member directory, member profiles, message boards, group chat and document library. You launch the new section and get good initial feedback. But after a few weeks it becomes clear that no one is using the new tools and after a few few months it is a complete ghost town.</em></blockquote><p>You bought the groceries and cooked the meal, but no one is coming for dinner.</p><p>In my experience, this is the rule rather than the exception. The features that sound the most exciting in theory are often quite different from the ones members will actually use on a daily basis. Perhaps more importantly, your member’s only section is competing for attention against the likes of Facebook, Slack, LinkedIn and Pokemon Go. Getting people to make your site a part of their daily or weekly routine is a tough ask.</p><p>To help prevent you from wasting blood, sweat and tears building something no one will use, below are some lessons I’ve learned building members only sections for clients.</p><p><strong>(1) Listen to your members</strong></p><p>A lot of expensive and unneeded features that get included in members only sections are the result of anecdotal requests (“Board Member A thinks Feature X would be really cool”) and/or poorly constructed membership surveys. Asking members what features they want is a vital part of the planning process, but you have to ask the right way. You need the right mix of quantitative and qualitative research.</p><p>Don’t just send an open ended email survey asking members what features they would like to see. Instead, develop a list of features you are thinking of adding and ask members to rank them in order of importance and/or to tell you how often they would use each of them. You need to a way to prioritize features into “must” and “nice to” haves.</p><p>Be sure to send the survey to all your members, and not just a small subsection. The needs of your most involved members are going to be different from those who are less active. Don’t let the loudest voices drive your development priorities.</p><p>Lastly, supplement the email survey data with qualitative research. Interview a few members over the phone or in person to get a sense of how they are using your current members only section (if you have one) and/or how they would use the new features you are contemplating. Interview members from a variety of backgrounds and engagement levels. These interviews can be really helpful in understanding how members actually use your site and fine tuning requirements.</p><p><strong>(2) Don’t recreate Facebook and LinkedIn</strong></p><p>I have worked with a lot of clients who want to build advanced social networking functionality into their members-only site. They basically want to create a “private” LinkedIn or Facebook for their organization, with groups, status updates, chat, message boards, etc.</p><p>In my experience this approach is nearly always a mistake. These types of social features sound cutting edge and exciting, but are rarely used in the context of a members only section. Most of your members aren’t going to spend enough time on your site to support features like chat or message boards.</p><p>If you do want to experiment with social features, a better approach is to try to leverage social networks your members are already using. Start a private group on <a href="http://www.linkedin.com/">LinkedIn</a> or <a href="http://www.facebook.com/">Facebook</a>. Experiment with <a href="https://slack.com/">Slack</a>. Start an email discussion list. These tools are more cost effective and likely to success than trying to build your own walled garden on your site.</p><p>Fish where fish are.</p><p><strong>(3) Start small and expand</strong></p><p>In software development, “the <a href="https://en.wikipedia.org/wiki/Minimum_viable_product">minimum viable product</a> (MVP) is a product with just enough features to gather validated learning about the product and its continued development.” In the context of a members only section, the MVP should consist only of the “must have” features you and your members have identified. Start out by building just these features and then expand later based on your site analytics and member feedback. This approach allows you to move quickly, and saves you time and money that might have been spent building features people won’t actually use.</p><p>As an example, we recently built out a members-only section for a professional society. They started out with a long list of feature requests that included expensive social features. After research and a series of discussions, their MVP consisted of the following features:</p><ul><li>User accounts for members with different permissions based on membership level.</li><li>Members-only document library</li><li>Listing of members-only events and continued learning opportunities</li><li>Access to proprietary database showing overall industry trends</li><li>A really good search of all the members-only materials.</li></ul><p>The professional society had a wealth of proprietary content that their members rely on in their day-to-day work. Providing their members with a way to quickly and easily access this content was far and away the most important feature for the new members only section. So for phase one of the project, we focused on doing that one thing really, really well. We focused on the area where the professional society could provide its members with real value.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=197eb5910178" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to avoid three common project management pitfalls]]></title>
            <link>https://medium.com/@toddzeigler/how-to-avoid-three-common-project-management-pitfalls-37b729ae4922?source=rss-7fa631982c8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/37b729ae4922</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[discovery]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[planning]]></category>
            <dc:creator><![CDATA[Todd Zeigler]]></dc:creator>
            <pubDate>Wed, 17 Aug 2016 21:19:46 GMT</pubDate>
            <atom:updated>2016-08-17T21:21:15.964Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jldW7A75tUvdfOkAoS8e5w.jpeg" /></figure><p>A few weeks ago I <a href="http://blog.thebrickfactory.com/2016/08/empathy-project-management/">wrote a post</a> about how important it is for project and account managers at web development firms to have empathy. If you are able to see the world as your client does, chances are you are going to do a great job for them. You will be able to anticipate problems before they happen.</p><p>As a follow up, I wanted to share some real-world examples of client communication problems we’ve run into at the Brick Factory and explain how they could have been prevented. The underlying theme is that most issues can be prevented with good communication that comes from understanding.</p><h3>(1) Hidden Requirements</h3><p><strong>Project management problem</strong></p><p>You have been working on a site redesign project for three months and are a week from launch. While reviewing the beta version of the site, the client points out that a members-only section that was present on their old site is missing and must be built prior to launch. This is the first you have heard of this feature. Your launch date is now in peril and you have to have a difficult conversation with the client since the work isn’t in your original Scope of Work.</p><p><strong>How it could have been prevented</strong></p><p>No matter what project management methodology you use (Agile, Waterfall, etc.) or how small a project is, every engagement should begin with a discovery phase aimed at surfacing requirements. Write out the features and functionality of the site/feature you are building and get the client to review and approve to make sure nothing is missing.</p><p>Skipping the discovery phase is sort of like heading out on a cross country, family road trip without a map or GPS. You will probably get there eventually, but it is going to take a long time and there will probably be tears.</p><h3>(2) Misinterpreted Designs</h3><p><strong>Project management problem</strong></p><p>Your team has produced a series of design comps for a new site that you are ready to show the client for the first time. Language and photography are still being finalized, so you use placeholders in the initial comp. You send the client the designs via email and don’t hear back for a week. When they finally do get back to you most of the feedback is on the placeholder images and text, and it becomes clear that the client is confused by parts of the interface. You are able to clear up the confusion with a phone call, but you have wasted a week.</p><p><strong>How it could have been prevented</strong></p><p>This one is pretty simple: you should always present your first big design deliverable either in person or via a screen sharing service where you can control the experience. You should only send a link to the design after you have presented the work first.</p><p>By presenting the work you are able to explain the decisions you made, fully demo how the interface works and clearly define what kind of feedback you are looking for. It gives you the opportunity to make sure your work is properly understood. No matter how thorough or well written an explanatory email, it can’t take the place of a conversation.</p><h3>(3) Misunderstood Deliverables</h3><p><strong>Project management problem</strong></p><p>You create a series of wireframes for a new website you are building. The wireframes are in black and white, and intended to demonstrate overall page structure and content priorities. After sending the wires to the client, you get a short response asking why the new site design is completely black and white.</p><p>Later on in the project, you send the client a complete, full color design comp that is in PSD format and optimized for widescreen desktop computers. The comp is posted in <a href="https://www.invisionapp.com/">Invision</a> so that the client can see what it will look like in a browser and provide feedback before you build it out in HTML/CSS/JS. The client calls you five minutes after receiving the comp in a panic, asking why the new site draft doesn’t work on mobile phones.</p><p><strong>How it could have been prevented</strong></p><p>In both of these scenarios the client misunderstood the deliverable you sent. In the first scenario they thought the wireframe was a full site design and in the second scenario they thought the design comp was a full working site draft.</p><p>If you are like us, your clients are smart people who are true experts at their jobs. But for a lot of them web development isn’t their primary job. They count on us to walk them through the process of building a site. It is a mistake for us to assume that all of our clients know what things like wireframes, design comps, mood boards, prototypes, etc. are.</p><p>One of the first things a project manager should do when onboarding a new client is explain the process that will be used to build the new site or feature. Walk them through each of the deliverables you are going to produce in detail, explaining what they are for, what their limitations are and what type of feedback you are looking for. I know this sounds obvious, but I personally have skipped this step and ended up confusing the client more times than I care to admit.</p><p><em>This post originally appeared on our </em><a href="http://blog.thebrickfactory.com/2016/08/three-common-project-management-problems/"><em>Brick Factory company blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37b729ae4922" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Empathy: a project manager’s secret weapon]]></title>
            <link>https://medium.com/@toddzeigler/empathy-a-project-managers-secret-weapon-8f64b81665a7?source=rss-7fa631982c8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f64b81665a7</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[empathy]]></category>
            <dc:creator><![CDATA[Todd Zeigler]]></dc:creator>
            <pubDate>Wed, 03 Aug 2016 21:54:54 GMT</pubDate>
            <atom:updated>2016-08-03T21:54:54.736Z</atom:updated>
            <content:encoded><![CDATA[<p>Our <a href="http://www.thebrickfactory.com/">Brick Factory</a> team recently <a href="http://blog.thebrickfactory.com/2016/05/our-new-digs/">moved into a new office</a> in the McPherson Square area of Washington, DC. Our new space was previously occupied by a law firm with an affinity for wood paneling, ship drawings and 80s style carpet. Thankfully, as part of our lease we were given the opportunity to completely gut the space and rebuild to our exact specification. This involved a pretty extensive construction project with deadlines, budgets and a team of contractors. As the client on the project, my job was to oversee the process and to make a million small and large decisions.</p><p>I had never been involved in a construction project before and it was quite a trip. I pretty much felt confused and incompetent the entire time. I didn’t know speak the language or truly understand the process. I asked many, many stupid questions and had to have things explained to me 2–3 times before I was able to “get it”. I lived in fear that I would make an expensive mistake. Despite my extremely shaky performance, the new office turned out great due to the wonderful job done by the team we worked with.</p><p>Managing the construction of our new office increased my appreciation for our clients. Being the client is hard. By playing the role, I was able to gain a greater understanding of the stress and emotions our clients feel when working with us on web development projects.</p><p>At the <a href="http://www.thebrickfactory.com/">Brick Factory</a> our clients are smart, busy people who spend their days fighting important policy battles, running successful businesses and/or trying to make the world a better place. Their jobs or hard and stressful, with deadlines and goals they rely on us to help them meet. While the web is critical to what they do, building websites is rarely their primary job and not all of them have a deep understanding of the web development process.</p><p>In order to do right by your client, I think one of the most important traits you can have is empathy. There is a lot of good content on the web about empathy (go watch <a href="https://www.youtube.com/watch?v=1Evwgu369Jw">this video</a> right now), but this definition sums it up pretty well:</p><blockquote><em>The ability to step into the shoes of another person, aiming to understand their feelings and perspectives, and to use that understanding to guide our actions.</em></blockquote><p>If you think about it, that is a pretty good description of what a project manager does. If you are able to see the world as your client does, chances are you are going to do a great job for them. You will have a deep understanding of their needs, and will be able to prevent most problems and resolve the ones that do pop up quickly and amicably.</p><p>While certainly incomplete, to be an empathetic project manager you have to do the following:</p><ul><li><em>Understand your client’s background and experience level</em>. The way you work with a client that is managing their first web development project is going to be fundamentally different from a client with a wealth of experience. Understand your client’s experience level and adjust your process accordingly.</li><li><em>Know how your client likes to work</em>. Some clients want to be involved in every decision while others want to provide overall direction and let you handle the details. Sometimes it is a mistake to ask for feedback too often. Other times it is a mistake to not ask often enough. If you understand your client you’ll know what to do.</li><li><em>Get to know your client’s company culture</em>. Is the organization fast paced or laid back? Who does your client contact report to? Does your client email you late or night or just during the business day? Understanding the environment your client is working in will help you provide them with better service.</li><li><em>Understand what is keeping your client awake at night. </em>Is there a big conference they are preparing for? A vote on a big bill that is fast approaching? A fundraising number they need to hit? If you truly understand the client’s pain points you’ll be able to provide better counsel.</li><li><em>Always figure out the “why” behind a request</em>. As a project manager you have undoubtedly received an out-of-the blue request to move a deadline or to implement a new feature ASAP. Take the time to understand the context. This will allow you to distill the request down to its core, providing you the information you need to solve the problem.</li><li><em>Actually talk to your client now and then</em>. A lot of work today is done via emails and collaboration tools such as Basecamp. Make the time to talk to your client on the phone and/or in person now and then. You will undoubtedly learn something you wouldn’t have known if you’d stuck exclusively to electronic communication. This will build connection and understanding.</li></ul><p>When you are a project manager at a web development firm, it is very easy to turn into a robot programmed to complete tasks as quickly and efficiently as possible. But being able to put yourself in the client’s shoes is just as important as efficiency. Indeed, empathy is often the difference between a great project manager and one that is merely good.</p><p><em>Originally published on our </em><a href="http://blog.thebrickfactory.com/2016/08/empathy-project-management/"><em>Brick Factory company blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f64b81665a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We Built It: International Youth Foundation Annual Report]]></title>
            <link>https://medium.com/@toddzeigler/how-we-built-it-international-youth-foundation-annual-report-ac0628a14095?source=rss-7fa631982c8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac0628a14095</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Todd Zeigler]]></dc:creator>
            <pubDate>Thu, 14 Jul 2016 15:19:44 GMT</pubDate>
            <atom:updated>2016-07-14T15:24:55.974Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7pujXlRhxNJ4zaAN8BqLPg.png" /></figure><p>A few weeks ago I <a href="http://blog.thebrickfactory.com/2016/06/designing-systems-instead-of-pages/">wrote a post</a> about changes we have made to our Brick Factory design process over the last few years. Check out the <a href="http://blog.thebrickfactory.com/2016/06/designing-systems-instead-of-pages/">full piece</a> if you have time, but the gist is that we have moved away from designing pages and towards creating systems. We are trying to design overall styles and repeating elements that make up the pages, instead of the pages themselves.</p><p>Showing is always better than telling, so I wanted to write a follow up post using the <a href="http://www.iyfnet.org/annual-report/2015/">Annual Report micro-site</a> we built for the <a href="http://www.iyfnet.org/">International Youth Foundation</a> as an example. What follows is an explanation of our design and build process for the project, with actual deliverables included to make things more concrete.</p><p><a href="http://www.iyfnet.org/">The International Youth Foundation</a> (IYF) works around the world to ensure youth develop the leadership, technical and life skills to earn a livelihood. A long-time client, IYF hired the Brick Factory to build a micro-site for their 2015 Annual Report. The project had a tight, one-month timeline.</p><h3>Deliverable One: Wireframe and Mood Board</h3><p>IYF planned to draft all report content themselves, and provided us sample copy and photos during our initial kick off discussion. The actual, final copy wouldn’t be ready until about halfway through the project. Given the tight timeline, we wanted our initial design deliverables to achieve two overall goals:</p><ol><li>Clearly communicate our overall approach to project.</li><li>Define the visual style (colors, typography, etc.) for the piece.</li></ol><p>We decided to provide a wireframe to demonstrate our approach and a mood board and section cover concepts to show visual style.</p><h3>Wireframes</h3><p>We recommended the Annual Report be built as a micro-site with links throughout to content to the main IYF website. To demonstrate the approach and the content structure for the site, we created wireframes for the <a href="https://invis.io/677X8AZCK#/173123916_Wireframe_-_Full_Report">main site page</a> and the <a href="https://invis.io/677X8AZCK#/173123935_Wireframe_-_Menu">menu system</a>. These wires essentially functioned as a visual outline of the micro-site. Here is a screenshot from the site wire.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jh9yN63knEZhmTCJ.png" /></figure><h3>Defining Visual Style</h3><p>Defining palette and typography is a critical part of any project. We have found mood boards to be a useful way to start thinking about look and feel prior to producing full design compositions. For the Annual Report, we created a relatively <a href="https://invis.io/677X8AZCK#/173137273_Mood_Board">simple mood board</a> that provided a few different font and color options for IYF to react to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/0*iLXqz0ZHaZbxZ7h2.png" /></figure><p>In light of the tight timeframe, in addition to the mood board we also produced a few design options (<a href="https://invis.io/677X8AZCK#/173137496_Cover_Option_1">1</a>, <a href="https://invis.io/677X8AZCK#/173137497_Cover_Option_2">2</a>, <a href="https://invis.io/677X8AZCK#/173137498_Cover_Option_3">3</a>) showing the introduction area of the annual report. With some minor tweaks, option one eventually became the introduction to the site. Here is a screenshot of the original report comp.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hBZZzlgpc86Pe-0l.png" /></figure><h3>Deliverable Two: Site Components</h3><p>The client provided quick feedback on our initial wireframes, mood board and cover page comps. After a round of edits, we got approval to move forward with our next set of design work.</p><p>While the report consisted of six sections and was pretty long, the content of each section was consistent in approach and style. Given that, as a next step we decided to further explore the design by producing comps of a few of the components that would be repeated throughout the piece. We produced a second version of the <a href="https://invis.io/677X8AZCK#/173143059_Cover_Round_2">overall site cover</a>, a design for the <a href="https://invis.io/677X8AZCK#/173143058_Menu_System">menu system</a>, a <a href="https://invis.io/677X8AZCK#/173143056_Section_Cover">section cover</a> (pictured below) and <a href="https://invis.io/677X8AZCK#/173143057_Text_Presentation">a presentation style for text and links</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2peSKfLO0OApRmlB.png" /></figure><p>The goal of this round was to simultaneously confirm with the client that the visual style we had developed was correct and to further build out the style guide for our internal implementation team.</p><h3>Deliverable Three: HTML Prototype</h3><p>After receiving feedback and approval on the component comps, we we put together a working prototype of the report introduction section, which represented about 20% of the full site. There were a few reasons we wanted to produce a working prototype as opposed to more static comps:</p><ul><li>We envisioned the piece having a series of animations and transitions. This sort of interactivity is much easier to show in working HTML than in static comps.</li><li>We wanted to quickly show the client what the site would look like on mobile phones and tablets without doing a million comps at each screen size.</li><li>Assuming the prototype was on track, we intended to reuse the HTML/CSS we developed for the actual site. Building the prototype would give us a head start on the project and allow us to move quickly once the content came in.</li><li>By giving IYF an idea of how the website would actually function in browsers early in the process, we would be able to identity problems before it was too late. If there was a disconnect with IYF, better to know early than a few days before launch.</li></ul><p><a href="http://blog.thebrickfactory.com/iyf-prototype/">You can view the prototype here.</a></p><h3>Finished Site</h3><p>We received minor edits to the prototype from IYF. By the time we addressed this feedback, the finished copy was ready. As a next step we dropped in the real copy and produced a complete draft of the micro-site that we sent to IYF for review. Due to the process we established, nearly all the edits were tweaks to copy and images as opposed to changes to functionality.</p><p><a href="http://www.iyfnet.org/annual-report/2015/">You can view the finished site here.</a></p><h3>Bottom Line</h3><p>With the proliferation of screen resolutions and the increasing sophistication of interfaces, designing websites has gotten really complicated the last few years. Given how hard it is, even the smartest, most well-intentioned designers and developers will fail if they don’t have good processes in place.</p><p>The IYF Annual Report project went smoothly because we focused on small, lightweight deliverables that did a good job of communicating our vision for the site. We used wireframes to demonstrate the structure of the site and our overall approach. We used a mood board and component comps to define the visual style for the site. Then we used a prototype to get initial feedback on the site’s responsiveness and animation styles prior to building out the full piece.</p><p><em>You can read a case study about the </em><a href="http://www.thebrickfactory.com/case-studies/iyf-annual-report"><em>project here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac0628a14095" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Web Development Process Explained in 11 Animated Gifs]]></title>
            <link>https://medium.com/@toddzeigler/the-web-development-process-explained-in-11-animated-gifs-1c6f3f76ef31?source=rss-7fa631982c8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c6f3f76ef31</guid>
            <category><![CDATA[gif]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Todd Zeigler]]></dc:creator>
            <pubDate>Wed, 06 Jul 2016 17:24:11 GMT</pubDate>
            <atom:updated>2016-07-06T17:32:10.050Z</atom:updated>
            <content:encoded><![CDATA[<p>Building websites is hard work. And a lot of it isn’t that much fun.</p><p>To help explain the process, we’ve put together this tongue and cheek post that explains how we typically feel during the various stages of a web development process. Since we build sites for clients, this post if from the point of view of a web development firm. Clients will likely experience similar mood swings, but at different points.</p><h3>(1) Award of project…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/212/0*CfTMBtMi8MyEtXBt.gif" /></figure><p>As a web development firm, having people hire us to build websites is a pretty critical part of our business model. The process of signing up new clients can be time consuming and stressful, so it always feels great to get a win.</p><h3>(2) Awesome kick off meeting…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*NTZh9bG8PIo-9Z0S.gif" /></figure><p>The beginning of a project is always sunshine and rainbows. Energy and focus is high and everyone is full of hope about the outcome. We are all in sync and working well together.</p><h3>(3) Presentation of initial design work…..</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*WpJmNFXt4cU1yyy9.gif" /></figure><p>The design process usually starts out well, with a well received initial design set. We’re feeling confident.</p><h3>(4) Reaction to design edits, round 10….</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*L4Xaub5u0vwfudxm.gif" /></figure><p>In an ideal world, we just go straight from step 3 to step 5. But sometimes things go off the rails, and we’re hearing the intern’s opinion on san serif fonts ten edit rounds into things. When this happens, <a href="http://www.thebrickfactory.com/our-people/tom-mccormick">Tom</a> may do his Bobby Knight impression.</p><h3>(5) Design is approved…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*BaOeCNyMtKqCVXIL.gif" /></figure><p>The sun is shining and we’re feeling optimistic again. With the design approved we’re free to start turning the design comps into a working website. A big hurdle has been overcome.</p><h3>(6) Testing on mobile phones and tablets…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*Hpj_5WEoyqfn1sYV.gif" /></figure><p>At this point we’ve got a draft of the site that works pretty well on our desktop computers. On average, 20% of visitors to our client sites come from tablets and mobile phones. Given that, pretty much all the sites we build are responsive, ensuring they work well no matter the screen size. This sounds pretty easy, but the reality is that getting sites to work well on mobile and tablets kind of sucks.</p><h3>(7) Internet Explorer testing and debugging…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*TpzVX0QALh7hN8dX.gif" /></figure><p>As hard as testing on phones and tablets is, debugging in Internet Explorer is much, much worse. It is soul crushing. If you say the words “Internet Explore 7” to a web developer they will either burst into tears or punch you in the face.</p><h3>(8) Writing and editing site content….</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*eK2M8P_s_YwyOWAW.gif" /></figure><p>Content is important. It seems obvious, but on many web development projects it is treated as an afterthought. If you have ever had to write the content for a website, you know that at certain points the only rational thing to do is assume the fetal position.</p><h3>(9) Powering through final tweaks before launch….</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*tznSpKva8an8dGyS.gif" /></figure><p>The really, really hard work starts after you have shown the client a working draft of a site. Working through those final edits and details is death by a million cuts. We need whiskey.</p><h3>(10) Process of actually launching the site…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/0*ioD3OVw6MkPTeW9D.gif" /></figure><p>After months of work launch day arrives. No matter how much you plan, there are always a few last minute hurdles to overcome and things don’t go quite as smoothly as you’d hope. And somehow you get things done and things work out in the end.</p><h3>(11) Reaction to successful launch…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*ZqSwEZ4VZBP7Oc1O.gif" /></figure><p>And we’re back to sunshine and rainbows. The launch of a website is a new beginning.</p><p><a href="http://blog.thebrickfactory.com/2014/07/web-development-process-explained-11-animated-gifs/"><em>This post</em></a><em> originally appeared on our Brick Factory blog.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c6f3f76ef31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Systems, Not Pages]]></title>
            <link>https://medium.com/@toddzeigler/design-systems-not-pages-845a12b512c6?source=rss-7fa631982c8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/845a12b512c6</guid>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Todd Zeigler]]></dc:creator>
            <pubDate>Thu, 30 Jun 2016 14:43:42 GMT</pubDate>
            <atom:updated>2016-07-01T13:35:44.776Z</atom:updated>
            <content:encoded><![CDATA[<p>For most of the web’s short lifetime, the primary way to design a website has been to create wireframes and comps (design compositions) of a site’s key pages. Oversimplifying a bit, designers identify these key pages and essentially create pictures of what the pages look like when presented on the web. The designs are typically done with desktop computers in mind and at a fixed screen width.</p><p>The client or product owner provides feedback on the work and eventually approve the page designs. The comps then get converted into HTML/CSS and built out as templates in whatever Content Management System is being used. And done! Like magic!</p><p>While not exactly easy, this process more or less worked for a long time and was the primary method most firms used to design websites. For a variety of reasons, over the last few years this page-centric design approach has proven to be irrevocably broken. It is somehow both extremely time consuming and ineffective at showing what the end product will actually look like.</p><p>Following we explain the problems with page-based design and explain how our Brick Factory team has transitioned to a system-based design approach.</p><h3>Why page-based design doesn’t work</h3><p><strong>Rise of Smartphones and tablets.</strong></p><p>Five years ago, nearly all website traffic came from desktop and laptop computers. If 10% of a site’s traffic came from phones and tablets that was a lot. Today it isn’t unusual for a site to see 50% of traffic coming from phones and tablets.</p><p>And within each of the main device categories (phones, tablets, desktops and laptops) there is a ton of variance in screen sizes. For our average site, the most popular screen size (usually 1366 * 768) is used by only 10% of visitors. For the highly trafficked websites we work on, we might see as many as 1,500 unique screen resolutions each month. A single site design must provide a good experience on gigantic desktop monitors (2560 * 1600) and tiny mobile screens (230 * 270). As you can see, these are two very different balls of wax.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*AC9wWAV6nKJxiVxy.jpg" /></figure><p>Given the range of screen resolutions, creating designs comps of a bunch of pages at arbitrary screen sizes just doesn’t make a lot of sense.</p><p><strong>Increased Complexity of Interfaces</strong></p><p>Web design has gotten a lot more sophisticated over the last few years. The projects we complete for our larger clients feel more like applications than simple websites, with user inputs often driving how the site looks and behaves. Designing these interactions out as “pages” requires a ton of page comps. For example, a donation system for a nonprofit client could easily require 10–20 page comps by itself.</p><p>Even simple websites are much more complex than they were four or five years ago. A four or five page promotional website today is likely to include sophisticated transitions and animations that are difficult to convey in a page comp.</p><p>It just isn’t efficient to demonstrate this sort of complexity via flat, page-based design comps.</p><p><strong>Page-Based Design Doesn’t Scale</strong></p><p>Due to the proliferation of screen resolutions and increase in complexity, on complex projects we have ended up doing a staggering number of wireframes and design comps using page-based design. Whereas four or five years ago a complex project might have meant twenty page designs, today it can easily mean 50–100.</p><p>The sheer volume of comps that we have ended up producing has lead to consistency problems. If every page is designed separately, unnecessary and redundant design elements are very likely to get introduced. This makes the resulting site harder to build and maintain, and the overall quality of the work is compromised.</p><p>Page-based design just doesn’t scale.</p><p><strong>Bottom Line</strong></p><p>Perhaps the biggest problem with page-based design is that it creates an inaccurate representation of how the end user will experience the resulting website. The designs a client approves don’t really reflect what the site ends up looking like.</p><p>Once those pixel perfect PSDs are turned into HTML/CSS and viewed in different browsers at different screen resolutions, they often look pretty different. All that painstaking design work is sort of wasted, as you still end up spending a ton of time polishing the site once you have a working draft.</p><p>Ultimately with page-based design there is a fundamental disconnect between the way the site is designed (flat PSDs) and the way it is built (HTML, CSS, Javascript, etc.).</p><h3>So What’s the Solution?</h3><p>While it has been a bit of a struggle, over the last few years we have made a conscious effort to move away from page-based design. Along with many <a href="https://www.google.com/url?q=http://atomicdesign.bradfrost.com/&amp;sa=D&amp;ust=1467296630573000&amp;usg=AFQjCNFYIpsehbjmqA3sq2CKiW9snWakmg">other designers</a>, we are trying to design systems instead of pages.</p><p>While we are still refining our process, for us this means creating a design process that is in tune with the way websites are actually built and function. We design overall styles and repeating elements that make up the pages, instead of the pages themselves. So instead of fifty design comps, for a project today we might produce the following design deliverables for a client:</p><ul><li>An overall style guide that defines palette and typography and the look/feel for critical, repeated site elements such as buttons, bullets, forms, images and icons.</li><li>Designs for key components that will be used repeatedly on the website. For our clients, typical repeating components might include a site navigation system, page header, email sign-up, photo gallery, news headline grid and donation system. For components that require interactivity, we will produce an HTML prototypes in addition to or instead of a set a of flat design comps.</li><li>Content hierarchy and/or wireframes that define what components make up each of the page templates we create.</li><li>Wireframes and design comps for a few important pages so the product owner or client can get a sense of what the end product will look like. We aim to limit this to a handful of key pages instead of creating a design for every unique page and template.</li></ul><p>After we get these key building blocks designed and approved, we start creating the site templates in HTML/CSS and see what things look like. We then allow ourselves plenty of time for refinement and polish. Instead of front loading all the design work, we take a more agile approach and fine tune the design after we see what the working draft looks like.</p><p>We haven’t perfected our process yet and by the time we do everything is likely to change again. But, at least to us, this system-based approach makes a lot more sense than producing 50–100 page comps.</p><p><em>This was originally posted on our </em><a href="http://blog.thebrickfactory.com/2016/06/designing-systems-instead-of-pages/"><em>Brick Factory blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=845a12b512c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nine Ways to Improve the Drupal Administrative Experience]]></title>
            <link>https://medium.com/@toddzeigler/nine-ways-to-improve-the-drupal-administrative-experience-45e58031f2f0?source=rss-7fa631982c8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/45e58031f2f0</guid>
            <category><![CDATA[drupal]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Todd Zeigler]]></dc:creator>
            <pubDate>Sun, 05 Jun 2016 14:55:45 GMT</pubDate>
            <atom:updated>2016-06-05T21:41:48.365Z</atom:updated>
            <content:encoded><![CDATA[<p>In the open source world, you often hear people observe that Drupal was built for developers while WordPress was built for content managers. This observation contains thinly veiled criticism of both platforms. For Drupal the implication is that the platform doesn’t provide a great user experience for content managers.</p><p>The criticism sticks because it is sort of true. Right out of the box Drupal’s administrative tools aren’t intuitive or easy-to-use. With the release of Drupal 8, Drupal out of the box is better than it used to be, but is still somewhat baffling to folks that aren’t familiar with the platform’s quirks.</p><p>As someone who builds sites in both WordPress and Drupal, I have to admit that I have contributed to Drupal’s bad content management reputation. I am guilty of not focusing enough on the experience of people that do the day-to-day work in Drupal: content managers. The fact is, with a little effort you can create a good content management experience in Drupal. Below are some tips on how you can improve the Drupal administrative experience.</p><p><strong>(1) Create Custom User Roles</strong></p><p>By default Drupal creates an Administrator user role that has access to the entire backend administrative system (content, theme, blocks, views, etc.). When setting up a site, all administrative users ware often given access to the full suite of backend tools. This is confusing to many users as they have access to lots of features they aren’t familiar with and really shouldn’t be using. It can also lead to bugs as admins experiment with backend tools they haven’t been trained on.</p><p>Drupal features a powerful user role system that allows for the creation of custom user roles. Once a custom role is created, super administrators can pick and choose what backend features and functionality the role has access to. At the beginning of a new project user roles should be set up for the different types of administrators. People who are just going to be managing content should only have access to the content editing tools. If someone is just posting press releases, they should just have the ability to post press release.</p><p>This approach both makes the administrative tools easier to use and prevents mistakes caused by people using features they haven’t been trained on.</p><p><strong>(2) Customize the Look of the Administrative Section</strong></p><p>The default Drupal administrative themes that come with Drupal 6 and 7 aren’t very attractive or usable. Fortunately there are a myriad of slick administrative themes you can install to improve the Drupal administrative experience. We are partial to <a href="https://www.google.com/url?q=https://www.drupal.org/project/ember&amp;sa=D&amp;ust=1464303143017000&amp;usg=AFQjCNH5I9SGuAn4-OwYGJ-13McP6Kz5jA">Ember</a> for Drupal 7 sites.</p><p>Drupal 8 actually has a pretty nice default administrative theme, although you can use a different theme (or create your own) if you want to.</p><p>Take the time to make sure your Drupal administrative section looks as nice as the site’s frontend.</p><p><strong>(3) Customize the Options in Your Administrative Menu</strong></p><p>If you have used a Drupal site you are undoubtedly familiar with the menu options that are available by default. Content. Structure. Appearance. People. Modules. Configuration.</p><p>While these options make pretty good sense for people that have full administrative rights and know Drupal, they aren’t relevant for all users on all projects. We recommend customizing the menu options based on your site’s workflow/needs.</p><p>Some tips:</p><ul><li>Minimize clicks by having frequently used administrative pages accessible via the top level navigation system. If 90% of the site’s content involves creating and editing blog content, have “Create Blog Entry” and “Edit Blog Entries” be two of your top level options. Give admins easy access to the functions they perform frequently.</li><li>Don’t be afraid to rename things. If you think “Theme” makes more sense than “Appearance” then simply rename the tab.</li><li>Add links to other resources you use in managing your site that may not be part of Drupal. Add links to documentation, style guides, Analytics accounts, etc. so that the Drupal administrative section can serve as the definitive resource for your web program.</li></ul><p><strong>(4) Create Custom Administrative Views</strong></p><p>By default Drupal features a “Find Content” section that allows for users to filter results by content type. On more complex sites this section becomes inadequate as your administrators will want to search using different criteria based on the content type they are reviewing. For example, an administrator may want to filter the content type blog post by author. This author filter may not be relevant for a content type such as press releases.</p><p>It is easy in Drupal to customize the options available on that main Find Content page and to create custom views for specific content types. Take the time to customize the backend content view pages so they are truly useful to administrators.</p><p><strong>(5) Take the Time to Set Up the Dashboard</strong></p><p>Drupal comes with an administrative dashboard section that allows you to create quick links to the most frequently used content. Take the time to set up and customize your site’s administrative dashboard. Here are some ideas on how the dashboard can be used:</p><ul><li>Create quick links to functions that are performed all the time. This would include things like Add Press Releases, Edit Press Releases, etc..</li><li>Create quick links to third party resources the client may want to access. This might include links to Google Analytics, Mailchimp, Client Reports, Style Guide, etc.</li><li>Include a list of recent content the user has edited.</li><li>Include a list of content updated by other users.</li></ul><p><strong>(6) Write Instructions</strong></p><p>When building large Drupal sites it is inevitable that some content types end up with a ton of fields. These fields can be mysterious to people not familiar with the site.. We recommend grouping these fields into logical field collections and writing clear instructions as to what the fields are used for as a way to avoid confusion.</p><p>As an example, say you have a content type called Research that includes a checkbox called Featured Research. On the backend you should explain that clicking this checkbox causes the research node to be featured prominently on the main Research page. Write clear instructions so that administrators always know the ramifications of the choices they make.</p><p><strong>(7) Document Image Sizes</strong></p><p>Over the years our Drupal sites have gotten more and more image intensive. And with the rise of mobile we also find ourselves having to upload multiple versions of images to ensure they look good on phones and tablets as well as desktops.</p><p>It sounds simple, but on the backend you should provide specs to content administrators regarding the file size, dimensions and format of images. If you want a square jpg that is no more than 500*500 to be uploaded, tell the administrators that up front. It will save a lot of trial and error.</p><p><strong>(8) Install and/or Customize the WYSIWYG</strong></p><p>It sounds crazy, but Drupal 8 is the first version of Drupal to include a WYSIWYG in core. (I told you Drupal was built for developers). So if your site is in Drupal 7, as a first step you will need to install a WYSIWYG module such as <a href="https://www.google.com/url?q=https://www.drupal.org/project/ckeditor&amp;sa=D&amp;ust=1464303143027000&amp;usg=AFQjCNFp5ACPhCqbQ0KzXC6AIq2P5ng_xw">CKEditor</a> if you don’t want your content editors to have to write straight code.</p><p>Once you have a WYSIWYG installed take the the time to customize the options that are available based on what your content managers will be doing. If you know your content managers will be copying a lot of content from Word, include the Paste from Word option. If you don’t want content editors to change fonts, don’t include the font selector option.</p><p>While we encourage the installation of WYSIWYG’s for basic formatting, we advise against providing too many options. If you have set up your Drupal site in an intelligent way, content managers should only be doing basic editing work (adding links, bullets, etc.) in the WYSIWYG.</p><p><strong>(9) Don’t Forget to Do Spring Cleaning</strong></p><p>A lot of the sites we manage have been in Drupal for years. In many cases the backends of our sites have gotten really messy as a result. Take the time a few times a year to go in and clean up to make sure the administrative tools remain easy-to-use.</p><p>Are there fields, taxonomies or content types that are no longer in use? Remove them. Are there new materials that should be featured in the overall administrative menu? Add them. Are there materials that are no longer relevant? Delete the links.</p><p>Periodic clean up is important. Without it the administrative section can get really confusing for new people who come on board who may not have historical knowledge of a site.</p><p><em>This was </em><a href="http://blog.thebrickfactory.com/2016/05/improve-the-drupal-administrative-experience/"><em>originally published</em></a><em> on our Brick Factory company blog.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45e58031f2f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How the Rise of Smart Phones and Tablets is Impacting My Clients]]></title>
            <link>https://medium.com/@toddzeigler/i-own-a-20-person-web-development-shop-based-out-of-washington-dc-called-the-brick-factory-our-1f2f2ce1698?source=rss-7fa631982c8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f2f2ce1698</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[responsive-design]]></category>
            <dc:creator><![CDATA[Todd Zeigler]]></dc:creator>
            <pubDate>Sat, 14 Mar 2015 14:42:21 GMT</pubDate>
            <atom:updated>2015-03-14T14:43:33.122Z</atom:updated>
            <content:encoded><![CDATA[<p>I own a 20-person web development shop based out of Washington, DC called the <a href="http://www.thebrickfactory.com/">Brick Factory</a>. Our clients are primarily non-profits, advocacy groups and brands.</p><p>The hype the last few years about the explosion of the mobile web has been pretty deafening. While I’m interested in the overall trend, I’m more interested in how the profiliferation of smart phones and tablets is impacting my actual clients. To further this understanding for the last few years my firm has taken an aggregate look smart phone/mobile visits of the websites we manage (60+ sites). Below are the key findings from our look at 2014 traffic data.</p><h2>Overall Trend</h2><p>Cutting to the chase, smart phone and tablet visits to the sites we manage grew aggressively in 2014. Just under 32% of visitors came from smart phones and tablets in 2014. Here is a graph showing the trend since we starting tracking this in 2010:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LXULvFskViNdSmyl.jpg" /></figure><p>After more than doubling every year from 2010 to 2013, traffic from smart phones and tablets <em>only</em> increased by 70% from 2013 to 2014. While I expect the percentage growth to slow further this year, I still project that by the end of 2015 close to 50% of the traffic to the sites we manage will come from smart phones and tablets.</p><h2>Variance</h2><p>While the aggregate trend is obviously important, diving into the data it is clear that each site has its own unique story to tell. Traffic from mobile devices ranged from 2% to 70% among our client base. Here is a graphic that demonstrates how much the mobile/tablet traffic percentage varied from site to site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ci7kCtyouk38Hvas.jpg" /></figure><p>The audience and goals of a site/organization has a huge impact of how much traffic comes from smart phones and tablets.</p><p>As an example, one of our clients is a company that focuses on professional development for large corporations. Since their clients are primarily accessing their web properties from work computers during office hours, their mobile/tablet percentage was only around 15%. Due to the nature of their work, their target audience tended to access the site from desktops/laptops more often than our average client.</p><p>Contrast that with another client that is a large advocacy group. This client maintains an active blog, sends out daily email alerts and frequently comments on breaking news. 50% of their traffic comes from mobile and tablets.</p><h2>Smart Phones vs. Tablets</h2><p>Smart phones were used to access the sites we manage more than twice as often as tablets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xN_51g3syvC-i-zx.jpg" /></figure><p>Interestingly, we saw a moderate increase in overall traffic from desktops and laptops. This increase was just dwarfed by the more dramatic increase in accesses from mobile phones and tablets. For our clients at least, the story isn’t that desktop and laptop usage is dying, it is that visits from phones and tablets are exploding.</p><h2>Android and Apple</h2><p>Interestingly, more people accessed the sites we manage from Android smart phones than from iPhones in 2014. The iPhone was the dominant device from 2010–2013. The iPad continues to dominate the tablet market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NhzVDJnVAjYRXWOe.jpg" /></figure><h2>Bottom Line</h2><p>The conclusion here is obvious: responsive design is now the rule and not the exception.</p><p>Back in 2010 and 2011, when planning projects we treated making a site mobile-friendly as a nice-to-have for most of our clients. The percentage of visitors coming from smart phones and tablets often didn’t justify the added time and cost required to make a site mobile-friendly. Creating a great mobile and tablet experience is now very clearly a requirement for every project we work on.</p><p><em>Note: This post is a modified version of a piece I originally wrote for our </em><a href="http://blog.thebrickfactory.com/2015/03/how-the-rise-of-smart-phones-and-tablets-is-impacting-our-clients/"><em>Brick Factory blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f2f2ce1698" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>