<?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[Macalester HCI - Medium]]></title>
        <description><![CDATA[Students explored a number of design problems in 2–3 week design sprints over the semester. This is what they came up with! - Medium]]></description>
        <link>https://medium.com/macalester-hci?source=rss----7ac5db827006---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Macalester HCI - Medium</title>
            <link>https://medium.com/macalester-hci?source=rss----7ac5db827006---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 17:26:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/macalester-hci" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Making an Attachable Basketball Hoop Device for Blind and Low-Vision Players]]></title>
            <link>https://medium.com/macalester-hci/making-an-attachable-basketball-hoop-device-for-blind-and-low-vision-players-76ef1f4ebdfe?source=rss----7ac5db827006---4</link>
            <guid isPermaLink="false">https://medium.com/p/76ef1f4ebdfe</guid>
            <category><![CDATA[blind-basketball]]></category>
            <category><![CDATA[accessible-design]]></category>
            <dc:creator><![CDATA[Sydneygreene]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 06:50:04 GMT</pubDate>
            <atom:updated>2026-11-09T22:31:43.952Z</atom:updated>
            <content:encoded><![CDATA[<h3>Making a Mountable Basketball Hoop Device for Blind and Low-Vision Players</h3><h3>Introduction</h3><p>Our group, the Think Tank, was tasked with designing for a group of people we are less familiar with and emphasizing accessibility centered design for our human-computer interaction course. Our team is made up of computer science majors and minors (Alli, Huthaifa, Sydney, and Tara) at Macalester College with a passion for design. Sports and staying active are important to everyone in our group, so as we were looking through design challenges on the <a href="https://www.makersmakingchange.com/design-challenges">Makers Making Change Website</a>, we felt particularly drawn to a design challenge to create an audible basketball hoop system for blind and low-vision athletes. After reading through the design challenge description, we set out to build an attachment that helps players <em>locate</em> the hoop and <em>know</em> when they score.</p><figure><img alt="Our four different sections– “understand, design, test, and evaluate” with   “understand” emphasized." src="https://cdn-images-1.medium.com/max/877/1*xMhnBmQ6aySwkzj6SoM66Q.png" /></figure><h3>Understanding the Problem</h3><p>The first task in our design process was understanding the problem we were designing for. The original publisher outlined some design features they were looking for from the product, and posed some open questions that we could tinker with during our design process. Once we had a good idea of what Eli was looking for, we looked to see what other design solutions had been developed. There were some really amazing solutions out there (see: <a href="https://www.newswise.com/articles/undergraduate-engineers-devise-basketball-system-for-the-blind">Johns Hopkins System</a>, <a href="https://www.isd411.org/about-us/news/news-article/~board/district-news/post/sonic-dunk-revolutionizing-basketball-for-low-vision-and-no-vision-athletes">Sonic Dunk Robotics Team</a>, <a href="https://www.havi.co/blogs/diy-smart-basketball?srsltid=AU7gw4Xz07pOql34g4y7pXY3BoxezIKbgrUfndriPmQVRBgOkb0-3uHz">Argentina Open-Source Board</a>). Looking at these designs, we noticed that they either had continuous sound <em>or </em>shot feedback, but we didn’t come across anything that incorporated both of these features.</p><p>All of the existing designs replaced the hoop entirely rather than attaching to an existing hoop. We didn’t want to have to do this as it would be more pricey and harder to install. Jacob Wobbrock et al. explain this concept of availability well in their <a href="https://dl.acm.org/doi/pdf/10.1145/3148051">Ability-Based Design</a>. Also, we found out that blind basketball players typically have someone tap on the hoop to locate the hoop. This fits the Ability principle mentioned by Wobbrock et al., as we are leveraging the fact that blind and low-vision users are excellent at localizing sound. We chose an electronic sound rather than physical tapping, though, as the audio can be tuned and changed easily upon the desire of the user. With all this in mind, we created a set of criteria for our audible hoop design and left some questions open to explore during user testing:</p><figure><img alt="A diagram of questions we encountered during the brainstorming phase. Low Cost: accessible for other makers and within the budget constraints. Attachable: make a design that works with many types of hoops so it can work anywhere. Adjustable Audio Levels: Product can be used indoors and outdoors, emits a sound that can be easily heard but not distracting. Open Source Files: Design that is accessible to the community, and allows other designers and makers to use and improve upon our design. Durabl" src="https://cdn-images-1.medium.com/max/776/1*ddhPzCQORaohLmMZMnjWoA.png" /><figcaption>A diagram of questions we encountered during the brainstorming phase.</figcaption></figure><h3>Understanding Our User Group</h3><p>We had a decent understanding of what the problem we set out to solve is, but we couldn’t truly understand the problem or design the best solution possible without engaging with the people who would actually benefit from and use our solution. We were recommended by our professor to look into the sport of goalball. Goalball, a sport designed exclusively for blind and low-vision athletes, uses a rubber ball with bells inside it that allows athletes to hear where the ball is at all times, and tactile markings on the floor to help athletes orient themselves on the court. If you are interested in learning more about goalball (visit the <a href="https://www.paralympic.org/goalball">Paralympic Goalball Website</a>). Tara reached out to the goalball team at the University of Minnesota and got the chance to observe and play goalball with them. During the session, we gathered valuable insights into what the hoop should provide, particularly regarding the device’s sound and placement. One initial idea was to use spoken guidance, with an automated voice continuously informing players of their position relative to the goal, whether they had missed, how close their shot was, and whether they had scored.</p><p>However, team members felt that continuous voice guidance could be overwhelming and blend with other sounds, causing confusion, especially due to many players talking to each other during the game. They emphasized that players should be able to focus on the sound of the ball while playing most importantly. Instead, they suggested that the device emit a constant sound from the hoop to help players locate it and stay oriented. They also recommended using a distinct sound to signal a score — one that would not be confused with other sounds. Through this connection, we were also able to send the goalball team a questionnaire to gather feedback on more specific design features:</p><figure><img alt="The questionnaire. The first question: what kind of sound would be most helpful to locate a basketball hoop? 1. tapping noises, 2. constant pitch, 3. a beep. The second question: How helpful would it be to have a different sound play when a basket is made from a scale of 1–5?" src="https://cdn-images-1.medium.com/max/519/1*ai3g93m4VyBFu1FFU1RwQQ.png" /><figcaption>The first two questions of the questionnaire.</figcaption></figure><p>Although we received only one response before moving into high-fidelity prototyping, Tara’s experience helped us better understand the community we are designing for and make more human-centered design choices. The response also confirmed some of our initial assumptions: a beeping sound would be beneficial, and its volume would best be adjustable. We also received useful suggestions for additional features, including Bluetooth connectivity and customizable audio. As our respondent explained, “I think that for someone who is blind, having the ability to connect AirPods or some sort of Bluetooth headphones would be helpful. If they had more spacial audio features, they could actually hear the beeping a lot better between shots.” However, we still wish we could have gotten more feedback for participatory design purposes, <a href="https://faculty.washington.edu/ajko/books/design-methods/design">as explained by Amy Ko</a>.</p><figure><img alt="Our four different sections– “understand, design, test, and evaluate” with “design” emphasized." src="https://cdn-images-1.medium.com/max/866/1*ZfafXHX0Mq6VMjCf3bnNtQ.png" /></figure><h3>Design Decisions</h3><h4>Sketching and Low-Fidelity Prototype</h4><p>With our key design elements in mind, we began making our first design decisions. To start, we brainstormed a collection of divergent sketches. These sketches allowed us to get creative with design elements and explore a bunch of possibilities, and then choose the best aspects of each to move forward with to make the best possible design solution we could.</p><figure><img alt="Possible design sketch series, showing the speakers and sensor zones in different positions. Some notes about whether or not to use a speaking voice, meter detecting, player positions, and a distance speaker." src="https://cdn-images-1.medium.com/max/568/1*eD5SOawN8TTDJaMwLNqYBw.png" /><figcaption>Possible design sketches.</figcaption></figure><p>In addition to the sketch series, we also collected a set of sounds to test during the low-fidelity testing phase (beep, metronome, sonar ping, chirp). <em>If there’s a way to embed these into the medium post here, that would be great. </em>From our sketches, we decided we wanted to mount a motion sensor connected to a CPX and speaker in the space between the rim and the backboard; this way, it could make a distinct score sound when a ball passed through the basket. Our low-fidelity prototype imitated how this system would work, since we didn’t have any of the hardware yet, though we had to get a bit creative. We ended up using a toy basketball hoop and mounting a phone to the board to play the various sounds we had previously collected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dEYX5q9q348KbyWQAU-jnA.png" /><figcaption>Low-fidelity prototype in which the phone produced a beeping sound while we were experimenting with the device position.</figcaption></figure><p>The low-fidelity prototype, while very crude, helped demonstrate our concept as well as gather feedback on what type of sound we should move forward with for the high-fidelity prototype.</p><h4>Hardware and High-Fidelity Prototype</h4><p>Our group has a good amount of experience with software, but hardware was much more out of our comfort zone, so we spoke with Dave Bailey, a Macalester Scientific Instrument Technician. He directed us to a time-of-flight sensor well suited for our project and provided us with a speaker. We also began designing a 3D-printed case to hold all of the hardware components, which could then be clipped onto a basketball hoop. He explained that the time-of-flight sensor was affordable and sends out an IR signal that measures how far away an object is when it bounces back. This would work for what we needed.</p><figure><img alt="Sketch of initial case idea, showing that the case will clip on the underside of the place the hoop mounts to the backboard. A diagram showing an initial layout of the components inside of the case." src="https://cdn-images-1.medium.com/max/519/1*YKf1BH9WQyvmA_LyvlmY2g.png" /><figcaption>Sketch of the initial case idea.</figcaption></figure><p>While we were waiting for our time-of-flight sensor to arrive, we got to work on the programming for the audio beacon and the score audio using CircuitPython, as well as formatting WAV files so they would be compatible with our microcontroller (Circuit Playground Express). The code plays a constant beep when the CPX is turned on, and we also included code to uncomment once we got the sensor. This code detects when an object passes in front of the sensor within a given range, stops the constant beep, and plays a sound to alert players when a basket is made. Once the time-of-flight sensor arrived, we connected all of the components with alligator clips and an audio jack for the speaker and tested it out. The constant audio beacon played as expected, and the score audio (the coin sound from Super Mario Bros.) played when the time-of-flight sensor was triggered.</p><figure><img alt="Steps showing the wiring of the CPX, case testing, wiring of the sensor, and everything wired together." src="https://cdn-images-1.medium.com/max/975/1*mCZyirH0xGnP5hGBNOQWog.png" /><figcaption>Creation of the High-Fidelity Prototype.</figcaption></figure><p>The alligator clips worked fine for testing, but they were only ever meant to be temporary. Once the attachment was mounted on a hoop and taking hits from basketballs, the connections needed to be secure. Soldering the wires between the time-of-flight sensor, the audio jack, and the circuit board would hold up much better, but it’s permanent, so we had to be sure about our layout before committing. We planned out where each wire would go and how long it needed to be to fit inside the enclosure. None of us had soldered before, so we went back to Dave Bailey, who taught us how.</p><figure><img alt="Images showing different steps of soldering." src="https://cdn-images-1.medium.com/max/901/1*ZeOhZxV5uWKFMXbGJBGgTg.png" /><figcaption>The soldering process.</figcaption></figure><p>While we were figuring out the circuitry, we were also designing the enclosure that would hold everything and mount it to the hoop. It needed room for the circuit board, the battery, the time-of-flight sensor, and the audio jack. Most of us had no 3D modeling experience, so instead of building a case from scratch, we started with an existing square case model and added features to it. That saved us from having to work out every dimension ourselves and cut down on iteration time.</p><figure><img alt="The base case model we started from." src="https://cdn-images-1.medium.com/max/484/1*8ZDbllwhXcui98UpJl0o_Q.png" /><figcaption>The base case model we started from.</figcaption></figure><p>We used Fusion 360 to edit the model. After a couple of hours of tutorials and playing around with the software, we had an okay prototype, so we printed it to see how it looked and to check our measurements. But we were curious whether AI could help us get to a more functional enclosure with the information we already had.</p><figure><img alt="Our first fusion prototype after a few hours of tutorials." src="https://cdn-images-1.medium.com/max/909/1*0n76nzceFta-Qb9QOFidyA.png" /><figcaption>Our first Fusion prototype after a few hours of tutorials.</figcaption></figure><p>We started researching the best ways to create 3D models with Claude and found a plugin called SolidCraft that we wanted to try. We used a chatbot to help us write a detailed prompt with everything about the design and what we wanted the enclosure to do, then gave that prompt to Claude with the plugin installed. About 15 minutes later, it gave us an STL file we could print and test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TzYSIiR0Fz0kFxMWfARJSQ.png" /><figcaption><em>Part of the prompt we used to generate the enclosure with Claude</em></figcaption></figure><p>The print showed us a couple of problems: the battery compartment was a little narrower than we expected, and the audio jack section didn’t match the shape of our jack or the way we were connecting it to the board.</p><figure><img alt="The updated model. The battery compartment came out too narrow, and the audio jack opening didn’t match our jack." src="https://cdn-images-1.medium.com/max/667/1*yc533bMHkFT4cm_ExyPQkQ.png" /><figcaption><em>The battery compartment came out too narrow, and the audio jack opening didn’t match our jack.</em></figcaption></figure><p>We tried fixing the file ourselves, but editing an STL in Fusion is tricky, so we decided to see if AI could help with that too. We wrote a new prompt asking Claude to turn the STL into an editable Fusion file, gave it the STL, and it worked. From there, making changes was much easier than trying to edit the STL directly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q_3p6MJWLrPM3ksrZnWDcA.png" /><figcaption><em>The STL converted into an editable Fusion file</em></figcaption></figure><figure><img alt="The final enclosure with everything in place." src="https://cdn-images-1.medium.com/max/700/1*PbHwXGTsgneVe4IxnSdlOw.png" /><figcaption>The final enclosure with everything in place.</figcaption></figure><figure><img alt="Pictures showing the first, second, and final prototype. The final prototype has everything in place." src="https://cdn-images-1.medium.com/max/975/1*R0KXOnvXBRJK3XtQaGxQpA.png" /><figcaption>3D printed case process.</figcaption></figure><figure><img alt="Our four different sections– “understand, design, test, and evaluate” with “test”." src="https://cdn-images-1.medium.com/max/915/1*O6j-vvsSsObnVnDui51B7g.png" /></figure><h3>Testing</h3><h4>Initial Testing</h4><p>After having everything together and set up, we did some initial tests without a hoop. We moved our hands in front of the sensor and dropped things in front of it. We quickly realized that the sensor was picking up <em>anything</em> in front of it. This would be a problem when it comes to actually using a hoop– even though the standard hoop is ten feet off the ground, the net would still be in front of the sensor. We quickly changed and tested the code with the help of Claude. Eventually, we were able to code the sensor to only detect a <em>change</em> in the data it receives every ten milliseconds or so. This allows it to ignore the net and register a ball falling through the hoop. We also wanted to be sure to follow Wobbrock’s Accountability principle, and not expect users to understand that it falsely triggers on the net. That is our responsibility to make sure our design works correctly.</p><h4>Real Time Testing</h4><p>We were able to test our prototype on a standard-sized basketball net and backboard, but it was low to the ground as it was made for kids. We were unable to use the Macalester court because we were not able to get in contact with the person who is in charge of athletic facilities, and basketball season had started. The gyms were in use. Alli and Sydney went to a nearby park with an adjustable hoop, but it was being used. They went to another park but were unable to adjust the hoop as it was locked. Luckily, the low basketball hoop was there and would prove sufficient for testing on a standard-sized net, backboard, and basketball. We secured the product onto the underside of the mount, as planned, with duct tape.</p><figure><img alt="Two different angles of the product mounted onto the hoop with duct tape." src="https://cdn-images-1.medium.com/max/663/1*fo3HrtbfoKIVNZGxihsZuw.png" /><figcaption><em>Two different angles of the product mounted onto the hoop with duct tape.</em></figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3yHErsuwpc0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3yHErsuwpc0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3yHErsuwpc0%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fca4f23f13de4a2408e74b10fffac3aa/href">https://medium.com/media/fca4f23f13de4a2408e74b10fffac3aa/href</a></iframe><figure><img alt="Our four different sections– “understand, design, test, and evaluate” with “evaluate” emphasized." src="https://cdn-images-1.medium.com/max/870/1*ZQRywLFinI1xd4Ump3E7mQ.png" /></figure><h3>Feedback, Considerations and Limitations</h3><p>When our prototype was nearly completed, we had the opportunity to meet with Gina Fugate, Ph.D., and a teacher of the visually impaired at the Maryland State School for the Blind, as well as being low vision herself.</p><p>We met with Gina over Zoom to show her our prototype and get feedback on our design choices. Gina told us that in a typical game of basketball with blind and low vision athletes, someone taps the basketball hoop with a stick at the beginning of each possession so athletes can orient themselves toward the hoop, but this current method still makes it quite challenging for athletes who are constantly trying to locate the hoop. She thought our constant sound beacon could be extremely helpful to athletes and make it much easier for them to orient themselves toward the hoop. When we did a demo of our prototype, Gina had some very helpful thoughts.</p><p>Originally, we had gotten feedback from the goalball team that directed us to a beeping sound, but Gina was a bit surprised that was the sound we had chosen. She said people have many different opinions on which type of sound they prefer; some people really like the beeping noise and some people hate it; it just depends on the person. She also thought eventually making a ball that emitted another sound would be helpful for athletes as well. Based on this feedback, we decided it would be beneficial to add a few different sounds (tap, beeps at different frequencies, etc.) for the user to choose from.</p><p>Unfortunately, we met with Gina fairly late in our design process, so we weren’t able to design a ball or add multiple sounds that the users can easily switch between, but with more time and further iterations of our audible basketball hoop, these features would certainly be included. This would also follow Wobbrock’s principle of transparency by letting users choose what they want to hear, and allowing them to preview the sounds.</p><p>With our time, budget, and resource constraints, we were bound to have some limitations from the start. This project is a prototype, and it was never bound to be perfect. Here are some things that we would do differently if we were not constrained at all, or started all over again with what we know now.</p><ol><li><em>Mounting System:</em> The mounting system for our prototype was never finished due to the time constraints and us making sure that the product itself was viable. Ideally, this product would have a clamp, similar to a monitor arm mount, that would be made of metal, and rubber on the inside to prevent falling or moving. We were going to try to use velcro, but were unable to get anything. We instead used duct tape. It worked to keep the product in place, which is what mattered most.</li><li><em>Speaker: </em>Our speaker that we began with was a bulky speaker with a built in amplifier. It worked for making sure our sounds worked, but was too big to mount, and needed to be plugged in. We switched to the speaker on the CPX for actual testing. Ideally, we would have smaller speakers easily mountable onto the hoop, with a power source built in or batteries.</li><li><em>Sensor: </em>The ToF sensor has its limitations. The product will pick up on any movement in front of it. This means that if a ball flies under the hoop during a miss, it will go off. Unfortunately, the only way to change this would be to use a different type of sensor, multiple sensors to track which way the ball is coming from, or something like computer vision — which we did not have the budget or time for.</li><li><em>Feedback from Presentation / Critique:</em> During our group presentation and critique, we were told we could have used a physical switch instead of a sensor to count when a ball went through the hoop. We didn&#39;t initially consider this, and with more time, we would love to see if it would be successful. Our peers mostly liked the sound that plays when a basket is made, though they had mixed opinions about the beeping sound. They suggested making the beep customizable. Their “what if” questions largely aligned with ours, but we thought many of those ideas would be impractical given our budget and time constraints. They also shared useful ideas for mounting the device, some of which we thought of and some we did not. Mounting remains ambiguous, as there is not one correct way to make it universal.</li></ol><figure><img alt="Picture" src="https://cdn-images-1.medium.com/max/1024/1*xDPqXcKBqt5WhC_Iuk277w.png" /><figcaption>Peer feedback received in class answering the prompts: “I like”, “I wish” and “What if”.</figcaption></figure><p><em>Enhancements / Improvements</em> from Live Testing with User Groups: We were unable to actually test this during an actual game, or with low-vision and blind folks. With more time, this is something that we would also love to do to get more feedback.</p><p>Ultimately, even though we did not have the ability to finish and figure out everything we initially set out to do (as we are learning, which often happens in the design process), we feel successful in its viability and the ability to reproduce our product easily. With a little more time, money, and testing, this could be a professional, marketable product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76ef1f4ebdfe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macalester-hci/making-an-attachable-basketball-hoop-device-for-blind-and-low-vision-players-76ef1f4ebdfe">Making an Attachable Basketball Hoop Device for Blind and Low-Vision Players</a> was originally published in <a href="https://medium.com/macalester-hci">Macalester HCI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a D&D Dice Roller]]></title>
            <link>https://medium.com/macalester-hci/designing-a-d-d-dice-roller-a8e691bfea51?source=rss----7ac5db827006---4</link>
            <guid isPermaLink="false">https://medium.com/p/a8e691bfea51</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[hci]]></category>
            <dc:creator><![CDATA[Moyartu Manley]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 05:02:26 GMT</pubDate>
            <atom:updated>2026-11-12T05:30:13.504Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://medium.com/u/7073538abec8">Anha Chaudhry</a>, <a href="https://medium.com/u/36164d294195">Boran Shan</a>, <a href="https://medium.com/u/031ba8ae668f">Lmanalan</a>, <a href="https://medium.com/u/bd3805f560f8">Moyartu Manley</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYPaNSQs0IUo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYPaNSQs0IUo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYPaNSQs0IUo%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/156dc2acfd8218b7f2fe11ebd285ea2a/href">https://medium.com/media/156dc2acfd8218b7f2fe11ebd285ea2a/href</a></iframe><p><em>As part of our Human-Computer Interaction course at Macalester College (Saint Paul, MN, USA), we were tasked with creating an accessible physical design to benefit an end user. So, we visited the </em><a href="https://www.makersmakingchange.com/"><em>Makers Making Change</em></a><em> website to find an unfulfilled assistive technology request. During our search, we came across a post from a user who wanted to create a lazy Susan dice roll returner for his friend, a Dungeons and Dragons (D&amp;D) player with limited grip and arm mobility. We loved this idea and readily signed on as a team.</em></p><h3>Understanding The Problem</h3><p><em>To differentiate between the post creator and the end user, we will denote them as </em><strong><em>PC </em></strong><em>and </em><strong><em>EU</em></strong><em>, respectively.</em></p><p>EU’s current setup is that he lifts an oversized die onto a ramp, which then rolls and is dropped onto a partially fastened felt tray. Once the die is dropped, someone else has to fetch it and put it back for the next roll.</p><h4>Necessary Features:</h4><p>So to fulfill those requirements, PC requested a dice roller with the following:</p><ul><li>A fixed C-shaped tray wall that is open towards the player</li><li>A rotating floor that utilizes a lazy Susan</li><li>A ramp mounted to the fixed back wall that dumps the die onto the rotating floor</li></ul><p>The goal is that after the roll is read, the floor can be turned such that the die rides around the wall into the open “home” pocket in front of EU. PC also suggested a motorized spin, but clarified that it was an optional addition.</p><blockquote><strong>EU specifically wants the <em>physical </em>act of rolling dice and a way to get the die back in front of him without someone picking it up.</strong></blockquote><h3>Low Fidelity Prototyping</h3><p>As our design process will illustrate, the Lo-Fi prototyping was a lengthy process that resulted in a multitude of sketches. Not only did we have our preliminary sketches based on the design challenge, but we continued our sketches in order to factor in feedback and real-life issues that may emerge from them. So, to get a solid reference point, we asked for pictures of the current setup.</p><figure><img alt="EU’s current setup, a ramp and felt tray" src="https://cdn-images-1.medium.com/max/1024/1*Kl7GbCN9AjTZkZ3KU1eG2Q.png" /><figcaption>EU’s current setup, a ramp and felt tray</figcaption></figure><p>From these photos and PC’s requirements, the team created 18 total sketches that best matched our mental models of the project description.</p><figure><img alt="Team sketches were around ramp-based and dice-dropping solutions" src="https://cdn-images-1.medium.com/max/1024/1*LJ_eDF5vZyiW1FQwEtKWFA.png" /><figcaption>Team sketches were around ramp-based and dice-dropping solutions</figcaption></figure><p>We wanted to ensure that our ideas aligned with PC and EU’s vision, so we sent our sketches over to confirm. PC sent back a sketch that included a wall that helped guide the dice into the pocket, so we kept that addition in mind when developing our prototypes.</p><figure><img alt="PC’s addition of a wall to Lucy’s sketch" src="https://cdn-images-1.medium.com/max/635/1*nubaviFcrY_gPcyjvwn32A.png" /><figcaption>PC’s addition of a wall to Lucy’s sketch</figcaption></figure><p>Eighteen sketches would be a lot of prototypes to build, so we picked two that felt different enough from each other to try out different features. Both follow PC’s basic layout: a fixed C-shaped wall, a proposed turning floor, and a ramp. They differ in how they’re built and in how the die gets around.</p><figure><img alt="Our two prototypes: a c-style cardboard box with a ramp, and a c-style paper ramp with a felt turntable" src="https://cdn-images-1.medium.com/max/1024/1*DEvQ-ZmHv-K5JiD8sXaYuA.png" /><figcaption>Our two prototypes: a c-style cardboard box with a ramp, and a c-style paper ramp with a felt turntable</figcaption></figure><h4>C-Style Cardboard Ramp:</h4><p>We built this prototype from a small Amazon shipping box. The red paper floor stands in for a rotating Lazy Susan, an angled flap stands in for the ramp, and a hole beneath the ramp is used to retrieve the die. Building it raised a question we hadn’t thought much about on paper: how big can the device get before it begins to interfere with a D&amp;D game? It was also difficult to grab the dice from the opening at the bottom, since the dice could land a little farther than was convenient to reach.</p><h4>Felt Turntable Ramp:</h4><p>This prototype tested the rotating floor itself: a disc of felt atop a circular piece of cardboard, with a C-shaped wall of blue paper wrapped around it. Felt was chosen as it should slow the die down and keep it from rolling off and it could be the platform for the lazy susan aspect. Building it got us thinking more about materials and how the die moves.</p><h4>Evaluation &amp; Revision:</h4><p>We got our first feedback in-person from classmates. They suggested moving the home pocket so the user can reach the die more easily. We then had more discussions about the size and how to control the die. Upon receiving this feedback, we had additional conversations via email with PC and EU, who helped clarify expectations for ramp and turntable layout. They wanted a wall under the ramp to push the dice toward the user. To make space for the wall, we moved the ramp to the bottom-right corner, as seen in our updated sketch.</p><p>We also compared the two prototypes using three questions:</p><p><strong>Does it solve the problem?</strong> The cardboard box allowed us to consider size, but didn’t solve the original problem. The hole beneath the ramp meant that EU would still have to reach in to get the die back, which may be physically taxing. The felt turntable came closer to our end goal, because the floor turns and carries the die toward the user. However, we had no way of pushing the die closer towards EU. That gap was filled by PC and EU’s wall suggestion.</p><p><strong>Is it easy to use? </strong>This was difficult to judge, as we can only communicate asynchronously with EU and PC. During low-fidelity testing, we didn’t yet have a finished 3D model for them to print and try. Our classmates tested the prototypes; however, they don’t have EU’s grip or arm mobility. So we didn’t count their experience as proof that the device would be easy to use for EU.</p><p><strong>Would the user want it? </strong>PC and EU want a device that fits the way EU already plays. So, we tried to align as closely to the Makers Making Change post as possible, while maintaining a similar arrangement to EU’s current setup.</p><figure><img alt="Turntable and ramp layour provided by PC" src="https://cdn-images-1.medium.com/max/512/1*gb8c5Y047IHbYajHRD2uhw.png" /><figcaption>Turntable and ramp layout provided by PC</figcaption></figure><figure><img alt="Boran’s sketch with PC’s feedback" src="https://cdn-images-1.medium.com/max/512/1*2_lc2ott1O_7oIA1mnqYBQ.png" /><figcaption>Boran’s sketch with PC’s feedback</figcaption></figure><p>We knew it would be very important to maintain <em>autonomy </em>while we worked through this, which is why we followed up through every milestone. We didn’t want to make any assumptions about the ability or range of mobility the EU had. So, when we thought about things such as ramp height or diameter of the base, we were mindful to let the PC and EU take the reins and let us know what worked best for EU.</p><p><strong>What didn’t work? </strong>Along the way, we experimented a little with different ways to execute the turntable with an automatic integration. The PC had mentioned that it would be nice but optional, so, <em>naturally</em>, we had to see what that would result in.</p><p>Unluckily for us, when we tried working with circuit boards, it did not pan out how we would have liked. We used the Adafruit Crickit, which was very beginner-friendly, and began assembly. We used the MakeCode extension to program two simple commands into the board so that the motor we attached could receive them and rotate to the given degree endpoints. In the end, we realized the motor was not powerful enough, and this would only complicate things in a counter-productive way.</p><p>We scrapped it, and all it was all the better for it.</p><p>Something else we considered was the design principles Jacob O. Wobbrock outlines of adaptability and customization.</p><h3>High-Fidelity Prototyping with 3D Printing:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RPDcfFaycyr_eBrlhLdHRw.png" /><figcaption><a href="https://www.tinkercad.com/things/79iSQh4rCVk-3d-prototype-for-dice-roller?sharecode=uG8utH7REfZ7z9UyCPs8D-Jlh4gitpLZX61f-5JqsZ0">Our ramp-based 3D Model</a> made by Lucy</figcaption></figure><h4>Design Rationale:</h4><p>The turntable portion was based on <a href="https://makerworld.com/en/models/970297-electric-turntable-lazy-susan#profileId-941734">the design PC sent</a>. This user has limited mobility and wants to be able to roll dice for Dungeons and Dragons without needing to reach out to grab them again. The user emphasized a desire to physically roll the dice rather than having a machine roll for them, and this is similar to the design they requested. We decided to 3D print the parts for this prototype, as it would allow us to design everything in CAD before beginning the build process.</p><h4>Pinch Points &amp; Sharp Edges:</h4><blockquote>Are 3D-printed seams or moving parts smooth and safe?</blockquote><p>Some parts could be smoother, with the final print of the ramp being slightly bumpier than expected. However, the filament can be sanded so that the surface is a bit smoother.</p><h4>Activation Force &amp; Fatigue:</h4><blockquote>Can it be operated repeatedly without strain?</blockquote><p>Without the motorized component, we believe the device can be used initially without strain. However, we have not tested whether repeated use will induce fatigue.</p><h4>Material &amp; Cleaning:</h4><blockquote>Can the device be easily wiped down or sanitized? (Important for shared environments or school settings).</blockquote><p>Parts of the device that readily come into contact with human touch or outside materials, such as the ramp or lazy susan, are able to be wiped down. For a deeper clean, the ramp, walls, and lazy susan can be disassembled and wiped with store-bought cleaning wipes.</p><h4>Fail-Safe Operation:</h4><blockquote>What happens if a wire disconnects, a battery dies, or a print snaps?</blockquote><p>Parts can be reprinted and altered using our .STL file. Thus, if a print snaps, it can be replaced if the user has access to a 3D printer. In our case, PC is able to print and reprint as necessary.</p><h3>Limitations:</h3><p>At the time of 3D printing, other classes were using the printers, thus access became more limited. In addition, due to its size, we could only print the design on the Prusa 3D printers in the Digital Resource Center (DRC) at Macalester College. However, the DRC has only two of these printers. Thus, given the high usage and limited availability, we had difficulty assembling the high-fidelity prototype. This led to a significant delay in testing, meaning that we could not send the file to the end-user prior to November 9th, 2026.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8e691bfea51" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macalester-hci/designing-a-d-d-dice-roller-a8e691bfea51">Designing a D&amp;D Dice Roller</a> was originally published in <a href="https://medium.com/macalester-hci">Macalester HCI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating 3D Printed Tactile Maps for Bathrooms]]></title>
            <link>https://medium.com/macalester-hci/creating-3d-printed-tactile-maps-for-bathrooms-7b8d9327f9dd?source=rss----7ac5db827006---4</link>
            <guid isPermaLink="false">https://medium.com/p/7b8d9327f9dd</guid>
            <dc:creator><![CDATA[Dureti Gamada]]></dc:creator>
            <pubDate>Fri, 06 Nov 2026 19:00:09 GMT</pubDate>
            <atom:updated>2026-11-08T17:50:01.155Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Demo Video Link</strong></p><p><a href="https://youtu.be/WNl5LKV8ufk">https://youtu.be/WNl5LKV8ufk</a></p><p><strong>The Design Motivation</strong></p><figure><img alt="The 825 ARTS community center building" src="https://cdn-images-1.medium.com/max/1024/1*uCDF2xXXKfRIVaIc7i0lRA.png" /><figcaption><strong>825 Arts Community Center building</strong></figcaption></figure><p>A local community center one of our group members works at, called 825 Arts, requested tactile maps for their bathrooms. As a result, our group will create a tactile map to place on the wall next to one of the bathrooms. The goal of creating these maps is to help people who are blind or have low vision navigate the layout of a bathroom before stepping inside the bathroom. We want to avoid people having to touch around a bathroom space that may not be clean for navigation. We also want to ensure these maps are <a href="https://dl.acm.org/doi/pdf/10.1145/3148051">usable and useful</a>. So, we design a tactile map that considers color, layout, and overall design for usability and usefulness for people who are visually impaired. To begin, in order to design the map, a group member took pictures of the floor plans, as seen in figures 1 and 2, and even recorded the bathroom layout. These pictures and recordings were very helpful for our tactile map designs, as we will describe in the next sections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3sAVoaiD_-TOSVh0K-vrlw.png" /></figure><figure><img alt="A floor plan for bathroom 1 and 2 of the community center" src="https://cdn-images-1.medium.com/max/1024/1*c5rRqlU9akFkK0R2H1holA.png" /><figcaption><strong>Figure 1. Bathrooms one and two</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vk_eC50wgRmGoOtUebX7Jw.png" /><figcaption><strong>Figure 2. Bathroom three</strong></figcaption></figure><p><strong>What are Tactile Maps?</strong></p><p>Tactile maps are known for describing the layout of a particular area for people who are visually impaired. The area does not have to be a bathroom; there are tactile maps made for other areas such as parks. Typically, there is an associated legend with braille and text that explain the meaning of any symbol that appears within the tactile map. For example, if we create a tactile map for a bathroom, and the bathroom contains a sink, the tactile map will include some representation of a sink within the tactile map. Let’s say the sink is represented simply with a circle inside the map. Then, there will be a legend near the tactile map with a circle, and next to this circle, there will be braille and text that mean “sink.”</p><p>Maps can also be made from various materials, such as 3D printed plastic. For design motivation, our group went to google and the MSP airport to find tactile map designs. Figure 3 showcases a few of our design inspirations. Figure 3a and 3c contain braille within the map, next to each particular symbol. Figure 3b and 3c contain a separate legend to describe each symbol within the actual map.</p><figure><img alt="A bathroom tactile map with braille inside the map" src="https://cdn-images-1.medium.com/max/740/1*bEh5zRFHd8UwHVvAgjRn1w.png" /><figcaption><strong>Figure 3a. Example tactile map 1</strong></figcaption></figure><figure><img alt="A tactile map for a bathroom with a legend" src="https://cdn-images-1.medium.com/max/806/1*z_H0k6I1kVQrLXsJQ3YadA.png" /><figcaption><strong>Figure 3b. Tactile map example with a legend</strong></figcaption></figure><figure><img alt="A tactile map with different 2D symbols and a legend" src="https://cdn-images-1.medium.com/max/662/1*E5f5BoNWni4UR7baK9xufA.png" /><figcaption><strong>Figure 3c. Tactile map with 2D symbols</strong></figcaption></figure><p><strong>Designing our Map</strong></p><p>We needed to think about how our tactile maps would look. What would be the material we used? Would we use simple 2D objects, such squares, circles, and triangles to represent the various objects within a bathroom? Would the representations be 2D drawings that mimic the actual shape of the objects within the bathroom? Or, could we attempt to make 3D miniature representations of each object on our map? Furthermore, would we have a legend like figures 3b and 3c, or instead place braille directly next to objects with no legend like figure 3a? How do we represent “You are Here” to people? To determine some possible solutions, we decided to create many sketches individually, and come together as a group to discuss what designs we believed would be most useful and usable for blind people. In later sections we discuss feedback for changing our design based on consultations with the director of the Disability Resources at our college.</p><p>First, our group members individually created <a href="https://www.christineesoldo.design/field-notes/the-art-of-ideation">multiple sketches</a> of potential tactile map designs as seen in figure 4. Some were 2D, some were 3D object replicas. Some utilized random 2D shapes, and some involved placing a number next to each object inside the map with a corresponding legend explaining what object the number was next to. As a group, we quickly decided that we did not want to utilize simple 2D shapes, like a circle or square. We wanted to design the tactile map such that the objects inside our map mimicked the actual shape of the objects within the bathroom. However, we debated whether we should make 2D or 3D object replicas. As we thought what would be most useful for people who are blind, we decided to create tactile maps that had a 3D replica of the bathroom objects. The design of this 3D tactile map could be useful for visually impaired people to feel the actual 3D layout of the bathroom. So, we utilized the videos of the bathroom to determine the layout, heights, and placements of each object within the bathroom. Lastly, our professor explained that we should have high contrast in color between the floor and the objects within the bathroom, as some people are low vision and the high contrast is helpful.</p><figure><img alt="Some sketches for design ideas for the tactile map" src="https://cdn-images-1.medium.com/max/884/1*hVntSQOjjNtC69zCYAkowQ.png" /><figcaption><strong>Figure 4a. Initial sketch design ideas for tactile map 1</strong></figcaption></figure><figure><img alt="A paper drawing of many different potential tactile map designs" src="https://cdn-images-1.medium.com/max/776/1*exUux5lpb_qRFNjz-VFUyA.png" /><figcaption><strong>Figure 4b. Initial sketch design ideas for tactile map 2</strong></figcaption></figure><p>Next, we needed to decide which objects we would include within our map. All our objects were based around the wall enclosing them, and placed on top of the floor beneath them. Within the bathrooms, there was consistently a toilet, a sanitary bin, toilet paper, a sink, a soap dispenser, a paper towel dispenser, a trashcan, and two railings. Therefore, these are the objects that our maps will contain. However, since the trash can and towel were on top of each other, we decided that they will be grouped into one 3D object representation named ‘towel and trash.’</p><p>One bathroom had a baby changing station, and we ultimately decided to not include the baby changing station within the one tactile map we will produce. Finally, we needed to discuss how to represent a “You are Here” symbol. Our discussions led us to google images of other representations of doors in tactile maps as seen in figure 5. As such, we utilized a symbolic, rectangular door that is about 30 degrees open from the walls.</p><figure><img alt="Tactile map with “You are here” door symbol" src="https://cdn-images-1.medium.com/max/784/1*pkGvNd6d5L_X3tgZ0VKYXg.png" /><figcaption><strong>Figure 5. Tactile map with door representation</strong></figcaption></figure><p><strong>The First 3D Print</strong></p><p>We decided to 3D print a map for multiple reasons. One reason was that we wanted a map that was durable to hang and maintain on a wall, so we could not make the map out of fragile materials such as paper or cardboard. Another reason was that we had access to a 3D printer at our college, and one of our group members was experienced with 3D printing.</p><p>We 3D printed an initial, low fidelity prototype to quickly visualize how our design may appear. As such, it includes the walls and objects, but does not include the floor or legend. To model the floor, we used a white paper background. At this stage of the process, we were not confident on how to model a way to define the objects. So, to make this design as usable as possible, we decided to write with pencil around the outside of the walls, close to the object within the wall for quick lookup. Our first print lacks a sanitary bin.</p><p>After our first print, we noted a few issues with the design. First, we realized that our representation for the towel and trash, which was a shallow indent within the walls, was difficult to feel. Second, the toilet paper was similarly difficult to feel, as it was a small protrusion out the walls. Lastly, none of the bodies of the objects were taller than the walls themselves. We believed that this lack of height did not sufficiently emphasize the presence of the objects within the bathroom. So, we made sure our next 3D print would lower the walls and raise all objects above them. The one exception is the rails, which we believe should be similar to the walls.</p><figure><img alt="A low fidelty 3D print of a wall with objects inside the bathroom, and text explaining the obejct around the walls next to the object." src="https://cdn-images-1.medium.com/max/942/1*W9cddMx-c9n_--CyLtCrOw.png" /><figcaption><strong>Figure 6. First 3D print</strong></figcaption></figure><p><strong>The Second 3D Print</strong></p><p>The second print focused on creating a more specific, complete design. The print uses a high contrast design, containing a black background and light brown objects, for people with low vision. The aforementioned objects were 3D printed to mimic the look of the actual object within the bathroom, as seen in figure 7. However, as we brainstormed the object designs before 3D printing, we ran into another problem: the sanity bin, toilet paper, soap dispenser, and towel with trashcan all were simplified to be a cube or rectangular prism. With such similar shapes, how would someone distinguish between them in a potential legend? Well, we decided to place an ‘X’ on the sanitary bin to distinguish this object. For the rest, we decided to ask for help as described in the next section. One additional question was whether we should keep the railings or not within the design. As the railings take up a notable amount of space, we decided to include them.</p><p>The actual design of the 3D printed objects on the map tried to mimic not only the shape, but also the spatial location of the object within the bathroom. This even includes whether the object is sunk into the wall, or sticking out of it. For example, the soap dispenser is completely sticking out of the wall, whereas the toilet and towels with trash can are sunk into the wall. This is mimicked by the design in figure 8.</p><figure><img alt="A higher fidelty tactile map with a floor, walls, and objects inside the bathroom." src="https://cdn-images-1.medium.com/max/922/1*xkhLtw-fewjD9d6AdfhyeA.png" /><figcaption><strong>Figure 7. Second 3D print</strong></figcaption></figure><p><strong>First User Test</strong></p><p>After completing our initial 3D print design, we wanted to talk to people who were visually impaired or who had experience with making useful and usable objects for blind people. As a result, we reached out to the director of the Disability Resources at our college for feedback. We formulated multiple questions that arose after the second 3D print. This included: How do we incorporate braille onto the map to identify each object within these single-person bathrooms? Should we place the braille inside within the map next to each object/shape, place the braille outside the map next to each object, place a number next to each object with a corresponding legend describing the object, or simply place each object within the map on a separate legend with braille describing the shape’s meaning? We wondered which would be more usable for visually impaired people. Lastly, how big should the map be?</p><p>The director recommended we place braille outside of the map, in a legend for multiple reasons. One reason is that people will naturally search for a legend, so without one, the design may be unnecessarily confusing. Additionally, the braille may be confused for objects within the actual bathroom. Next, we asked about how to distinguish between the cubic and rectangular prism objects. The director recommended putting a “TP” on the toilet paper, as not all blind people use braille. The director also recommended cutting out the rectangular prism that represents the towel and trash, as well as removing its front face. This is because we wanted to mimic the paper towel dispenser and trashcan design, which in the bathroom involves a paper towel dispenser directly above a trash can, with a gap in between the two objects. The director mentioned that we can scale down the object pieces on the legend, as they do not have to feel exact but must be understandable. Additionally, since this map contains English text, we will place the legend on the left. This is because English is read left to right. Lastly, for recommendations for the size of the overall map, the director specified that we should determine how much space we have to work with on the wall. After seeing the wall where the tactile map would be placed, we learned that we do not have much space, so we must scale our tactile map down to fit the wall. This will involve scaling down the legend objects.</p><figure><img alt="A drawing of a potential 3D print design" src="https://cdn-images-1.medium.com/max/1024/1*85vxykF_PkZXQLGsxL3eXg.png" /><figcaption><strong>Figure 8. Redesign of 3D print based on Director of Disability Resources</strong></figcaption></figure><p>We created a sketch redesign of the map based on the feedback as seen in figure 8. The sketch contains the legend, along with the updated 3D shapes for the towel with trash and toilet paper. The sketch also specifies how tall every object should be relative to the walls encompassing them. Tier 1 is the shortest, and tier 4 is the tallest.</p><p>The doorway is important. We considered highlighting the rectangle representing the door yellow, as seen in figure 8. However, we ultimately decided against this, in order to keep the tactile map more uniform color-wise. We maintain a design of a black background with white objects. After consulting with the <a href="https://www.access-board.gov/ada/guides/chapter-7-signs/">ADA guidelines</a>, we learned that the braille must be 0.025’’ to 0.037’’. Our final braille design will ensure this height. Additionally, we decided to color the braille and text white in addition to the objects, so that the braille and text also contrasted against the black background. Unlike figure 8, our final redesign will contain a floor that is black and a door and walls that match the white of the objects. Also unlike figure 8, we also decided for our next print that we would mimic the toilet paper roll design by having two toilet paper rolls and a poll as the actual bathrooms do.</p><p>To 3D print the braille, a group member found a program to generate a braille design for a 3D printing program that was created by a blind person. The braille is not the typical half sphere, but instead a half sphere with its head partially removed.</p><p><strong>Gina User Test</strong></p><p>We contacted Gina Fugate, who works at Maryland State School for the Blind. She is visually impaired, so she is a part of a user group that may utilize tactile maps. Therefore, her evaluation of our design was significant. Her evaluation involved utilizing a black and white combination for high contrast to comply with triple A contrast check standards. She suggested ensuring our objects were not shiny so as to avoid a glare from light. She noted that, in general, braille sometimes can be inaccurate and lack durability. Lastly, she suggested that the depth of certain objects, such as the toilet, could hold too many germs in the 3D print. As a result of this feedback, we ensured our final design was black and white, avoided shiny designs, and modified the depth of objects to avoid germs.</p><p><strong>Surface Covering</strong></p><figure><img alt="A 3D print of the legend of our tactile map, containing all the items within the bathroom in the legend" src="https://cdn-images-1.medium.com/max/690/1*_F2MCEZxRBGXOB4hUdBxag.png" /><figcaption><strong>Figure 9. Third 3D Print</strong></figcaption></figure><figure><img alt="A small, PETG 0.4mm 3D print of the toilet portion of the legend" src="https://cdn-images-1.medium.com/max/710/1*FmtNj6RcZ3f6tSFbZ8V8Cg.png" /><figcaption><strong>Figure 10: 3D Print PETG 0.4mm</strong></figcaption></figure><p>We printed the legend portion of the 3D print, as seen in figure 9. After feeling the print, we realized that the braille was a little rough. We decided that we needed to have some surface covering to smooth out the braille to feel better for reading. We contacted a chemistry teacher for Ethyl Acetate, as suggested in this <a href="https://www.creality.com/uk/blog/how-to-smooth-3d-prints">article</a>, for PLA filament smoothing. However, we did not hear back. In figure 10, we 3D print a small portion of the tactile map for testing methods to smooth. This included heating the braille, adding Mod Podge to the braille, and sandpapering the braille. As a result of our tests, we realized that sandpaper resulted in the smoothest braille.</p><p><strong>The Final Design and Conclusions</strong></p><figure><img alt="A 3D printed tactile map of a bathroom, with its legend" src="https://cdn-images-1.medium.com/max/1024/1*opKajJJWfs1Sj0mWCiZKxg.jpeg" /><figcaption><strong>Figure 11: Final 3D Print</strong></figcaption></figure><p>We printed our high fidelity prototype in PLA 3D filament with a 0.2 mm nozzle. We used sandpaper to smooth out the braille. The final design is seen in figure 11.</p><ul><li>Strengths: Full legend with map, high legibility, high color Contrast, intuitive layout</li><li>Weaknesses: Braille is rough, we used sandpaper to smooth it out to the best of our abilities.</li></ul><p><strong>Ethical considerations</strong></p><p>Ethical considerations involve a lack of user testing from people who are visually impaired. Although we did receive helpful user testing from Gina, this user testing was over Zoom so she could not touch the map herself. In-person user testing and communication with more people who are visually impaired would have helped us create a better design for blind people.</p><p><strong>Future Exploration</strong></p><p>Having finalized the design, we took a step back to consider a broader question: what other, more diverse forms could tactile maps take? Most of our design choices, such as the top-down floor plan, legends, and symbols are derived from visual maps, which follow their own established conventions. However, we explored several other possibilities; some could be tested using existing tools, while others would require further development. These further explorations include:</p><ul><li>Incorporating a route into the map (a raised line starting at the doorway and tracing the sequence in which items are typically used within the bathroom). Given the small size of this particular bathroom, adding a route would only create unnecessary visual clutter.</li><li>Audio-tactile maps. As the director of a disability resource center pointed out, this would be particularly helpful for individuals who do not read Braille.</li><li>Shape-changing maps. Devices such as pin-actuated displays, which use thousands of small, retractable pins to render maps and images, are already in use at public transit kiosks in Busan, South Korea. A single such display could represent all the rooms at 825 Arts, eliminating the need for individual, static maps for every restroom.</li><li>Textures for tactile maps. Useful for exploring materials that are most effectively perceived through touch. For instance, a smooth surface for some areas, a ribbed texture for some, and a dotted texture for others.</li></ul><p><strong>References</strong></p><p><a href="https://dl.acm.org/doi/pdf/10.1145/3148051">https://dl.acm.org/doi/pdf/10.1145/3148051</a></p><p><a href="https://www.christineesoldo.design/field-notes/the-art-of-ideation">https://www.christineesoldo.design/field-notes/the-art-of-ideation</a></p><p><a href="https://www.creality.com/uk/blog/how-to-smooth-3d-prints">https://www.creality.com/uk/blog/how-to-smooth-3d-prints</a></p><p><a href="https://www.access-board.gov/ada/guides/chapter-7-signs/">https://www.access-board.gov/ada/guides/chapter-7-signs/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b8d9327f9dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macalester-hci/creating-3d-printed-tactile-maps-for-bathrooms-7b8d9327f9dd">Creating 3D Printed Tactile Maps for Bathrooms</a> was originally published in <a href="https://medium.com/macalester-hci">Macalester HCI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for One-Handed Gaming—The Sick Stick]]></title>
            <link>https://medium.com/macalester-hci/designing-for-one-handed-gaming-the-sick-stick-9641fa91a517?source=rss----7ac5db827006---4</link>
            <guid isPermaLink="false">https://medium.com/p/9641fa91a517</guid>
            <dc:creator><![CDATA[Hayden Pierce]]></dc:creator>
            <pubDate>Mon, 02 Nov 2026 21:00:25 GMT</pubDate>
            <atom:updated>2026-11-10T02:43:56.188Z</atom:updated>
            <content:encoded><![CDATA[<p>Traditional gaming controllers are usually designed for people who can use both hands, which can make gaming difficult for someone with only one usable hand. For our second design sprint, we decided to create the Sick Stick, a one-handed gaming controller that combines a large joystick for movement, a smaller joystick for looking around, and buttons along the handle for other in-game controls. Our goal was to make games, for example, Minecraft, easier to play using just one hand without having to completely change how the game is played.</p><p>At the beginning of the assignment, most of us were interested in creating accessibility in gaming. We all either are passionate about gaming or are already studying ways to make modern technology more accessible. There were already many existing products that would create accessible gaming, such as large controllers with customizable buttons or pads with rollers rather than a controller.</p><p>Not only did we do a lot of research to ensure we weren’t simply copying an existing product, but we also wanted to narrow down our scope of users. We wanted to focus on a group that would benefit from a physical product. One issue we had was that some user groups, such as the blind or the deaf, would benefit more from a software product rather than a hardware product, which was out of scope for this assignment.</p><p>There were two groups of people we considered: people who do not have fine motor control and people who only have one usable hand. We chose to focus on people who only have one usable hand, as we knew people with this problem, and it would be easy for us to test as well. It can also broaden our scope of users; even able-bodied people can use a one-handed controller if they wish!</p><p>We also realized that just remapping buttons in a game wouldn’t do enough to solve the problem since players still need to use multiple controls at the same time. We wanted our controller to make that easier without completely changing how someone plays a game.</p><h3>From Ideas to Our First Prototypes</h3><p>A good lo-fi prototype starts with a basic idea and a few bullet points. Our design plan was to build an <em>efficient</em> one-handed controller for amputees or people with injured arms. Three designs came to mind: a robust remote, a big joystick, and an input-riddled mouse. Our main design philosophy was <em>simple but loaded</em>. We sketched out several versions of these controllers, and we got to work on our duct tape and cardboard lo-fi prototypes.</p><figure><img alt="Pencil sketch of our original joystick design with buttons on the handle and a rectangular base." src="https://cdn-images-1.medium.com/max/402/1*UebGUNicxmDBt3PG3oqY_Q.png" /><figcaption>One of our original sketches for the larger joystick before we started building our prototype.</figcaption></figure><p>This part of our creative process connects to the <em>divergent and convergent thinking</em> that Amy Ko talks about in <a href="https://faculty.washington.edu/ajko/books/design-methods/design"><em>How to Design</em></a><em>. </em>We started by coming up with a bunch of different ideas, like the trackball, mouse, and joystick, and followed up by narrowing things down to the ones we wanted to actually build and test. This helped us compare our different prototype ideas instead of just going only with our first idea that came to mind.</p><p>For those unfamiliar with lo-fi prototyping, it is a design technique where designers keep ideas high and costs low. We used <em>rudimentary </em>tools such as paper, pencil, glue, cardboard, strings, and markers to test what our product will <em>use—like before</em> committing to complicated and time-consuming tools such as computer code or motherboard chips. It’s a great way to pump out a <em>large</em> number of designs and iterate on those that <em>work </em>to make them <em>work great</em>.</p><p>For our lo-fi prototypes, we chose to stick to our big joystick and input-riddled mouse ideas. We gathered in Macalester College’s idea lab and got crafting! For the big joystick, we used toilet paper tubes, cardboard, and duct tape for the stick as well as Su&#39;s—our lead engineer&#39;s—microcontroller joystick and styrofoam. We topped it with googly eyes for charm, Play-doh for the top’s finish, and a pom-pom for the smaller thumbstick. Lastly, we added plastic buttons on the back to simulate game buttons. While the size of the joystick made it plop slightly over time, it was fully working and ready for user testing.</p><figure><img alt="Our first joystick prototype was made with cardboard, yellow tape, google eyes, green Play-doh, and a foam base." src="https://cdn-images-1.medium.com/max/1024/1*CLltQJUzzMU3_djqrN7ttw.jpeg" /><figcaption>Our original lo-fi joystick prototype made with cardboard, tape, and other materials.</figcaption></figure><p>The input-riddled mouse’s creation was a tad less sophisticated than the big joystick, but it was still as effective. We divided a large piece of cardboard into eight-or-so equal sides to turn it into an arc. Through an overuse of duct tape, we combined it with a flat cardboard base and smaller pieces of foam to act as buttons: two for the thumbs and three for the middle, ring, and pinky fingers, respectively. Of course, we also added a pom-pom for the thumbstick!</p><figure><img alt="Our mouse-shaped cardboard prototype with yellow tape and cardboard buttons along the top and sides." src="https://cdn-images-1.medium.com/max/1024/1*UqIv1tK83pZ06CneZPh4PA.jpeg" /><figcaption>Our second lo-fi prototype, which used a mouse-like design with buttons along the top and sides.</figcaption></figure><p>Cobbling these designs together took around an hour—way faster than if we had dived straight into the hi-fi prototype and tried to figure out 3D modeling, components, and wiring on the first day. The lo-fi prototypes helped us figure out <em>how many</em> and <em>which</em> components we needed, as well as the general dimensions of the designs before committing to them. DaVinci sketched out the Mona Lisa before painting it, and so did we!</p><h3>Testing Our Initial Designs</h3><p>Once we finished our lo-fi prototype designs, we next had to get feedback from a real user. We met with a Macalester football player who had recently injured his arm to test our initial design. We wanted to see how comfortable and practical our controller was to use with one hand, especially when it came to things like the grip, button placement, and joystick movement.</p><p>One of the biggest things we learned was how important the natural hand position is when using the controller. Our user suggested moving some of the buttons more toward the side instead of directly behind the joystick, since that is where his fingers naturally rested while holding it. He also mentioned that the pinky finger could be harder to use, so having fewer buttons for that finger could make more sense. We also talked about having two columns of four buttons, with the less often used controls being toward the bottom to avoid accidentally pressing them while in an intense gaming session.</p><figure><img alt="A hand holding our cardboard joystick prototype to show how the fingers fit around it." src="https://cdn-images-1.medium.com/max/1024/1*u-QorI4H8JLwXYIccbbJKw.jpeg" /><figcaption>How our original joystick prototype fit in someone’s hand during our early testing.</figcaption></figure><p>Also, our user brought up the movement and sensitivity of the joystick itself. Since our design has you moving the entire controller like a joystick, we needed to pay extra attention to how much movement would actually be comfortable for different users. He mentioned that some people might prefer a smaller range of motion, while others might want more flexibility if their mobility allows. This made us think about whether we could make the joystick adjustable rather than having the same for everyone. We also talked about how important it would be for the joystick to return to a neutral position when it isn’t being moved since we wouldn’t want the controller to accidentally register incorrect movements while gaming.</p><p>We also got some feedback about the overall size and stability of our joystick. One concern was that it might be too tall and uncomfortable during longer gaming sessions. We also needed to figure out how to keep the base from moving around while someone was playing. These were things we wanted to keep in mind when figuring out the dimensions of our hi-fi prototype.</p><p>After looking at both of our lo-fi prototypes and also the feedback we received, we decided to stick with the larger joystick design instead of the mouse. Yes, the mouse was an interesting idea, but we had some concerns about how natural it would feel to control the smaller joystick with an index finger, and moving it to the thumb could cause its own comfort issues. With the larger joystick, we liked the idea of using the entire hand for movement while still having the smaller joystick and the other buttons on top of the controller. Our design wasn’t perfect, but we felt like it gave us a good starting point to work off of based on the feedback we received.</p><h3><strong><em>Using Feedback to Improve Our Design</em></strong></h3><p>One thing we struggled with after our lo-fi testing was fitting enough buttons onto the handle without making it too crowded or uncomfortable. With some help from our user, we decided to move the pause and home buttons down to the base. Since those aren’t used as much during gameplay, we figured it’d be fine to have them a little farther away. This would also mean less wiring and weight inside the handle, making it more comfortable to hold.</p><p>We also wanted to keep in mind that different users might have different needs. We talked about possibly making some of the buttons adjustable so people could move them to wherever feels most comfortable. We also wanted to consider left-handed users as well. We probably won’t have all of this working on our current prototype, but it’s something we’d like to look into as we continue.</p><p>This ties into <a href="https://doi.org/10.1145/3148051"><em>ability-based design</em></a>, which we learned about in class. Basically, instead of expecting people to adapt to a regular controller, we wanted our controller to better fit what they could already do. This was a big reason why we focused on our user’s natural hand position and considered making some parts adjustable for users.</p><h3>Bringing Our Controller to Life</h3><p>Once we knew what direction we wanted to go, it was time to start building our hi-fi prototype! We used 3D modeling to design the handle and laser cutting to make a base for our components. The handle fits around the larger joystick so moving the entire thing controls movement, while the smaller joystick on top is meant for looking around. Getting everything to fit was harder than we thought, especially the top joystick, so we had to adjust and reprint that piece a few times.</p><p>Something else we noticed was that the 3D printing wasn’t necessarily going to work perfectly the first time. We had to make quite a few adjustments to the actual size of our controller handle to make sure everything would fit properly. Rachel worked on adjusting the handle’s length and width and also figuring out how the two halves would fit together around the joystick at the base. There was a bit of trial and error, since its hard to gauge the best size and structure for the joystick, but we did use some strategies to reduce the amount of time spent printing.</p><p>We were able to find a joystick grip model on Printables, and we were able to use it as a basis for our model. Surprisingly, the top plate of the model almost fit the thumbstick we wanted to use! We just needed to cut a deeper hole on one of the sides so that the entire part completely fit.</p><p>Printing the main joystick over and over again would take a lot of time and materials. That’s why we printed out one half at a time: we could get a decent idea of what size would provide the most comfortable grip.</p><p>We also created a few “test prints” before committing to the finalized print. One example of this is with the buttons on the side of the grip. We wanted to insert buttons that are 16mm in diameter along the side of the controller. So we printed out a small square that had a 16 mm hole to make sure the button fit. It was good that we did this, because the button didn’t fit! We increased the hole to 16.8 mm in diameter, and the button fit completely afterwards. If we hadn’t tested this, we would’ve wasted a lot of time and materials.</p><figure><img alt="A red button fitted into a small gray 3D-printed piece to test the buttone hole sizes." src="https://cdn-images-1.medium.com/max/1024/1*lms9EGS_8nLRif17ol7uYQ.jpeg" /><figcaption>One of our test prints to make sure the buttons would actually fit.</figcaption></figure><p>But of course, printing issues were always inevitable; for example, one print basically turned into a tangled mess of plastic, also known as spaghettification. This wasn’t ideal, especially considering how long some of these prints already took! Although we were still figuring out some of the measurements and how everything would fit together, it definitely had showed us how much really goes into the physical side of making a product compared to just a simple cardboard prototype.</p><p>Another challenge was figuring out how to fit all the electronics inside our controller. Our main joystick sits on a breadboard connected to a microcontroller, so we needed enough room for the wiring and buttons while still making the handle comfortable to hold. It sounded pretty simple on paper, but fitting everything together was definitely tougher than we thought!</p><figure><img alt="Hands fitting a joystick, breadboard, and microcontroller into our laser-cut controller base." src="https://cdn-images-1.medium.com/max/1024/1*5XKdP-2K52Rs2oAsvr9WKg.jpeg" /><figcaption>Fitting our joystick and electronics inside the laser-cut base.</figcaption></figure><p>Another thing we had to figure out was how to keep the base from sliding around while playing. At first we thought about weighing it down with coins or something similar, but that would take up space needed for wiring and probably won’t even keep it stable. We decided a desk clamp would make more sense since it could keep everything in place without adding extra weight. We definitely don’t want the whole controller sliding across the desk while trying to avoid a Creeper!</p><p>We needed to figure out how we were going to actually connect our controller to a computer and make it work with a game. For our demonstration we decided to use Minecraft since there are quite a few different controls that would normally require both hands when playing on a computer. We ended up using CircuitPython with our Adafruit KB2040 microcontroller to send keyboard and mouse inputs through a USB-C cable. After quite a bit of trial and error with the wiring and code, we got the larger joystick working for movement, one of the handle buttons working for attacking, and the red base button working for pausing the game. We also got the smaller joystick on top responding in Minecraft, but we were still running into some issues with the camera drifting or moving on its own, along with the downward-looking motion having some signaling issues. Pretty ironic for the Sick Stick to have stick drift! We were also waiting on an additional part called an MCP23017 expander to connect the rest of our handle buttons. It definitely wasn’t everything we originally wanted working yet, but it was still pretty cool seeing our controller actually control a player in Minecraft!</p><p>We used Claude and ChatGPT throughout the process to help us better understand some of the wiring diagrams and instructions for our different electronic parts. We also used them to help with writing and troubleshooting our CircuitPython code, especially when running into problems with the smaller top joystick. They were extremely helpful for figuring out what to try next when we would get stuck, despite us still needing to test everything ourselves since many problems we ran into were for the actual wiring rather than just the code itself.</p><h3><strong><em>Putting Our Controller to the Test</em></strong></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FXIcupwqVxd8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DXIcupwqVxd8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FXIcupwqVxd8%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e8af819d53a6e12821ed67c8bb6af5cb/href">https://medium.com/media/e8af819d53a6e12821ed67c8bb6af5cb/href</a></iframe><p>Since we were still waiting on our MCP23017 expander and having issues with the smaller joystick, not every control was working for our hi-fi testing. We still had our user try the controller in Minecraft using some Wizard of Oz testing. He could move with the larger joystick, attack or break blocks using a handle button, and pause with the red base button. For the unfinished controls, one of our teammates helped from the computer while he played. This let us test how the controller actually felt during gameplay despite some of the wiring and programming still needing work.</p><figure><img alt="Our user sitting down and holding the 3D-printed Sick Stick controller during testing." src="https://cdn-images-1.medium.com/max/1024/1*ejyQglVFhmug_rWI7GJZHQ.png" /><figcaption>Our user testing out the Sick Stick during our Minecraft demonstration.</figcaption></figure><p>Overall he really liked how far our controller had come since he first tested the cardboard prototype with googley eyes! One of his biggest suggestions was to move the handle buttons closer together since reaching some of them could still feel a little bit far. We talked about using slightly smaller buttons and increasing the total to ten for our next prototype we’re planning for Design Sprint 3. He also noticed that some parts of the controller were a little loose, but this was mainly because we had temporarily taped parts of it together to get everything somewhat ready for testing. A lot of his feedback was related to things we already knew needed more work, but it was still very helpful and lots of fun to see how the controller actually felt and held up while playing a real video game.</p><p>One limitation of our testing was that we only had one user test this version of our controller. His feedback was extremely helpful to our building process, but we also realized that someone with a temporary arm injury might have different needs than someone who permanently has only one usable hand or arm. We would definitely like to test with more users who have different levels of mobility and accessibility during Design Sprint 3 if possible, especially since our current design is mainly meant for right-handed people. This could help us narrow down on what works for different people instead of just saying one design fits all.</p><p>We also tried to involve our user during the entire process, which ties into <a href="https://doi.org/10.1145/2723869"><em>design for user empowerment</em></a><em>. </em>His feedback helped us figure out things like button placement and joystick movement, and we’ll keep using it as we make changes for Design Sprint 3.</p><figure><img alt="A hand holding our black 3D-printed controller with red side buttons, a top joystick, exposed wires, and tape holding the whole thing together temporarily." src="https://cdn-images-1.medium.com/max/1018/1*uXTJT_xlqgI1Y6CCzeMgkA.png" /><figcaption>A closer look at our current Sick Stick prototype and how it fits in someone’s hand.</figcaption></figure><h3><strong><em>Final Thoughts and Future Improvements</em></strong></h3><p>We still have quite a few things we want to improve as we move into Design Sprint 3! Our biggest priority is getting the rest of the buttons working once our MCP23017 expander arrives. Based on our user’s feedback, we’re also planning to use ten smaller buttons that are closer together. We also want to fix the top joystick, improve our wiring, and make the controller more stable. Eventually we’d like to look into a left-handed version or even a D-pad. We’ve learned a lot from building and testing this version and we’re excited to keep improving it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9641fa91a517" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macalester-hci/designing-for-one-handed-gaming-the-sick-stick-9641fa91a517">Designing for One-Handed Gaming—The Sick Stick</a> was originally published in <a href="https://medium.com/macalester-hci">Macalester HCI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesigning the Macalester Idea Lab Site]]></title>
            <link>https://medium.com/macalester-hci/round-parakeets-redesigning-the-macalester-idea-lab-site-9baefc5e3851?source=rss----7ac5db827006---4</link>
            <guid isPermaLink="false">https://medium.com/p/9baefc5e3851</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Moyartu Manley]]></dc:creator>
            <pubDate>Fri, 09 Oct 2026 22:18:46 GMT</pubDate>
            <atom:updated>2026-10-28T19:46:59.401Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://medium.com/u/f51e27ba4584">Huthaifa Mohammad</a>, <a href="https://medium.com/u/f21e3d36eb5e">leaentity</a>, <a href="https://medium.com/u/bd3805f560f8">Moyartu Manley</a>, <a href="https://medium.com/u/8ec7ed3f9421">Owen Blanchard</a></p><p>Linked is our high-fidelity <a href="https://www.figma.com/proto/WrWPn9NhDahRzi6uBCkIwg/IdeaLab-Website-Prototype?node-id=14-1237&amp;t=uuCiX6eWAn7tqLrh-0&amp;scaling=min-zoom&amp;content-scaling=fixed&amp;page-id=1%3A2&amp;starting-point-node-id=14%3A1237">Figma</a> and <a href="https://www.macalester.edu/160-hci-round-parakeets/">WordPress</a> prototypes.</p><h3>Introduction</h3><p>On the second floor of Macalester’s DeWitt Wallace Library exists the Idea Lab, a quirky makerspace utilized by a multitude of groups: students, faculty, community members, alumni, etc. The space has a unique charm that makes you want to get your hands dirty; to create and innovate. However, navigating the space requires recognition and familiarity with the resources they offer and where supplies are located. While you can always ask the friendly student workers for directions on where the art supplies are, we aim to lessen the load on both the student workers and coordination staff. Their<a href="https://www.macalester.edu/entrepreneurship-and-innovation/idealab/"> current website</a> seeks to accomplish that task, but in our opinion, it isn’t currently meeting that threshold.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bPULYcZa6M9WaP_aeD-I3g.jpeg" /></figure><h3>From Research to Design Decisions</h3><p>Our conversations with Idea Lab staff reveal that the website serves a much broader audience than we initially expected. Students and faculty are frequent users, but the site also reaches alumni, prospective students, families, local entrepreneurs, and visitors from other colleges.</p><p><strong>So, how can the website serve people who already know the Idea Lab while also welcoming those encountering it for the first time?</strong></p><p>We also noticed a balance between identity and utility. Staff described the Idea Lab as a “happy place” built around creativity, curiosity, and experimentation. They wanted the website to communicate that the space is more than a place for crafting but also a place to explore ideas and solve problems.</p><p>At the same time, many visitors come to the website with practical questions: <em>What resources are available? Where can I find them? What events are happening? How can I reserve a space or contact someone?</em></p><p>This pushed us toward a design that could communicate the Idea Lab’s identity without getting in the way of common tasks. We prioritized clear access to resources, events, reservations, and staff information while using color and the order of different sections to offer smoother navigation.</p><p>We focused on making the site:</p><ul><li>Easy to navigate</li><li>Visually inviting</li><li>Familiar to use</li><li>Accessible to different users</li></ul><p>These principles became the starting point for our first prototypes.</p><h3>Testing our Paper Demos</h3><p>We had two paper prototypes. One paper prototype featured a mini-map of the idea lab for locating resources, for reference we will call this the Mini-Map Prototype. The other paper prototype featured a resource search bar, thus we will refer to it as the Search-Bar Prototype. We performed a user evaluation for our aforementioned prototypes with the following user groups: alumni and faculty.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-SrseqHLwMSEiufJCDLobA.jpeg" /><figcaption>Our search-bar prototype</figcaption></figure><p>(Alumni User Evaluation) Search-Bar Prototype:</p><p><strong>Reserving a Space: </strong>She checked the calendar, tapped it, and easily navigated the pop-up to reserve space and create a workshop. She found the reservation workflow straightforward and successfully reserved the space.</p><p><strong>Checking for Resources: </strong>She looked for a search bar. When struggling to locate a specific resource, she scrolled down the resource grid.</p><p><strong>Contacting the Idea Lab: </strong>She disliked the contact box because it failed to send a copy of the message back to the sender, leaving no paper trail. She strongly preferred locating a direct staff email for communication.</p><h4>(Faculty User Evaluation) Search-Bar Prototype:</h4><p><strong>Reserving Tables for Class: </strong>User stated that none of the interface buttons explicitly mentioned “class,” making the reservation options feel overly student-centric. As a result, they would default to emailing the Idea Lab manager.</p><p><strong>Checking Availability of Yarn: </strong>The user clicked the “yarn” resource item. They felt lost by the extended description layout and confused about how tutorial thumbnails were presented on the overlay. They clarified that they did not need an exact inventory count of yarn, just a baseline assurance that yarn would be available when hosting the class.</p><p><strong>Contacting the Idea Lab:</strong> The user<strong> r</strong>ejected the contact form entirely, reaffirming a preference for direct email communication with staff.</p><h3>Mini-map prototype</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zRRj3-lom03tRRko5iO2oA.jpeg" /><figcaption>Our mini-map prototype</figcaption></figure><h4>(Alumni User Evaluation) Mini-Map Prototype:</h4><p><strong>Finding Workshops/Activities: </strong>Our alumni user successfully navigated to “Events and Calendar” and pressed the calendar button. However, she found the resulting pop-up to be too small and frustrating, preferring a full-page view with a clear back/exit button.</p><p><strong>Finding Equipment: </strong>Initially bypassed the resource map to search externally on Google (<em>“sewing macalester”</em>). When guided to the interface, she experienced choice paralysis. She disliked the resource map, noting it wasn’t intuitive. She preferred a global search bar or clicking map pins that expand into dropdowns, stating that sorting through every individual pin was tedious.</p><p><strong>Contacting the Idea Lab: </strong>She naturally looked toward the staff section to find contact emails.</p><h4>(Faculty User Evaluation) Mini-Map Prototype:</h4><p><strong>Reserving Tables for Class: </strong>User noticed the map first due to visual prominence, tapped a pin to view resources, then clicked out before locating the reserve button. They wanted the ability to reserve specific spaces directly from the map pins (for example, reserving a sewing station for a class context). They disliked excessive screen overlays and confusing terminology. They specifically took issue with booking a “room,” because they view the Idea Lab as an open space. They requested clarity on enclosed vs. open spaces, suggesting using a complete floor plan of the lab, and emphasizing the need to view seating capacity without clicking through too many layers.</p><p><strong>Checking Availability of Yarn: </strong>The user explicitly stated they would not use a mini-map to locate a specific resource, finding map pins inefficient for this purpose.</p><p><strong>Contacting the Idea Lab: </strong>The user stated they would email the Idea Lab manager directly out of habit from past experience.</p><h4>Usability Takeaways:</h4><p><strong>Navigation Preferences: </strong>Both user groups showed frustration with map-based interfaces for resource hunting. If a map is kept, users want it to function logically. Users would want a complete layout showing seating capacity and open zones rather than pins.</p><p><strong>Pop-ups and Overlays: </strong>Alumni found small pop-up windows frustrating and wanted full-page views with clear exit buttons. Faculty similarly complained about excessive screen overlays that clutter the interface and cause confusion.</p><p><strong>Communication: </strong>Alumni disliked submission forms because they didn’t send a confirmation copy back to the user, leaving no paper trail. Faculty bypassed the digital forms and contact interfaces entirely, preferring to email staff directly based on habit and trust.</p><p><strong>Student vs. Faculty Mental Models: </strong>Faculty noted that reservation options felt entirely student-focused and objected to the term “room” because they view the Idea Lab as an open space. Faculty do not need exact inventory counts, but rather assurance of availability for a class. Students, however, need quick, clear locational data.</p><p>From these takeaways, we prioritized using a search bar as our primary method for locating resources. Given that there was existing user trust in emailing, we aimed to make the email address of the Idea Lab and its managers more visible. Finally, we worked to use terminology that could apply to both student and faculty mental models.</p><h3>Iterating the Design</h3><p>Testing the two prototypes made it clear that our next iteration did not need more features; what we needed was clearer priorities. Several interactions we had initially considered useful, particularly the mini-map and layered pop-ups, created additional steps between users and the information they were looking for. At the same time, some of the simplest behaviors, such as searching for a resource or emailing a staff member directly, consistently matched how our participants already expected to use the site.</p><p>We combined the strongest elements of both and reconsidered the interactions that had caused friction, rather than choosing one prototype wholesale. Our final iteration focused on three areas: making search the primary tool for resource discovery, reducing unnecessary overlays and navigation layers, and making direct communication with Idea Lab staff more visible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cejKmWyCyLd7izVsRajKMQ.png" /></figure><h3>Building the High-Fidelity Prototype with AI</h3><p>After testing our paper prototypes, we had a better, clearer idea of what we wanted our next iteration to accomplish. We knew that search needed to be the primary way for users to find resources, that we wanted to reduce unnecessary pop-ups and overlays, and that direct communication with Idea Lab staff needed to be easier to find.</p><p>For our first high-fidelity prototype, we decided to use AI to help us make these ideas into a Figma design. We were initially a little skeptical about whether an AI model could accurately reproduce what we wanted. This was different from starting with a blank design: we already had a low-fidelity paper prototype, had tested it with users, and had specific interactions and details that we wanted to preserve in the high-fidelity version.</p><h4>What did we use?</h4><p>We used two AI models during the process, with each serving a different purpose:</p><ul><li><strong>Claude Pro</strong>: used to create and modify the Figma prototype through its Figma MCP.</li><li><strong>ChatGPT</strong>: used to help us organize our requirements and create the prompts we would give to Claude.</li></ul><p>We started by asking Claude what information it needed from us to create the design effectively:</p><p>“I want to make a Figma design and I want you to execute it. What is the optimal way of input you want to receive to create the design?”</p><p>Rather than immediately generating a design, Claude asked us to provide information about six areas:</p><ol><li><strong>What the design is and who it is for</strong></li><li><strong>The screens or frames we wanted and what each should contain</strong></li><li><strong>The platform and dimensions</strong></li><li><strong>Our visual direction</strong></li><li><strong>Existing Figma assets, if any</strong></li><li><strong>The scope of the prototype</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*QkF1TB_skaOXj2wO2VAIUA.png" /></figure><p>This gave us a useful structure for thinking about what information the AI actually needed. Instead of simply telling it to “make a website for the Idea Lab,” we could provide the design requirements, user needs, visual direction, and interactions that we had already established through our research.</p><h4>Turning our research into a prompt</h4><p>After getting Claude’s list of requirements, we moved to ChatGPT to help us turn our materials into a single, detailed prompt.</p><p>We provided ChatGPT with Claude’s questions along with the materials we had collected during the design process. This included our paper prototype, the results from our user testing, and the color palette we wanted to use for the design. The goal was to make sure that the prompt captured not only what the website should look like, but also <strong>why certain design decisions had been made</strong>.</p><p>Once the prompt was ready, we gave it to Claude along with the reference images of our paper prototype. We then let Claude generate the Figma design.</p><p>After approximately 15 minutes, we had our first high-fidelity prototype.</p><p>The result was surprisingly close to what we had envisioned. However, there was one thing that wasn’t included in the first prompt that we missed: <strong>the prototype was not clickable.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XCt97UU-t0wD2fwZs8Rfzg.png" /></figure><p>The visual design had been created, but the interactions that we had tested and refined in our paper prototypes were not yet represented in the Figma prototype. Since interaction was an important part of our design, we went back to ChatGPT and asked it to help us create a second prompt specifically for making the prototype interactive.</p><p>We then gave this new prompt to Claude and waited another 10 minutes.</p><p>This time, Claude updated the prototype to be a clickable prototype.</p><p>The process showed us an important difference between using AI to generate a design and using AI as part of a design process. The AI could produce a high-fidelity interface relatively quickly, but it still needed <strong>clear instructions about the interactions and decisions that mattered to us</strong>. Our paper prototype and user testing were therefore not replaced by AI; they became the foundation that allowed us to tell the AI what to build.</p><h3>The Final Designs</h3><p>Our final designs combines the strongest parts of both paper prototypes. It makes search the main way to find resources, removes most overlays, and puts staff contact information near the top of the page. Linked is our high-fidelity <a href="https://www.figma.com/proto/WrWPn9NhDahRzi6uBCkIwg/IdeaLab-Website-Prototype?node-id=14-1237&amp;t=uuCiX6eWAn7tqLrh-0&amp;scaling=min-zoom&amp;content-scaling=fixed&amp;page-id=1%3A2&amp;starting-point-node-id=14%3A1237">Figma</a> and <a href="https://www.macalester.edu/160-hci-round-parakeets/">WordPress</a> prototypes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EumkycjlPpuFMyMvBXYLGw.png" /><figcaption>Starting point on the current Idea Lab website</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZyjeGMXM7edhTZ2noitUaw.png" /><figcaption>(High-Fidelity WordPress Prototype) “Start here” site navigation menu</figcaption></figure><h4>Three decisions shaped our end result:</h4><p><strong>Search is the primary way to find resources.</strong> From testing, we found out that the map caused users to be overwhelmed by choice. We also considered laying out the full floorplan of the lab, but however we felt that users unfamiliar with the space would struggle to find resources that way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pa1SqhnpDDirrmt2ehI07g.png" /><figcaption>(High-Fidelity WordPress Prototype) Resources Section</figcaption></figure><p><strong>Staff contact information is visible and accessible. </strong>Both groups preferred emailing staff to using a contact form. We added a “Start here” navigation menu near the top of the page, right after the introduction and about sections, with direct staff email links, so contacting someone takes one click instead of a search through the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MsO9B7QEAbrmDbz_UEA7ag.png" /><figcaption>Staff contact on current Idea Lab website</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*si13sqeT8DhkBNr8YBf5yA.png" /><figcaption>(High-Fidelity WordPress Prototype) Staff section</figcaption></figure><p><strong>Reservation language works for classes and individuals. </strong>Our faculty user found our reservation options student-centric, and objected to the word “room” on our paper prototype because they saw the Idea Lab as an open space. We revised the labels so they apply to both a student’s project and a professor’s class, and organized reservations by area of the lab so people can confirm that the space and materials they need will be available.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cXD7HYgI14_mQEg9gO0B8A.png" /><figcaption>Reservation section on current Idea Lab website</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qynpJmmPUzgnkMkJwsGcDw.png" /><figcaption>(High-Fidelity WordPress Prototype) Reserve space button near events header</figcaption></figure><h4>Fixing the original site’s usability problems</h4><p>Before we started designing, we each evaluated the current Idea Lab website against Jakob Nielsen’s <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">10 Usability Heuristics for User Interface Design</a>. Three heuristics stood out. Here is each problem we found on the original site, followed by how our final design handles it.</p><p><strong>Aesthetic and Minimalist Design</strong></p><p>“<strong>Interfaces should not contain information that is irrelevant or rarely needed. Every extra unit of information in an interface competes with the relevant units of information and diminishes their relative visibility.</strong>”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EumkycjlPpuFMyMvBXYLGw.png" /><figcaption><em>Before: </em>Dropdowns with one sentence descriptions</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ZwPmwzQcT04VX1hLEVe7g.png" /><figcaption>Two dropdown drawers with one sentence descriptions</figcaption></figure><p>For the section, “What You’ll Find In The Idea Lab”, we found that the dropdown interface was unnecessary. Prior to clicking the toggle, we expected each header to contain at least a paragraph of information, or at least a list of what each space contains.</p><p>Upon clicking the toggle, 1–2 sentences are revealed. In addition, we felt that the sentences weren’t very descriptive and raised more questions than answers. For instance, with the descriptor, “A low-pressure way to get started and collaborate alongside supportive staff”, it made us wonder, <em>“what kind of drop-in sessions?”, “what would we be collaborating on?”, “if they are recurring, then when do these sessions occur?”</em>.</p><p><strong>After:</strong> We replaced the dropdowns with a Resources section built around the two things our testers asked for: a clearly marked search bar and reservations for each area of the lab. Visitors can see what the Idea Lab offers without opening anything.</p><p><strong>Help Users Recognize, Diagnose, and Recover from Errors</strong></p><p><strong>“Error messages should be expressed in plain language (no error codes), precisely indicate the problem, and constructively suggest a solution.”</strong></p><p><em>Before: </em>A redirect to a misspelled Idea Lab email</p><p>Another issue we noticed was that the email redirect was misspelled. While this would be noticeable to Macalester students and those experienced with technology, this may not be as noticeable to those who are less experienced.</p><p><strong>After:</strong> We corrected the email link and put staff email addresses where our testers looked for them: the “Start here” menu and the staff section. Because testers trusted email more than contact forms, a working address matters more than any form we could add.</p><p><strong>Flexibility and Efficiency of Use</strong></p><p><strong>“Shortcuts — hidden from novice users — may speed up the interaction for the expert user so that the design can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.”</strong></p><p><em>Before: </em>News articles towards the bottom of the page</p><p>Finally, we felt that the breadcrumbing was off. The news articles displayed above are listed under Idea Lab News &amp; Highlights but the breadcrumb leads to Entrepreneurship &amp; Innovation. As a result, to return to the Idea Lab page, I would have to use the side navigation bar.</p><p><em>Before: </em>Breadcrumbing when clicking into the article, “Partners And Reflection: Emotions”</p><p><strong>After:</strong> We corrected the breadcrumbs and links so that a visitor who opens an Idea Lab news article can go straight back to the Idea Lab page, without using the side navigation bar.</p><p>Our prototypes are imperfect, especially the high-fidelity WordPress version, as our site editor privileges were limited. However, we’re gradually correcting and perfecting our prototype.</p><p>The best example of this is our calendar. Initially, we thought we were forced to use a WordPress table-style calendar, with extremely limited information, and no live updates. We then improved that to a screenshot, but in the current version of the prototype, we successfully implemented a live-updating calendar through i-frames with help from our peers, which was indicated to us was not possible.</p><h3>AI, Accessibility, and Ethical Considerations</h3><p>When using AI, we were a little worried about the ethical side of letting AI influence the decisions behind our design. We didn’t want to let the AI make its own design decisions. Instead, we took all the input we gathered from our paper prototype and user study and used it to create a detailed prompt. We then used Claude as a tool to take the gist of our design and recreate it in Figma.</p><p>We also kept in mind that if the final design ended up being inaccessible or confusing, the designer would still be responsible for the design. Because of this, we tried to make our prompt descriptive enough to limit the number of design decisions the AI could make on its own. We included our references, user feedback, and the design choices we had already made so that the AI had clear guidance before creating the design.</p><p>This also made us question whether using AI changed our role from designers into more of prompt writers and evaluators. I would say yes and no. AI definitely eliminated a lot of the time and effort that would normally go into creating the design. However, if I didn’t already know what I wanted as a designer, or didn’t have the skills to create the initial prototype and run the user testing, then I wouldn’t have had the information needed to give the AI good instructions in the first place.</p><p>So, AI can definitely help cut down the time spent on the design process, but the ideas and decisions still need to come from the designer. What helped us especially was having visual cues from our paper prototypes and the results from our user study. These gave us something concrete to give the AI instead of asking it to come up with a design from scratch.</p><h3>Reflection</h3><p>We had two key takeaways from this project, which we hope to use through the rest of our design course as well as going into future careers and design projects. First and foremost, this project made extremely clear the importance of human input. Without our testers and their feedback, our initial designs, while clever and pretty, would have lacked functionality, confused users, and put out the very user groups we were hoping to specifically help.</p><p>Second, working with WordPress, which is the recognized web-tool for Macalester websites, made clear the difficulties presented when forced to work with specific tools or within specific restrictions. While helpful and usable by most groups, WordPress is not a tool for generating ambitious, aesthetic, or highly functional designs, and in many capacities places extreme limits on the design functionalities we were hoping to achieve, but working within these boundaries was a great learning experience.</p><p>Going forward, it will be incredibly interesting how AI can be applied to design and accessibility. With proper guidance, it was made clear how powerful AI is as a design tool, but the specific modularity of pieces and how they interact is such a key part of web design, making it unlikely that AI can replace that capacity. More interesting, however, is AI as a cheap, reliable, and large-scale accessibility feature, remodeling websites to meet internet standards, enable screen readers, fix contrast issues, and generally make the internet accessible to all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9baefc5e3851" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macalester-hci/round-parakeets-redesigning-the-macalester-idea-lab-site-9baefc5e3851">Redesigning the Macalester Idea Lab Site</a> was originally published in <a href="https://medium.com/macalester-hci">Macalester HCI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesigning the Idea Lab Website]]></title>
            <link>https://medium.com/macalester-hci/redesigning-the-idea-lab-website-2f966f504646?source=rss----7ac5db827006---4</link>
            <guid isPermaLink="false">https://medium.com/p/2f966f504646</guid>
            <dc:creator><![CDATA[Daguilar]]></dc:creator>
            <pubDate>Fri, 09 Oct 2026 21:45:38 GMT</pubDate>
            <atom:updated>2026-11-09T17:11:14.387Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A project by Rachel Xu, Sydney Greene, Daniel Aguilar, and Royce Johnson.</em></p><figure><img alt="Student’s at the Idea Lab creating prototypes for a class." src="https://cdn-images-1.medium.com/max/960/0*XQHA0FribWLJpVu7.jpg" /></figure><blockquote>“Navigation is the science of moving from one place to another. When it comes to websites, users may feel frustrated and give up on a task if they have to maneuver an ocean of unclear features.”</blockquote><p>The Idea Lab website at Macalester College appears to display information about the department straightforwardly: photos, news, a calendar, and different hyperlinks. Nevertheless, on closer inspection, certain sections of the website are simplistic and repetitive. To improve navigation and better depict the essence of the Idea Lab, we created three different website prototypes that prioritize novelty and simplicity.</p><h3>Initial Exploration and Critique of the Idea Lab Website</h3><p>When users first land on the website, they see photos of activities in the space and a description of the department first. Below, the content begins to get inconsistent and cluttered.</p><ul><li>“What You’ll Find” Section: It displays a set of dropdown menus that contain only one sentence describing the department&#39;s offerings and space features.</li></ul><figure><img alt="Drop-down menus that each give one-sentence explanations about the Idea Lab." src="https://cdn-images-1.medium.com/max/782/1*hiaTwwTGaatoo5EUZZPvyg.png" /></figure><ul><li>Activities and Sessions Square: It describes the events that take place in the space and prompts the user to follow the department’s Instagram page; the hyperlink is unclear unless the user reads the whole paragraph. It also changes color on hover, but only the at sign is interactive.</li></ul><figure><img alt="A rectangular box with a description of what kind of events can occur in the Idea Lab and the mac_eship Instagram handle." src="https://cdn-images-1.medium.com/max/781/1*grcAwkNcYl2pxSMyiR26Yw.png" /></figure><ul><li>Monthly Calendar: The embedded Google Calendar is in monthly view and shows a dense amount of information.</li></ul><figure><img alt="A calendar in month view on the Idea Lab website that displays all events." src="https://cdn-images-1.medium.com/max/782/1*AwgMlYQBSl67pK4BQuvEsQ.png" /></figure><ul><li>Contact and Reservation Sections: Buttons that redirect users to the EMS website and to contact the Idea Lab coordinator. The latter does not work across devices; some users might not be able to access the contact information.</li></ul><figure><img alt="“Schedule the Idea Lab” and “Want to Learn More About the Idea Lab?” sections." src="https://cdn-images-1.medium.com/max/777/1*yxgv3s50yIfw9lRGLNEIlw.png" /></figure><ul><li>News and Highlights: Information and features make this area feel overwhelming. An introductory text is shown between two hyperlinks that redirect users to the same story, all stacked next to each other.</li></ul><figure><img alt="A list of Idea Lab news articles, each having a picture, title, description, and another different title." src="https://cdn-images-1.medium.com/max/785/1*IvvAq38kvmpchWtvO-khwg.png" /></figure><p>These features hinder the possibility of a smooth navigation experience for different types of users. However, making significant updates is not a seamless process either. The WordPress building blocks used by Macalester College to create their webpages can constrain designers’ creativity. Since we intended not only to reimagine a new potential website for the Idea Lab, but to inspire changes even with the limitations of WordPress, our three designs explored increasing levels of constraint while informing one another.</p><h3>Initial Sketching &amp; Paper Prototyping</h3><blockquote>“The Idea Lab is more than just a room in the DeWitt Wallace Library — it’s a collaborative workspace where students, faculty, and community come together to build, test, learn, and play.”</blockquote><p>Where can multiple users easily build, test, learn, and play in the real world? A laboratory or playground would work, of course. But what kind of condensed, familiar space echoes this essence of the Idea Lab? After some discussion and sketches, our answer was clear: a corkboard! We wanted one of our prototypes to resemble an interactive corkboard, where information appears in a pop-up as if someone is pinning a poster onto the board.</p><figure><img alt="A rough sketch of the reimagined Idea Lab website that looks like a decorated corkboard." src="https://cdn-images-1.medium.com/max/771/1*TgZIHnrjbXx-LZQ4O-hwDA.png" /></figure><figure><img alt="Two rough sketches of the reimagined Idea Lab website. The top sketch follows a standard website structure while the bottom follows the corkboard idea." src="https://cdn-images-1.medium.com/max/678/1*6w0vF9aN0oiSYycxIfdRVQ.png" /></figure><p>However, we did consider the possible limitations of the Macalester website. After speaking with the Idea Lab staff, we learned that WordPress, the website editor Macalester uses, is extremely limited. A Macalester page can only be made using pre-existing blocks, limiting creativity. That is why we decided to make a second prototype look similar in structure to the original Idea Lab website, but simplified, a <em>semi-constrained </em>design.</p><figure><img alt="Initial sketches of modules for the semi-constrained design." src="https://cdn-images-1.medium.com/max/692/1*AfoPotoQ11AENyFHrmfhRg.png" /></figure><p>From sketches, one of the main features discussed that we were excited to include in our prototypes was an interactive map of the space. However, we were not fully sure of how to lay out its contents and make it as accessible the best, so for our paper prototyping we aimed to keep the idea simple and representative to get feedback from users.</p><figure><img alt="A rough sketch of the Idea Lab map and contact information." src="https://cdn-images-1.medium.com/max/690/1*IEztFJl3wUsTAZCbp1CsSg.png" /></figure><p>We also wanted to make our paper prototypes as similar to using a computer as they could be to improve the testing experience. We built a mock computer screen out of materials found in the Idea Lab. As our semi-constrained design was intended to be scrollable, we also made a system where we could pull the paper through the screen as if the user was scrolling through the pages. This significantly improved the user’s testing experience. For pop-ups, we used small Velcro to add pieces of paper on top of the main piece. The unconstrained design did not need to use this feature, as it is meant to be a simple, one-page screen, with pop-ups essentially holding the information needed to complete the task.</p><figure><img alt="Frame system that imitates the process of scrolling to improve user testing." src="https://cdn-images-1.medium.com/max/687/1*H72Uf3HisxMHdr12bVZ8QA.png" /></figure><figure><img alt="Paper design embedded into squared crafted frame, and individual pop-ups (staff, map areas, calendar views) with Velcro." src="https://cdn-images-1.medium.com/max/693/1*N1wPyz0SFZjeBGwqU4BY1w.png" /></figure><p>Our constrained design was mainly built using Canva and then printed and put together, as it was more complicated, and our unconstrained design was built using colored construction paper. Note that the paper colors are not accurate to the final product. We just wanted to make it obvious which parts were separate to both the user and us — also, we were limited by the construction paper palette.</p><figure><img alt="An assembled paper prototype of the unconstrained design. It consists of various colors and a corkboard-like appearance." src="https://cdn-images-1.medium.com/max/690/1*0lJBsHEaFnIl_7zx2J-UPQ.png" /></figure><h3>Usability Tests with Paper Prototypes</h3><p>We focused on three user groups for testing: first-year students, faculty members, and Idea Lab student staff. Each user group was given three different tasks to perform with the prototypes, commenting on their thoughts and actions as they performed the tasks.</p><p>The main takeaway from the usability tests was that navigation is crucial. For our constrained design, it was very easy to backtrack, but it wasn’t clear what information could be found with just the home page and sidebar alone. The unconstrained design had easier navigation, but was a little too cluttered, as the student staff we ran the test with mentioned. An interesting discovery from testing was to hear what expectations users had on what a section would display; they reported that having the calendar under events and the map under resources felt confusing.</p><p>For our high-fidelity prototypes, we had to balance between making all UI elements clear to meet user expectations, while not overwhelming the user with too much information. We ran usability tests with a faculty member who mentioned that she wanted to see all the information needed on screen initially. She seemed to prefer the unconstrained design for that reason, albeit mentioning it was a bit cluttered, as mentioned before.</p><p>Users also mentioned that they liked the reserve button to be apparent and not hidden. The faculty member mentioned that she has to deal with reserving spaces a lot for various faculty members, so she appreciated direct access to the reservation button. Similarly, the Idea Lab student worker mentioned he preferred the immediate access to the EMS reservation system, since he looks for relevant events he should be aware of during his shift in there, not on the Google Calendar.</p><p>Based on all of this feedback, we tried our best to incorporate this into our designs. After we all followed the Figma tutorials and we understood the software, we got to work on the high-fidelity prototypes. We planned to make both in Figma, and then later create a fully constrained design into a Macalester WordPress site with limited blocks. We began with an unconstrained design in Figma with the constrained idea in mind so that our creativity and ideas were not fully limited. This made it easier for us to later make any changes in WordPress based on what we came up with.</p><p><strong>High-Fidelity Unconstrained Prototyping: Figma</strong></p><p>For the unconstrained design, we followed our paper prototype’s main idea. First, adapting colors to align with a variation of Macalester’s college secondary color palette, we improved the visual hierarchy and made the website look cleaner altogether. The website was re-sketched with the same idea in mind but a slightly different, more polished design.</p><figure><img alt="The initial design of the unconstrained prototype’s home page." src="https://cdn-images-1.medium.com/max/701/1*OT3AwtvskJul3q6GpuNinQ.png" /></figure><p>The main changes we made were to the banner at the top and to the widgets that users can click on to open the news and calendar. We also played around with the font to, again, exude a professional but still fun feeling. Some changes were made due to the critique we did in class. The reserve button was put on the left sidebar with the rest of the navigation buttons, and the FAQ page idea was removed as it did not seem necessary. The color palette we chose was multi-colored and fun, while still including the dark blue of the Macalester palette.</p><p>Along with the homepage, we also made the about page, map, materials, tutorials, staff, news, and calendar and events pages. The creation of the map page was pulled from the map we created for the constrained design, which was mentioned in the section above. For the materials page, we went with four simple, different colored buttons that swapped the text and fill color when you hovered over them. Each button overlays a list of the sections’ respective materials.</p><figure><img alt="The materials page of the unconstrained prototype as a pop-up window." src="https://cdn-images-1.medium.com/max/696/1*H6jBUISNc7gaQrkI77bZ4w.png" /></figure><p>We kept the materials sectioned off according to the way that the Idea Lab organizes their space. The tutorials, staff, and news pages all use modules within the larger page to separate the information. This is the only part of the unconstrained design that we used AI on. Auto-layout on Figma took some getting used to, and we were short on time. The built-in Figma agent built just the modules for the staff and news for us.</p><figure><img alt="The tutorials page of the unconstrained prototype as a pop-up window." src="https://cdn-images-1.medium.com/max/768/1*kEup1hXrh6mdXQMGw_V3DA.png" /></figure><p>The staff page includes a full-time page and a student worker page. This is achieved by changing the button of the respective page to a different color and swapping the overlay when the button is clicked. The full-time staff have emails, roles, and phone numbers, so their modules are larger. The student staff only include a name and picture, and because there are many student staff, this page is scrollable so the readability of each staff member’s information remains.</p><figure><img alt="The staff page of the unconstrained prototype as a pop-up window." src="https://cdn-images-1.medium.com/max/776/1*1SON26vsn82XxEeSjflDtQ.png" /></figure><p>The footer of the page was also changed along the way. Initially, it did not span the left sidebar, but because we moved the news page to the right side, we extended the bar. This also made the design look more balanced and cohesive and allowed us to include more information without looking too cluttered. We took inspiration from the Macalester website footer and included the information about Macalester on the right side.</p><figure><img alt="The footer of the Macalester website." src="https://cdn-images-1.medium.com/max/877/1*Chy-GLyDfYcH6sgvGcUGSw.png" /></figure><p>On the left side is the contact information and location of the Idea Lab itself. The mail button takes the user to a mailto link, and the Instagram button sends them to the Idea Lab’s Instagram page. While it is technically the Macalester Entrepreneurship page, it also promotes Idea Lab events.</p><figure><img alt="The footer of the unconstrained prototype." src="https://cdn-images-1.medium.com/max/831/1*OF25ZGEciIRbciPC9dQ2oQ.png" /></figure><p>To sustain focus on the pop-ups and improve readability, the background behind them becomes slightly darker. Based on feedback from class critiques and the Stark tool, we also modified the shades of the colors we had to create better contrast.</p><figure><img alt="A small part of a pop-up, focusing on how the background darkens to contrast the pop-up’s contents." src="https://cdn-images-1.medium.com/max/226/1*YzNOKUw4W2qAqcBP1D-Eww.png" /></figure><figure><img alt="The first color palette of our unconstrained prototype." src="https://cdn-images-1.medium.com/max/247/1*9xME8bJ9WCa-Gpt1zfYIXA.png" /></figure><figure><img alt="The final color palette of our unconstrained prototype." src="https://cdn-images-1.medium.com/max/237/1*xu47dkTXW1dRz7u2vV-xlw.png" /></figure><p>On the other hand, the class critique and user testing with new representatives for our user groups pointed out that our reservation button was very salient by having a different color than the column’s. For this reason, we updated it to a neutral beige in the design and added a transition screen, as in the semi-constrained design, which we further discuss for our semi-constrained design. This informs the user better about the status of the system and shifts the focus.</p><figure><img alt="The final design of the reserve button, with a white button and dark green text." src="https://cdn-images-1.medium.com/max/368/1*waAAD1if2B9xkOKhEMGJqA.png" /></figure><p>Finally, to increase readability, we changed the calendar on the right bar to start at a week view and increased its size. Both an Idea Lab student worker and a freshman student on a second round of testing mentioned that the monthly view felt very cluttered, while the week view could work as long as it could be displayed with better spacing. As a result of these updates, our main page’s final look improved and was designed to interact with the user better.</p><figure><img alt="The final design the unconstrained prototype’s home page." src="https://cdn-images-1.medium.com/max/832/1*22_59Xf8eDgiSgie4Z-joQ.png" /></figure><h3>High-Fidelity Semi-Constrained Prototyping: Figma</h3><p>Our semi-constrained design builds upon ideas from the constrained design and noted limitations of the Macalester website. To copy the website structure efficiently into Figma, we first designed a small section of the website; along with instructions, our paper prototype, and the Idea Lab current website, we asked Claude to create an initial design. This design required multiple manual updates to improve navigation, especially the sidebar, section organization, and specific content.</p><figure><img alt="Initial design that copied the Macalester College layout. Provided to Claude as a reference to re-create the current building blocks of the Idea Lab and build new ones." src="https://cdn-images-1.medium.com/max/766/1*znXf2a8-GDvNUZRrgy1Xug.png" /></figure><p>Our main goal was to ensure users could navigate sections easily and quickly from the first page. For this, we included information from the Idea Lab, photos, three main buttons, and all relevant sections in a dropdown menu in the sidebar, as well as a direct link to the reservation system.</p><figure><img alt="The home page for the semi-constrained prototype of the Idea Lab." src="https://cdn-images-1.medium.com/max/740/1*6DdTjM713pk9104Z9nJOhg.png" /></figure><p>Based on class feedback, we set the calendar — which alternates between a monthly, weekly, and daily view — to start at a weekly view by default. As with the unconstrained design, the calendar has shapes to distinguish between types of events.</p><figure><img alt="The calendar of the semi-constrained prototype showing events in a weekly view." src="https://cdn-images-1.medium.com/max/765/1*MJdvvmnggIm1ETvgCkncdw.png" /></figure><p>One of the main strengths of this prototype is that, unlike the actual sidebars on the Macalester website, the one here stays visible at all times. This allows the user to navigate through sections and access contact information at any point without having to look around. Nevertheless, as with other features for our prototypes, this is not functional for non-desktop devices, unfortunately.</p><figure><img alt="A section of the semi-constrained prototype showing the different areas of the Idea Lab on a map." src="https://cdn-images-1.medium.com/max/773/1*-WDFLGdE-C4_cx03Nv3iZA.png" /></figure><p>When the user attempts to make a reservation, instead of going directly to the EMS system website, there is an intermediate screen. Since users might be unfamiliar with the platform, this transition ensures that they understand there will be a different website involved. We included a tutorial button as a placeholder for a link to a video that would explain when and how to reserve the Idea Lab. Additionally, a third button lets the user return to the previous page.</p><figure><img alt="A confirmation page informing that the user is leaving the Idea Lab page to go to the EMS page." src="https://cdn-images-1.medium.com/max/763/1*PvGlAgqaI7JWSDVsOoVroQ.png" /></figure><h3>High-Fidelity Constrained Prototyping: WordPress</h3><p>For the fully constrained prototype, we wanted to use the WordPress hosting tools that the official website uses. This came with the benefit of automatically having a sidebar, header, footer, and content blocks that match the Macalester design, but we were unable to make any of the fundamental changes, such as having an always-visible sidebar. We were able to reuse some blocks that were originally designed for other campus departments, and even embed a Google Calendar that shows the week schedule by default.</p><figure><img alt="Weekly calendar view in the constrained WordPress design." src="https://cdn-images-1.medium.com/max/766/1*_cgjujMvBVqn0imNtRQeRQ.png" /></figure><p>However, the biggest challenge was implementing the interactive map element. We could not create a WordPress native block, and the custom HTML block was limited, so we took inspiration from the embedded Google Calendar. The calendar used an iFrame to display web content that was being hosted somewhere else, so we decided to host our own web content on GitHub to make it appear like a WordPress block.</p><p>We put screenshots of the Figma map prototype into Claude to get a baseline for the CSS and HTML elements to match the theme, then made changes to refine the design to fit inside the WordPress iframe. A limitation we realized was that the iFrame element is always 800x600 pixels, which means it doesn’t follow responsive design. The map element can be viewed at this link: <a href="https://dinodigger3000.github.io/idea-lab-map-demo/">Idea Lab Map Demo</a>.</p><figure><img alt="Interactive map design with the help of Claude for WordPress constrained design." src="https://cdn-images-1.medium.com/max/777/1*4mhSqV2PVJrJ0RH9Zb1hXg.png" /></figure><p>For the sidebar, we added links to each section of the page. This still allows the user to navigate easily from the start of the webpage. To have links that bring the user to different spots on the same page, we used the WordPress embedded HTML anchor tool, so we could include links like url/idealab<em>#calendar </em>to direct the user without reloading the whole page.</p><figure><img alt="Main page of the constrained WordPress design." src="https://cdn-images-1.medium.com/max/770/1*cm575ku9f27XHMyXMB5krw.png" /></figure><p>Using WordPress was challenging, but one benefit of using it was that the calendar and events feed were using the real APIs that the original site uses, so the content will always be updated automatically.</p><figure><img alt="Events section in the constrained WordPress design." src="https://cdn-images-1.medium.com/max/1024/1*DdL3kKef7WanPbZuH2_Zzw.png" /></figure><h3>Critique &amp; Accessibility</h3><p>We made a couple of changes to the unconstrained prototype after checking for accessibility. We initially made the full-time staff page not scrollable and only had four individual modules, but we changed it so that the font size could be bigger and more readable. On the other hand, shapes to represent different types of events on calendars were reported to not be big enough. Thus, we updated their sizes accordingly to improve their visibility.</p><p>Also, we initially had a lighter color palette, but then the white text would not contrast as well with the background, so we made some colors darker. However, the yellow and white remained an issue, and in retrospect, we should not have included yellow as a background color for text at all. We did not have enough time on the assignment to change our entire color palette when we realized, but it is something that we will keep in mind for the future.</p><p>Given the format of our unconstrained design and Figma limitations, it was not possible to include alternative text in this prototype. Nevertheless, the semi-constrained prototype and the constrained prototypes included alternative text — either shown on the screen or available through inspection of image elements. To better account for screen readers, we move the modules of alternation between elements of the map to sit at the top of the section rather than below across designs. In this way, a screen reader would read them first and make the element have more immediate relevance.</p><figure><img alt="The map of the Idea Lab on the unconstrained design. The buttons to navigate each section are at the top of the pop-up to allow easy flow for screen readers." src="https://cdn-images-1.medium.com/max/767/1*tCF4IO6SGIaguXFu5SDV1w.png" /></figure><h3><strong>Usability Tests with High-Fidelity Prototypes</strong></h3><p>After finishing up our high-fidelity prototypes, we performed another round of user tests. We did not have enough time to implement all of the feedback, but it was still meaningful to hear how else we could improve the designs if we did have time. Overall, the feedback was positive. Users were content with the simple navigation of both prototypes, especially with the unconstrained one because of everything being on one page.</p><p>The Idea Lab staff stated that the map is not necessarily a “map” in the standard sense, but rather a generic overview to “explore the space.” We did change the label to “explore the space” as a result. There was also feedback from all groups about changing some graphics and aesthetics, such as the color of the “reserve” button and certain elements of the GIF. The Idea Lab currently intends to highlight their role in entrepreneurship over their status as a maker space. For this reason, we adjusted the originally icon-heavy GIF.</p><figure><img alt="Updated opening GIF for the constrained and unconstrained design reading “Where curiosity meets action.”" src="https://cdn-images-1.medium.com/max/1024/1*Yw5oLyOFS2G7BjSydGxR9Q.gif" /></figure><p>All new users involved in testing mentioned that the events section and calendars were fairly standard, but lacked pictures. They reported that these elements thus felt more boring or disconnected from the rest of the prototype. Nonetheless, the simplicity made the designs overall clear and direct. This feedback pointed to the need to incorporate non-overwhelming, meaningful visual elements that could spark interest and appreciation for the Idea Lab.</p><p>Finally, testing raised new considerations of needs previously not met for user groups. The freshman student mentioned they were unsure of how to know whether an event required an RSVP from the calendar. Moreover, they mentioned that it was difficult to find the student workers list on both semi-constrained and constrained designs; they wished that there was a section exclusively dedicated to portraying what it is like to work at the Idea Lab.</p><p>Altogether, feedback revealed to us that many updates and improvements would be needed to reach a better design. This brings us to our limitations, as changes were beyond the scope of our project and timeline.</p><h3>Limitations</h3><p>One of our limitations is that we do not account for all possible types of users. Alumni and potential donors are user groups that we did not consider in our testing and design focus. Since we did not have much content from the Idea Lab website to base the prototypes on, and we were limited in time to create it on our own, it was difficult to extensively portray the work and relevance of the Idea Lab for parents and prospective students.</p><p>Something to note is that it was difficult to access some of the Idea Lab’s information. This made it difficult to figure out what to put on the website. For example, the original website did not list what materials were available in the Idea Lab. We had to either ask the Idea Lab staff or wander around the Idea Lab for QR codes that give a list of supplies. There was a list of supplies for specific sections, but not one for the shelf of bins filled with general materials. As a result, in the unconstrained design we had to make a materials page ourselves, which is why “general materials” looks and behaves differently from the other lists.</p><h3>Conclusion</h3><p>This project taught us many lessons regarding design and testing. Paper prototyping was an effective way to awaken our creativity and consider navigation from an early stage. By having ideas laid out simply, it was also easy to determine which features could be shared across devices later on, such as the map and calendar modules.</p><p>Furthermore, testing both our paper prototypes and high-fidelity prototypes demonstrated how crucial it is to interact with users as much as possible from the start. Many of our section titles and content were different from what users expected to find for each; people did not expect a calendar under events, but a simple list or news that illustrates them. Overall, feedback constantly reminded us of how crucial it is to revise a design to identify assumptions that can be problematic.</p><p>In the future, we would be interested in exploring how other user groups not considered for testing interact with the prototypes. Their feedback would make updates more meaningful and help shape how the Idea Lab can be better represented. Additionally, incorporating some of our ideas into the constrained WordPress sites by proposing and creating new, standardized building blocks and modules would be a unique learning experience. We did not have as much time to work on our WordPress website; in the future, we would like to spend more time on finalizing products such that users might implement them right away or be inspired to copy features into an existing design.</p><h3>Links to Figma Designs</h3><ul><li><a href="https://www.figma.com/proto/kRLNQVNhdx3JU6J59hNLN8/Draft-Constrained-Design?node-id=58-2&amp;t=ObPWTLQoq1REbOCD-1&amp;scaling=min-zoom&amp;content-scaling=fixed&amp;page-id=46%3A2&amp;starting-point-node-id=58%3A2"><strong>Unconstrained design</strong></a></li><li><a href="https://www.figma.com/proto/kRLNQVNhdx3JU6J59hNLN8/Draft-Constrained-Design?node-id=58-2&amp;t=ObPWTLQoq1REbOCD-1&amp;scaling=min-zoom&amp;content-scaling=fixed&amp;page-id=46%3A2&amp;starting-point-node-id=58%3A2"><strong>Semi-constrained design</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f966f504646" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macalester-hci/redesigning-the-idea-lab-website-2f966f504646">Redesigning the Idea Lab Website</a> was originally published in <a href="https://medium.com/macalester-hci">Macalester HCI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DJ-BA’s Idea Lab Proposal]]></title>
            <link>https://medium.com/macalester-hci/dj-bas-idea-lab-proposal-5ccd0f5c1cfa?source=rss----7ac5db827006---4</link>
            <guid isPermaLink="false">https://medium.com/p/5ccd0f5c1cfa</guid>
            <dc:creator><![CDATA[Dureti Gamada]]></dc:creator>
            <pubDate>Fri, 09 Oct 2026 20:58:07 GMT</pubDate>
            <atom:updated>2026-10-09T21:26:04.420Z</atom:updated>
            <content:encoded><![CDATA[<p>Here is a link to our Figma Prototype:</p><p><a href="https://www.figma.com/design/ZSiCgJqnpcATeyUr9DUrUN/Idea-Lab-Prototypes?m=draw">https://www.figma.com/design/ZSiCgJqnpcATeyUr9DUrUN/Idea-Lab-Prototypes?m=draw</a></p><p><strong>Introduction</strong></p><p>We designed two low-fidelity and two high-fidelity prototypes for the Idea Lab’s website. For the first design sprint of Macalester’s “Human-Computer Interaction” course, we were tasked with redesigning the <a href="https://www.macalester.edu/entrepreneurship-and-innovation/idealab/">Idea Lab’s website</a>. In our third class session, we critiqued the website’s design and identified inaccuracies. This includes the following examples.</p><p>The “What You’ll Find in the Idea Lab” tagline demands one<em> </em>click to reveal a short, one-sentence description:</p><figure><img alt="What you’ll find in the idea lab" src="https://cdn-images-1.medium.com/max/1024/1*JzCmFgUIBTjbpPErYy6PmQ.png" /><figcaption>What you’ll find in the idea lab</figcaption></figure><p>There is an unclickable highlighted element:</p><figure><img alt="Unclickable highlighted element" src="https://cdn-images-1.medium.com/max/1024/1*5xVCU75B7Fom4Ms6mzuEWg.png" /><figcaption>Unclickable highlighted element</figcaption></figure><p>Finally, there is a button that takes you to a separate unrelated site, which is the EMS reservation interface:</p><figure><img alt="Schedule the Idea Lab EMS" src="https://cdn-images-1.medium.com/max/1024/1*3o05LYR6Yj_rt5RTKq8cUQ.png" /><figcaption>Schedule the Idea Lab EMS</figcaption></figure><p>The aforementioned examples each violate at least one of <a href="https://www.nngroup.com/articles/ten-usability-heuristics/#poster">Nielsen’s ten usability heuristics</a>, including: <em>visibility of system status</em>, <em>consistency and standards</em>, and <em>flexibility and efficiency of use,</em> respectively. In addition, the layout of the site felt arbitrary and disorienting. Why is there a second photo carousel at the end? Why doesn’t the “Contact Idea Lab” button open Gmail, Macalester’s primary email service provider? Lastly, why does the Entrepreneurship &amp; Innovation department’s Instagram handle need its own section? While part of its mishaps are due to Macalester’s strict web design paradigm, the Idea Lab website lacks focus, misuses its space, and <em>tells </em>you more than it <em>shows </em>you.</p><p>Thus, we were tasked with creating two low-fidelity and high-fidelity prototypes for the Idea Lab’s website. A low-fidelity prototype, also known as a paper prototype, is a quick paper-and-pencil design that rivets towards functionality, usability, and anatomy rather than aesthetics, mechanics, or bugs. The method is comparable to the preliminary sketch of the Mona Lisa — how else was DaVinci supposed to know where to paint? High-fidelity prototypes, on the other hand, are the finished, computerized version of a low-fidelity prototype. It is on a real screen, it has color, and it closely resembles the final design. It is the 3D model of a house, as opposed to its blueprint.</p><p><strong>Our Design Process</strong></p><p>While many companies choose to jump straight to high-fidelity prototyping, our class stuck to paper prototyping first for its simplicity, low cost, and the benefit it brings to our “more is more” philosophy. Each member of our team designed two low-fidelity prototypes (shoutouts to the Idea Lab for its art supplies) and evaluated them using Amy Ko’s <em>How to Evaluate Empirically</em>. Then, we designed two additional low-fidelity prototypes by taking in elements from our previous designs. Those two prototypes were our basis for the high-fidelity prototype:</p><figure><img alt="DJ-BA’s 2 low fidelity prototypes" src="https://cdn-images-1.medium.com/max/1024/1*mpRwMZLCi883mmyw8RdGfw.png" /><figcaption>DJ-BA’s 2 low fidelity prototypes</figcaption></figure><p>Our two final paper prototypes share the design philosophy, <em>space efficiency</em>, yet they fulfill that philosophy using different means. The leftmost prototype rearranges the website’s elements in three separate columns instead of two — creating a layout jam-packed with content with as few scrolls as possible. It also features quality-of-life additions such as the color-coded Google Calendar, accessibility settings, and the combination of both image carousels. The rightmost prototype reworks the <em>Entrepreneurship &amp; Innovation </em>website — removing the large sidebar in favor of four call-to-action buttons for the department’s most important features. Quality-of-life additions include: “Reserve” and “Contact” buttons at the top for zero-scroll access, one-row taglines with no redundant descriptions, and an image carousel featuring the Idea Lab’s tools and machines. Unlike the leftmost design, this design omits the “Instagram handle” card, the “Meet the Staff” section, and the second half of the introductory paragraph — it’s efficient in the sense that it streamlines the website’s features.</p><p>After evaluating our two final low-fidelity prototypes, we began work on the two high-fidelity prototypes in Figma. While both of our high-fidelity prototypes are based on the rightmost low-fidelity prototype, we incorporated multiple elements from the leftmost prototype, such as the aforementioned color-coded Google Calendar, the removal of the taglines, and captions and indicators for the image carousel. We believed that the streamlined layout of the rightmost prototype combined with the complexity of the leftmost prototype created a balance between usability and aesthetics. However, we chose to expand the design with additional sections such as the “Contact Us” message box, the “Schedule Us” section with EMS (Macalester’s reservation tool) integration, and a footer with the missing subpages from the original’s sidebar.</p><p>For the second high-fidelity prototype, we embraced A/B testing techniques to enrich the testing phase. It allowed us to assess the effectiveness of the colors, the button placement, and section order. This way, we can pinpoint exactly what needs to stay and what needs to be changed. It’s during this design phase that we decided to get rid of the taglines, as we approached a “less is more” and “show don’t tell” philosophy for our design; tests with and without them showed similar results, suggesting that they were not benefiting or harming the user experience. We opted to remove them in line with our design philosophy of <em>space efficiency</em> and our “show don’t tell” approach.</p><p><strong>Test Cases</strong></p><p>As we advanced through to our final paper prototype, we had to keep considering: who is this for? Who are we marketing to, and whose life becomes simpler as a result of our interference? We narrowed down our user-testing groups and main audiences to faculty/event organizers, arts/crafts students, and prospective students. We were looking at what actually draws them in and compels them to stay on the website; what they’d want to look for. A good way we implemented this was a simple division of ‘user tasks’, where we’d ask them to find things throughout the website to ultimately see if our design’s usability was accessible and enjoyable to navigate.</p><p>As we tested our low-fidelity prototypes, one problem stood out, which was that our design wasn’t as intuitive or as specific as they’d have liked. The good thing about prototyping, luckily, is that we care to see our mistakes more than our accomplishments. The first was that it was a little difficult to distinguish between the different aspects because of the lack of color, and the contact information was a bit confusing, since they didn’t know which area to gravitate towards to ask for help. The first prototype was very, very simple.</p><p>To help them really experience the web interface, we used a little ‘scrolling window’ so we could simulate the actions of a computer, making it as interactive as we could at that stage. The prospective students said the way we phrased things like having “workshop” in two areas was confusing, but an aspect that we kept throughout the paper prototypes, a color-coded Google Calendar, seemed to be popular in theory.</p><p>The prospective student user also mentioned that a freshman student is likely reading that mission statement and what the Idea Lab is actually about before rushing to the task, and thought it would be helpful to integrate the Entrepreneurship and Innovation calendar into her own in a simple click so she would not have to go through the whole thing. She also thought the image captions, which were updating, weren’t clear enough for communicating what was going on. This was a challenge, since we had to think about the battle between being concise and to the point, while also being descriptive and specific enough.</p><p>Another challenge we had across all user testing groups was the interactive aspect, where they’d often ask for clarity on whether something was a hyperlink or an advertisement and the 3D aspects. The arts and crafts user testing group seemed to have the least amount of struggles and navigated through the page with ease, only struggling with the contact us section. Our event organizer felt as though the booking rooms were confusing for that reason. This was tricky since we incorporated a feedback, help, and messages forum into one, and also thought about a meet the team area in the sidebar, where we’d have their roles and contact information. A drop-down inquiry or something that says general feedback would be helpful, as suggested by our event organizer testing group. Our arts/crafts user brought up how an entrepreneur would struggle to find something specific they’re looking for. Evidently, we had to reflect on what reason they’d go to the contact us/message us section versus a direct email- which we decided was dependent on the user group. A happy medium was to keep both, since a start-up or entrepreneurship business would be more likely to directly contact and email an individual rather than go through the system.</p><p>We also decided to add a footer instead of our miscellaneous items, and along with the arts/crafts student’s advice, keep the right-hand side legend or toolbar for general contact information with emails, phone numbers, faces, and that he was more interested in the space than the people behind it, so it wouldn’t need to be front and center.</p><p>There was a preference for a weekly basis instead of monthly for the calendar, which we thought was great advice. They liked the placement and liked the idea of having that information brief and to the point. It becomes tricky when you want to stay true to the original reference and respect the mission statement, while simultaneously trying something new. So we were trying to find that balance.</p><p>The high-fidelity tests were done on Figma, a design tool, to simulate the feel of a real website, at least on a desktop. In this case, in execution, the colors seemed to be the main issue. Our event organizer user tester thought that the colors could be more distinguishable so that it could be a little bit clearer. And the arts/crafts student seemed to dislike our color scheme that strayed away from the original blue and orange. They didn’t pair well with the background, and overall the color story would’ve done better as the original one. The message us area was also confusing for them, so we decided to stick to the original website format generally and go from there.</p><p><strong>In-class critique</strong></p><figure><img alt="Figure 1. Initial design for in-class critique" src="https://cdn-images-1.medium.com/max/446/1*vtCapgAMMvfi-6s6rGBF6g.png" /><figcaption><strong>Figure 1. Initial design for in-class critique</strong></figcaption></figure><p><strong>Figure 1. Initial design for in-class critique</strong></p><p>The in-class critique occurred on Wednesday, September 30, 2026. Before the in-class critique, our group divided into two groups: one group contained Dureti and Anha, the other group contained Bryant and Joseph. Our group had completed our first prototype, but had not completed our second prototype. Therefore, we received critiques purely based on our first prototype. Dureti and Anha received positive critiques about multiple aspects of the prototype. This included the fact that the users felt positively about the image placed on our Idea Lab website of the area, as seen in Figure 1. This also included the fact that the feedback section was useful for general comments for any user to provide feedback. Another positive critique was that the users enjoyed the ability to scroll through a carousel of images by clicking buttons below the image, as well as clicking the arrows to the left and right of the image. The top bar, E&amp;I design, and the “Challenges,” “Idea Lab,” “Internships,” and “Funds” buttons at the top received positive feedback. Bryant and Joseph received positive feedback about the E&amp;I design as well.</p><p>Our group also received constructive criticism for the prototype. One criticism was that multiple texts, specifically the “Student-led workshops” and “Drop-in Sessions” rectangles as seen in Figure 1, appeared to be clickable when they were not intended to be clickable. These rectangles of text were intended to highlight general events that can be found in the Idea Lab. They appeared to be clickable due to the fact that, when a user hovered over them, they changed colors. As a result, we received critiques that we should either have them be clickable, or otherwise, we should remove the effect of the rectangles changing colors. They also suggested that any buttons that were clickable should be a different color than these rectangle “tags” that were not clickable. As a result, we decided to completely remove them, as well as the “Collaborative Space” and “Community Workspace” buttons, as all four buttons did not add new information to the website and were confusing to users.</p><p>There were several additional critiques. The users wished that there was a sidebar or top bar for shortcuts to each section within the webpage; the circles underneath the image carousel were smaller; the feedback section had a more specific title and was also further down the page, there was a “meet the staff” section; and there was a color-coded calendar with a key and a week view rather than a month view. Bryant and Joseph received feedback about the addition of a sidebar for quick navigation, the blue tagline boxes reading as buttons, the orange color reading as a red color, moving the feedback to the end, clearer sections, potentially allowing emails outside of Macalester to schedule rooms, including a meet the staff section for contact information, having feedback sent to the Idea Lab’s email, and renaming the feedback section to a more general contact form with subject templates.</p><p>As a result of these discussions, our group had multiple goals to improve our design prototype. The main goals include: adding scrolling capabilities, adding a section for learning about and contacting staff members, fixing the taglines so that they appear to be taglines rather than buttons through changing their shape and placement, requiring a user to sign in before being allowed to access the scheduling flow, and fixing the orange color palette. In addition, we have decided that we will remove the sidebar and have more distinct sections.</p><p>The “more is more” philosophy with prototyping, as discussed in class, involves the importance of creating several prototypes rather than focusing all energy on one single prototype. This is due to the fact that, with more quickly completed prototypes, it is easier to determine various potential designs that could make for a better website. After choosing the quick designs that are thought to be the better designs, a designer can subsequently focus their energy on improving and polishing this particular design. Overall, the “more is more” philosophy suggests that a large quantity of prototypes allows for better design choices, as opposed to one single prototype design, due to the variety of designs created. As a result of this philosophy, each member of our group created two rough sketches of prototypes. We compared and contrasted our designs by noting which elements of everyone’s prototypes we believed we should keep and which elements we believed we did not need. We learned that, from the various designs, we wanted to have a color-coded calendar, a meet the staff section, and image carousels.</p><h3>Conclusion</h3><figure><img alt="Figure 2. Prototype 1 for in-class presentation" src="https://cdn-images-1.medium.com/max/378/1*0eE-L6fM19ldADdzndZbmA.png" /><figcaption><strong>Figure 2. Prototype 1 for in-class presentation</strong></figcaption></figure><p><strong>Figure 2. Prototype 1 for in-class presentation</strong></p><figure><img alt="Figure 3. Prototype 2 for in-class presentation" src="https://cdn-images-1.medium.com/max/380/1*DqlFCbGyUubW87lPBKTh3A.png" /><figcaption><strong>Figure 3. Prototype 2 for in-class presentation</strong></figcaption></figure><p><strong>Figure 3. Prototype 2 for in-class presentation</strong></p><p>Based on our test groups, we can conclude that our final design philosophy centered on making the Idea Lab website welcoming, understandable, and easy to navigate. During our initial explorations, we considered different layouts and ways to present the space.. Through paper prototype testing and the in-class critique, we learned that an appealing design also needs to clearly communicate what visitors can do. For example, the prospective student preferred the appearance of our more detailed paper prototype but still struggled to locate sewing drop-in information. Our final design placed greater emphasis on clarity. We revised the introductory description, removed misleading tagline shapes that resembled buttons, and added clearer headings and spacing. We also removed the persistent sidebar while retaining an accessibility pop-out. The calendar included a color key and weekly view and remained separate from room scheduling; this allows visitors to browse events without entering the reservation process. We added a sign-in step before scheduling, introduced a meet the staff section, and renamed the feedback section as a contact form placed at the bottom of the page.</p><p>On the other hand, low-fidelity prototyping helped us compare ideas and identify problems before investing more time in a polished design. Testing across three user groups helped us examine different goals, including finding events, suggesting workshops, and reserving space. Their feedback revealed unclear descriptions, confusing labels, and missing contact information. However, scrolling required demonstration, and paper could not fully communicate hover effects. Meanwhile, high-fidelity testing allowed us to examine strengths and remaining weaknesses. The prospective student found sewing drop-in information in both versions, the craft/art student easily located mending hours, and the event organizer could reach room scheduling. However, the prospective student needed guidance to suggest a workshop and found the booking capacity label unclear. The professor questioned whether the contact form supported requests beyond feedback, while both the professor and the craft/art student struggled to interpret the calendar’s event categories. Although testers liked the calendar, its categories and color code still needed clarification. Both prospective and craft/art students also preferred the blue and orange version over the purple alternative.</p><p>This project was a journey for us to learn that adding a feature does not automatically make its purpose clear. Comparing prototypes and observing testers helped us question our assumptions and connect design decisions to visitors’ needs. In a future revision, we would add inquiry categories to the contact form, replace abbreviated booking labels with plain language, and make calendar categories more distinguishable through text as well as color. We would also clarify navigation around the contact form and make links to staff information more visible. In future projects, we would test digital interactions earlier and leave more time to revise and retest them. Further testing with a broader range of visitors, including people with accessibility needs, would help us assess whether these changes make the website easier to use.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ccd0f5c1cfa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macalester-hci/dj-bas-idea-lab-proposal-5ccd0f5c1cfa">DJ-BA’s Idea Lab Proposal</a> was originally published in <a href="https://medium.com/macalester-hci">Macalester HCI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Idea Lab Website Redesign — Team Apollo]]></title>
            <link>https://medium.com/macalester-hci/idea-lab-website-redesign-team-apollo-d19058f23ea2?source=rss----7ac5db827006---4</link>
            <guid isPermaLink="false">https://medium.com/p/d19058f23ea2</guid>
            <dc:creator><![CDATA[Hayden Pierce]]></dc:creator>
            <pubDate>Mon, 05 Oct 2026 18:52:19 GMT</pubDate>
            <atom:updated>2026-10-09T23:55:32.179Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>For this design sprint, our group, Team Apollo, redesigned the Macalester Idea Lab website. We felt like the current site doesn’t always show some of its most important features as clearly as it should. The design also feels a little too plain in some places and a bit messy in others. Considering how creative the Idea Lab itself is, we thought the website could do a better job of reflecting that.</p><p>Our number one goal was to make information easier to find and clean up existing features while introducing new ideas that could make the site easier to use. We created two different high-fidelity Figma prototypes. One stays more consistent with the current Macalester website, while the other has more of a colorful and creative approach.</p><p><strong>Our final prototypes:</strong></p><p><a href="https://www.figma.com/design/U9Gz6i28QPaj95MpAqAt0S/Team-Apollo---Idea-Lab-Design?node-id=171-338">Prototype 1 — Macalester-Inspired Design</a></p><p><a href="https://www.figma.com/proto/KkPs2atdQNrXpfeEzI8szd/Team-Apollo---Idea-Lab-Prototype-2?node-id=325-2&amp;p=f&amp;scaling=min-zoom&amp;content-scaling=fixed&amp;page-id=0%3A1&amp;starting-point-node-id=7%3A2">Prototype 2 — Alternative Idea Lab Design</a></p><h3>Understanding the Problem</h3><p>We initially started by looking at the current Idea Lab website and finding some of its usability issues. Information felt harder to find than necessary, especially when it came to things like equipment, workshops, and reservations.</p><p>We focused on three main user groups: first-year students, student clubs, and faculty/staff. We picked these groups because they would probably be some of the people most likely to use the Idea Lab, but for different reasons.</p><p>First-year students may want to find tools, tutorials, hours, or workshops due to being unfamiliar with the idea lab. Student clubs might want to reserve space, find supplies, or organize events. Faculty and staff might want to check availability or reserve the lab for their classes.</p><p>From talking with Idea Lab staff, we also learned that they wanted the website to give people more information about the lab and make visitors more curious about the space in general. They had mentioned ideas such as clearer tool lists, better images, and helping people understand where equipment is located.</p><p>This influenced our direction because we realized the website shouldn’t just look better. It should also help people understand what they can actually do inside the Idea Lab.</p><h3>Starting With Paper Prototypes</h3><p>Before we started working in Figma, we created two different paper prototypes. We wanted to figure out the basic organization and navigation before spending too much time worrying about colors, fonts, or making everything look finished.</p><p>Our first paper prototype stayed more similar to the current Macalester desktop website. It included a sidebar, calendar, news, gallery, and a rotating circular menu for exploring different categories. We wanted to see whether the rotating menu could make navigation more interesting, and we believe it did.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LsPU5BsvMku63E4uOFM5Cw.jpeg" /></figure><p><em>Figure 1. Our original desktop-style paper prototype, showing the rotating menu, calendar, news, and gallery.</em></p><p>Our second paper prototype was more compact and originally looked closer to a mobile design. It separated Home, Workshops, Tools &amp; Supplies, and Reservations into different sections so visitors could focus on one task at a time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WZjUxPu4vwLnXqDWFjkhgw.jpeg" /></figure><p><em>Figure 2a. Our second paper prototype shows the original Home, Workshops, Tools &amp; Supplies, and reservation layouts.</em></p><p>We also made a more detailed paper version of Prototype 2 as we continued building off our ideas. This helped us expand on the original smaller layouts and better see how we wanted the website to look before moving everything into Figma.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nqGUjt2g4lwjWedKN7ywjA.jpeg" /></figure><p><em>Figure 2b. Our further developed paper prototype for the second design shows how we expanded on the original mobile-themed layout before creating the high-fidelity Figma version.</em></p><p>Making both versions helped us compare different approaches instead of immediately going all in on one design. Also, it was easier to make big changes at this stage before everything became more complicated with interactions in Figma.</p><h3>Early Usability Testing</h3><p>We followed this stage up by completing three usability tests with our paper prototypes. One was with a first-year student, one with a club member, and one with a professor.</p><p>The first-year student tested finding the Idea Lab hours, workshops, tools, and equipment. The club member focused on reservations, supplies, and workshops. The professor tested reserving the lab, checking availability, and finding information about using the space for a class.</p><p>Some of the most useful feedback was for making tools and equipment easier to find. One great idea that came from our testing was having an aerial, top-down 2D map of the Idea Lab with different stations labeled.</p><p>This eventually led us toward an A–Z tool finder, where users could select equipment or supplies and see their locations on the map. We also started thinking about making the calendar more concise and the navigation clearer.</p><p>One thing we took away from these tests was that people don’t always approach a website the way the designers expect them to.</p><h3>Prototype 1: A Familiar Design With New Features</h3><p>Our first high-fidelity prototype follows a more traditional Macalester-style website. We wanted to keep a similar layout while also bringing in new features that made the site more interactive.</p><p>The sidebar helps users navigate to different sections, including quick actions, reservations, the calendar, FAQs, and staff information.</p><p>One of the biggest features is the rotating circular menu, which was developed from our first paper prototype. Users can explore different categories, including workshops, equipment tutorials, tools and supplies, and reservations.</p><p>We thought this would be a more interesting way to explore the Idea Lab rather than having regular buttons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_YdXbZmTd5Y2tusxsCoycw.png" /></figure><p><em>Figure 3. Our first high-fidelity prototype develops the original paper design into an interactive website, including the rotating menu and event calendar.</em></p><p>The prototype includes an interactive calendar where users can click to see upcoming events and additional information. We also added drop-down FAQs, news and photos, and information about the people working in the Idea Lab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/1*Q-oUTTnPWHRX_r23ae1zlA.png" /></figure><p><em>Figure 4. The rotating interactive menu is used to easily navigate through the quick options in alternative to selecting them on the sidebar menu.</em></p><p>One strength of this version is its familiarity. Someone who already uses Macalester’s websites would most likely recognize the structure. However, the page is fairly long, and the rotating menu is less conventional, so users need to understand that they can interact with it.</p><h3>Prototype 2: A More Creative Twist</h3><p>Our second high-fidelity prototype took a different direction. Instead of staying close to the original design, we wanted something more colorful, organized, and unique to the Idea Lab.</p><p>We used the exact Macalester blue and orange colors throughout the design, with a consistent sidebar and four interactive categories on the home page to look like they are hanging from a tool shelf. This includes the menu options for workshops, tools &amp; supplies, equipment, and reserve.</p><p>When users select a category, the home page shows related information. We also created full pages for each category so visitors could find more details without making the home page too crowded.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MFKeoMAD73GSMX8c4RN83A.png" /></figure><p><em>Figure 5. Our second high-fidelity prototype uses a different visual style, with a menu sidebar and interactive tool shelf cards.</em></p><p>A problem we ran into was keeping everything visually consistent. Some earlier layouts had too many elements, inconsistent spacing, or buttons that didn’t clearly look clickable. We also had some issues getting the correct fonts input into the file.</p><p>We adjusted colors, spacing, borders, and selected states so the pages felt like they belonged to the same website.</p><p>One strength of this prototype is its overall aesthetic and interaction level. Although there is more going on visually, the home page could potentially feel busy to some people. We tried to balance that by keeping navigation simple and reducing any unnecessary clutter.</p><h3>Developing the Interactive Map and A–Z Tool Finder</h3><p>One of the biggest features we developed was the interactive Idea Lab map.</p><p>This idea came out of our early usability testing. We thought it would be best if visitors could see where equipment and supplies were located, especially if they had never visited the Idea Lab in person before.</p><p>We started with the idea of a simple top-down map of the lab. As we worked on it more, we added an A–Z tool finder so users could locate specific equipment instead of just looking at the room layout.</p><p>In Prototype 2, users can select items from an alphabetical inventory, and the 2D map shows the items&#39; location. We included things like the 3D printer, Cricut machine, sewing machine, scissors, and other supplies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4QiP3bljmNIPr4ybh_mxzg.png" /></figure><p><em>Figure 6. This map was developed from an early idea for a labeled room layout into an interactive A–Z tool finder showing supplies and their locations.</em></p><p>This was probably our best and favorite piece of feedback we received during any of the testing. We originally weren’t planning such a detailed feature, but it became one of the most useful parts of the prototype.</p><p>It also connects with Jakob Nielsen’s design principle of recognition rather than recall. Instead of expecting someone to remember where equipment is located, the website helps them visually find it.</p><p>The selected map markers also support visibility of system status, since users can see which location corresponds to their selection.</p><p>These are two of Nielsen’s <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">10 Usability Heuristics</a>.</p><p>The map is still within a Figma design file and doesn’t connect to a live website, but it shows how the feature could work on a real browser.</p><h3>Improving the Calendar</h3><p>Another feature we spent time improving was the calendar.</p><p>During our class critique, people mentioned that the schedule looked cleaner than the original, but we also received suggestions about having different calendar views.</p><p>In Prototype 2, we developed day, week, and month views, allowing for visitors to look at events and availability in different ways.</p><p>We also worked on making event names, dates, and times easier to understand by adjusting spacing, highlighting, and formatting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cxcq1qtnQ3iWcWBuGKhrgA.png" /></figure><p><em>Figure 7. Our updated calendar includes three viewing options, allowing users to check schedules in the format that works best for them.</em></p><p>This connects with Nielsen’s principle of flexibility and efficiency of use, since different visitors might prefer different ways to view information.</p><p>It also connects with aesthetic and minimalist design, because we wanted to remove unnecessary clutter without hiding important information.</p><h3>Class Critique and Design Changes</h3><p>We also got a lot of helpful feedback during our class critique. People seemed to really like the overall aesthetic of both prototypes, especially the Idea Lab logos, sidebar, interactive map, and rotating circle menu. Several classmates mentioned how clear the navigation was and how detailed the map looked.</p><p>We also got some useful suggestions about things that could be improved. One person mentioned that the spacing and text sizes varied between the home page and other pages which made them feel like two different websites. Others mentioned that some areas had too much text, that certain features felt repetitive, and that some buttons and layouts should be more consistent.</p><p>A few classmates also suggested having daily and weekly calendar views, using real Idea Lab photos instead of AI-generated images, and making the interactive map easier to understand.</p><p>We took a lot of this feedback into account when finishing our designs. In Prototype 2, we added Day, Week, and Month calendar views, improved spacing and button consistency, simplified some of the layouts, and replaced placeholder images with real Idea Lab photos. We also continued developing the interactive map and A–Z tool finder to make locating equipment easier.</p><p>For Prototype 1, the feedback also made us think more about the amount of text around the rotating menu, how the different sections were spaced, and whether the website felt consistent from top to bottom.</p><p>One thing we learned from this critique was that even when people like how a website looks, there can still be smaller usability issues that aren’t immediately obvious to the people designing it. Not every suggestion meant we needed to add something new, and sometimes removing or simplifying things was the best option.</p><h3>High-Fidelity Feedback</h3><p>As we continued to develop our Figma prototypes, we completed a second round of usability testing with three new people from our targeted groups: a first-year student, a student club member, and a faculty/staff member. We focused more on how people could actually scroll, click buttons, and interact with the website. This was much different from our paper prototype testing we did, which was more focused on the general layout and organization of everything.</p><p>For first-year students, we received feedback that it wasn’t originally very clear which item was selected in the A–Z tool finder. Based on this, we improved both prototypes by adding highlighted selections and circular markers to make equipment easier to find.</p><p>For student clubs, we received feedback that the reservation process in Prototype 2 was a little confusing, especially when choosing dates and times. We improved this by adding a clickable date picker with different reservation options and making it clearer which selections were made and how to change them.</p><p>For faculty and staff, we received feedback about wanting weekly and daily calendar options instead of only having the typical monthly view. We added daily, weekly, and monthly options, which gave users more flexibility and added a nice new level of organization to the scheduling aspect of our redesign.</p><p>Overall, this second round of testing helped us notice smaller issues with the actual interactions that weren’t as obvious when we were working with paper prototypes.</p><h3>Accessibility and Design Principles</h3><p>We also worked on accessibility as we developed the prototypes.</p><p>For our accessibility review, we looked at color contrast, text readability, button sizes, and navigation.</p><p>In Prototype 2, we used Macalester blue and orange consistently, with dark text on lighter backgrounds. We also improved smaller clickable areas and made selected elements easier to recognize.</p><p>This connects with the <a href="https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum">WCAG 2.2 target size guidelines</a>, which emphasize making interactive elements a good size or spaced apart.</p><p>Another principle we focused on was consistency and standards. Using similar buttons, navigation patterns, and layouts across the pages mean users don’t have to keep figuring out how the website works.</p><p>We also considered user control and freedom, especially for popups, reservations, and calendars. Users should be able to explore different options and return to where they were.</p><p>While we made improvements based on our accessibility review, Figma alone can’t fully test accessibility. A finished website would still need a keyboard, screen reader, and responsive design testing.</p><h3>What Worked and What We Would Improve</h3><p>Our paper prototype testing helped us understand how different people might use the website, while the later class critique gave us more feedback about visual design and interaction.</p><p>Of course, some features would still need more work before becoming a real website. The calendar would need live event information, reservations would need real availability, more tools and supplies could be added to the 2D map, and the equipment finder would need accurate, updated locations.</p><p>Both designs have strengths and weaknesses. Prototype 1 is more familiar, while Prototype 2 is more unique and separates information more clearly. However, the rotating menu in Prototype 1 may take getting used to, and Prototype 2’s home page could feel busy.</p><h3>Using AI During the Project</h3><p>We used AI for several parts of the project. It helped us create some Idea Lab logos and early image concepts, including ideas for the aerial map.</p><p>We also used AI for Figma tutorials, troubleshooting interaction problems, formatting issues, and making different features work. Later, we used it for some direct Figma adjustments, especially helping out with our Idea Lab map.</p><p>This saved us time because instead of searching through a bunch of tutorial videos, we could ask about a specific problem and get instructions for what we were trying to do.</p><p>However, we still had to review the results. Something generated by AI might look good but not accurately represent the actual Idea Lab.</p><p>This raised ethical questions, especially when using AI-generated images. We didn’t want to give visitors an inaccurate impression of the space, which is one reason we switched to using real photos.</p><p>We also recognized that equipment availability and reservations shouldn’t appear live or confirmed unless they are connected to accurate information.</p><p>Another limitation is that we focused mainly on three user groups. We would want to hear from more people, including students with different accessibility needs before treating either design as a finished product.</p><h3>Final Reflection</h3><p>One of the biggest things we’ve taken away from this project is that it can be pretty easy to make something look nice aesthetically, but making it interactive and easy to use takes it to a whole different level.</p><p>When we first started working in Figma, even just connecting buttons and pages took us some time. As we added calendars, rotating menus, reservations, and interactive maps, things became much more complicated over time.</p><p>We also learned how important feedback is throughout the design process. Some of our most useful ideas, especially the A–Z tool finder and map developed because we were thinking about what actual users needed on request.</p><p>Overall, we’re happy with how different the two prototypes turned out. Both have their own strengths and weaknesses, but they work toward our project goal of making the Idea Lab website easier to navigate, more informative, and more inviting for visitors.</p><p>If we had more time, we would continue testing the designs and explore how their features could eventually work with real Idea Lab information. The biggest lesson for us was that a successful redesign isn’t just about making something look better. It’s about making something people can actually understand and use efficiently.</p><p><strong>References</strong></p><ul><li><a href="https://www.nngroup.com/articles/ten-usability-heuristics/">Nielsen Norman Group — 10 Usability Heuristics</a></li><li><a href="https://www.nngroup.com/articles/recognition-and-recall/">Nielsen Norman Group — Recognition and Recall</a></li><li><a href="https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum">W3C — WCAG 2.2 Target Size</a></li><li><a href="https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum">W3C — WCAG 2.2 Color Contrast</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d19058f23ea2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macalester-hci/idea-lab-website-redesign-team-apollo-d19058f23ea2">Idea Lab Website Redesign — Team Apollo</a> was originally published in <a href="https://medium.com/macalester-hci">Macalester HCI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DJ-BA’s Idea Lab Proposal]]></title>
            <link>https://medium.com/macalester-hci/dj-bas-idea-lab-proposal-348445409a21?source=rss----7ac5db827006---4</link>
            <guid isPermaLink="false">https://medium.com/p/348445409a21</guid>
            <dc:creator><![CDATA[Bjuarez]]></dc:creator>
            <pubDate>Fri, 02 Oct 2026 19:44:51 GMT</pubDate>
            <atom:updated>2026-10-02T19:44:50.886Z</atom:updated>
            <content:encoded><![CDATA[<p>We designed low-fidelity and high-fidelity prototypes for the Idea Lab’s website.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=348445409a21" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macalester-hci/dj-bas-idea-lab-proposal-348445409a21">DJ-BA’s Idea Lab Proposal</a> was originally published in <a href="https://medium.com/macalester-hci">Macalester HCI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesigning the MSCS Home Page — by Team Seek]]></title>
            <link>https://medium.com/macalester-hci/redesigning-the-mscs-home-page-by-team-seek-080eff43cc39?source=rss----7ac5db827006---4</link>
            <guid isPermaLink="false">https://medium.com/p/080eff43cc39</guid>
            <dc:creator><![CDATA[Kayla Olivas]]></dc:creator>
            <pubDate>Fri, 08 Aug 2025 20:31:44 GMT</pubDate>
            <atom:updated>2025-08-08T20:31:44.034Z</atom:updated>
            <content:encoded><![CDATA[<h3>Redesigning the Math, Statistics, and Computer Science Department Homepage</h3><p><em>Savannah Haugen, Elan Levin, Ethan Caldecott, Kayla Olivas</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*trkELy151Ad_jTzBRvoZ-Q.png" /><figcaption><a href="https://www.figma.com/proto/cuLVKV079Z7DdMLp1RUsw0/Full-Figma-Prototype?node-id=3-397&amp;p=f&amp;t=rZx6y8fJyrHk2DhF-0&amp;scaling=min-zoom&amp;content-scaling=fixed&amp;page-id=0%3A1&amp;starting-point-node-id=3%3A397">Link to our Figma Prototype</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*mifrn7ZG-T162vdZxgVxhQ.png" /><figcaption>Our iterative design process from concept to the final prototype!</figcaption></figure><h3>Overview</h3><p>The current Macalester Mathematics, Statistics, and Computer Science (MSCS) website lacks in certain areas when it comes to user experience. Through trial and error, our task was to redesign certain parts of the website to make it easier for a certain user group to accomplish specific goals.</p><h3>Heuristic Evaluation</h3><p>We begun by evaluating the current MSCS website using Nielsen’s <a href="https://www.nngroup.com/articles/ten-usability-heuristics/#poster">10 Usability Heuristics</a> and looking for anything that violated a heuristic. We found many violations, and we will describe three here. These are the most prominent and widespread violations.</p><p>The first is that the website contains a lot of text and large text chunks, and it is rare for users to read the entire text. This violates the Aesthetic and Minimalist Design heuristic.</p><figure><img alt="A screenshot of the homepage of Macalester’s MSCS website, displaying large chunks of text." src="https://cdn-images-1.medium.com/max/1024/1*xBNMn7ti-pKr4lAPHRM2Qg.png" /><figcaption>Display of large chunks of text</figcaption></figure><p>The second is that the list of faculty and staff are not initially ordered alphabetically but rather by department chairs, department coordinators, and other professors. Also, there is no way to filter for specific professor departments or roles. This can be difficult to decipher for a user not in the MSCS department. This violates the Match Between the System and the Real World heuristic.</p><figure><img alt="A screenshot of the first three professors on the faculty and staff page of the MSCS website, showing that the list doesn’t start in alphabetical order, which is what a typical user may expect." src="https://cdn-images-1.medium.com/max/1024/1*pGw3COMvpEl6kQ0323vvDA.png" /><figcaption>Snapshot of the Faculty and Staff page</figcaption></figure><p>The third is that there is no FAQ tab on the main menu bar or on any main page of the website, which is unfortunate as these can help create shortcuts for the user. This violates the Flexibility and Efficiency of Use heuristic.</p><figure><img alt="The side panel of the MSCS website that does not contain an FAQ button." src="https://cdn-images-1.medium.com/max/374/1*fxL0V0MsShlE5bObOZ3y1w.png" /><figcaption>Main menu bar with no FAQ button</figcaption></figure><h3>Persona and Task Development</h3><p>The user group we decided to design for was <strong>transfer students who are interested in MSCS or have an MSCS major.</strong> We wanted to design a more simple, clean, and easy to understand interface than the current MSCS website. More importantly, we made sure to dedicate our attention to the features of the MSCS website that would be most important to a transfer student, and we came up with a task for each feature. They are:</p><ol><li><strong>Find where you can compare the courses you have already taken at St. Catherine University versus the ones that correlate to them at Macalester. </strong>We wanted to create a simple view to compare courses between a users’ current university and Macalester.</li><li><strong>Find the course progression of the CS Major at Macalester. </strong>We wanted to include an easy-to-follow course progression of the intended major.</li><li><strong>Find the chair of Computer Science at Macalester. </strong>We wanted users to easily find applicable professors of the intended major.</li><li><strong>Find out how to find a CS internship opportunity at Macalester. </strong>We wanted users to be able to look at potential student opportunities.</li></ol><h3>Paper Prototyping</h3><p>When creating our paper prototype, we started by refining the home page redesigns we made on the third day of class. We had two different designs to choose from, and we picked the one with a horizontal header and middle-split page body. When creating our header, we went back and forth between writing out what MSCS stands for and leaving just the acronym. To avoid visual clutter, we decided to just have the acronym on the header. To fill out the rest of the page, we included a frequently asked questions section, buttons for each major, and a picture of Olin-Rice.</p><figure><img alt="Homepage of our paper prototype with big buttons for majors, a picture of Olin-Rice Science Center, FAQs, and colored puffballs along the menu bar to represent something is clickable." src="https://cdn-images-1.medium.com/max/784/1*wL3BGGx9eurLFwBDegEINw.png" /><figcaption>Home page of paper prototype</figcaption></figure><p>We wanted to model the Computer Science page similarly to the main MSCS home page. We included the same four styled boxes with relevant CS-specific information, like courses, major and minor requirements, and faculty and staff. Once this page was completed, we began to think about how the computer science courses page would be structured. When designing this page, we wanted to improve the text-heavy, complicated design of the current courses page and make it easier to understand. We wanted it to be easier to decipher the progression of the computer science curriculum and see what order and pairings classes were frequently taken in. We decided to split them into intro, core, and elective courses, and omit the description to keep the page cleaner. We put the description in an optional dropdown. An important part of this page was the ‘Course Comparison’ button, which takes users to the next part of our design.</p><p>One of the most difficult tasks for us to design for was when a transfer student wanted to compare the courses at their school to Macalester courses. We talked about how we wanted to list the different courses, and how we wanted to compare them–by skill, by content, or by level. Ideally, we decided that we would be able to web scrape MSCS courses from any school’s website and create an accurate comparison to Macalester’s. However, for the prototype, we decided to only include local schools for the sake of simplicity. Once the drop-down ‘Choose your school’ section was selected, we wanted the screen split in two. One side displayed the selected school’s courses, and the other side would be Macalester courses. This would allow students to see how far in the Macalester curriculum they had progressed.</p><figure><img alt="A side-by-side course comparison of our paper prototype comparing St. Catherine and Macalester’s computer science courses." src="https://cdn-images-1.medium.com/max/630/1*lHoYz511PCT13YySGynSoQ.png" /><figcaption>Side-by-side course comparison of paper prototype</figcaption></figure><p>In our design of the ‘Faculty and Staff’ page, we wanted to prioritize organization by department and by role, to make it easy for prospective transfers to locate faculty in their desired department, or to view all of the department chairs. Throughout our design, we incorporated colored puffs to denote how each of the pages worked together. You can see this on our ‘Home’ page, on the ‘Course Comparison’ page, and on the ‘Faculty and Staff’ page included below. If you refer to our home page, you’ll see a blue puff over the ‘Faculty and Staff’ part of the navigation bar. This corresponds to the blue puff in the corner of the ‘Faculty and Staff’ page. This helped us keep track of and demonstrate to our usability test subjects what parts of the website lead to others. This was helpful in our usability tests, which are discussed in further detail below.</p><figure><img alt="The faculty and staff page of our paper prototype with professors listed in alphabetical order, general info about each professor, and a filter button to enhance the search process of finding a professor." src="https://cdn-images-1.medium.com/max/762/1*7FzGgE2voFLuwP-__oa1vg.png" /><figcaption>Faculty and Staff page of paper prototype</figcaption></figure><h3>Usability Testing — Round 1</h3><p>Our redesign was designated for a specific user group that would benefit greatly from our simpler take on the MSCS website. This user group specifically being: <strong>prospective transfer students looking to major in computer science at Macalester College.</strong></p><p>The two people we ran a usability test with were both from a different university and they were computer science students in real life. When we began the usability tests, we asked them to tell us a little bit about themselves and about how much time they spent on the internet. Both users said they use the internet every day. From here, we were able to gauge what the competency level was for navigating website interfaces.</p><figure><img alt="Image describing the usability test process." src="https://cdn-images-1.medium.com/max/284/1*EJbEdLOr2k61-u9Vwjdr4w.png" /><figcaption>Usability testing is a multi-step process to ensure we get the most valuable feedback as possible.</figcaption></figure><p>We started off both usability tests asking them to simply observe the home screen. As much as we wanted to tell them what exactly the website was about, we knew we had to see what they perceived to be the goal of the interface. User #1 noted that she enjoyed the picture on the home page — verifying that Macalester was a real campus. She immediately noticed the four squares in the middle of the screen and observed that she would be able to click on them. These were exactly our intentions thus far!</p><figure><img alt="A usability tester touching a “button” on the paper prototype of our MSCS website redesign." src="https://cdn-images-1.medium.com/max/1024/1*Ljx74XBf9Napny00dSDfDQ.jpeg" /><figcaption>Picture captured doing one of our usability tests.</figcaption></figure><p>User #2 also noted that she enjoyed the picture on the home page but took note that she did not understand what ‘MSCS’ meant on our header until she put together that the acronym were the names in the squares.</p><p>Both the users expressed that they liked the ease of being able to navigate throughout our prototype. They understood the added items that indicated something was interactive, for example, the post it notes on the home page and the colorful puffballs. When we asked them to go to a different page on the prototype, they tapped on the puffball that was within that page’s title. On the home page, they understood that the 4 sticky notes meant that they could be clicked on to go to another page. In the courses page of the protype, we included a drawn on icon to indicate drop down functionality. When tasked to find a description of the course, they clicked on those icons. The feedback we received was crucial for the development of our next prototype.</p><h3>High-Fidelity Prototyping</h3><p>Once we completed our first round of usability tests, it was time to use that feedback to create a high-fidelity prototype in Figma. We wanted to keep the simple, clean, and easy to understand layout we had in our paper prototype.</p><p>We started by individually designing a different page of our website. When we compared the designs as a group, we realized we needed a consistent structure and layout for our website.</p><p>The color choices, mainly the blue and orange, are the exact shades on the current Macalester website as outlined in their color palette <a href="https://www.macalester.edu/communications/visual-identity/colors/#:~:text=The%20primary%20color%20palette%20consists,used%20throughout%20our%20brand%20materials.">page</a>. We wanted to use the same consistency for the fonts; however, Figma did not contain the exact font types that Macalester uses, so we chose our own fonts:</p><ol><li>One for the text on the blue background at the top of the page</li><li>The other for everything else</li></ol><p>We chose rounded boxes for our main design shape for a sleek look, which we used for buttons, images, and other text backgrounds. For the blue boxes, we added transparent images, similar to Macalester’s website. We wanted to incorporate orange into our design, which we did for all of the main headers on each page.</p><figure><img alt="Home page of the MSCS website showing the layout with colors, boxes, images, and frequently asked questions." src="https://cdn-images-1.medium.com/max/1024/1*2x8e2hSWIlOotox1nbkPYA.png" /><figcaption>Home page of redesigned MSCS website</figcaption></figure><p>The toughest aspect when designing this prototype was the Computer Science course page and course comparison pages. It was difficult to get all the text boxes aligned on the course page as well as fit the side-by-side view of the course comparison page on one frame. In the next section, you will see the final result of the Computer Science course page.</p><h3>Usability Testing — Round 2</h3><p>We performed a usability test of our high-fidelity prototype on a new user, User #3, and a user that tested our paper prototype, User #2. User #2 expressed that they enjoyed the colors and large text, this was something they were hoping for after seeing our black and white paper prototype. Additionally, they liked the Frequently Asked Questions section that was throughout our page because it allowed for “easy access to the things they will most likely need to know.” Something they suggested was using less bold letters, similar to our header bar, because the consistent bold formatting disrupted the visual hierarchy, making it difficult for the user to distinguish which information was most important. To make an effective visual hierarchy, you need font weight, size, and spacing variations to guide users’ attention and indicate relative importance. And if we use bold text more sparingly, we can help users scan and absorb information more efficiently without overwhelming them. They noticed the course comparison button much quicker this time around than the first time since they said the button was small on the paper prototype.</p><figure><img alt="Computer science course page of the MSCS website showing the course progression and containing a compare courses button for transfer students." src="https://cdn-images-1.medium.com/max/925/1*VSb2mjZoSNUcRbGfqsZ59g.png" /><figcaption>Computer science course page from our high-fidelity prototype.</figcaption></figure><p>User #3 expressed that they enjoyed the layout of the squares and how consistent that was throughout our website. They commented on how they would of liked to know the credits of the courses that were on the computer science course page. We chose not to make any design changes based on the feedback about course credit visibility because our primary design goal was to streamline content comparison for prospective students, not full academic planning, which should be done with an advisor. This was a great tip considering that as a transfer student, their previous taken courses may be different credits than those at Macalester. Once they entered the course comparison page, they mentioned the convenience of being able to compare the courses side by side; however, they said it was confusing on what the side by side courses meant. “Are these exactly equivalent to each other?” was one of the questions asked when looking at the adjacent courses.</p><p>Surprisingly, we overlooked the difficulty of having too much bold text throughout our website could bring. We were also surprised that no one commented on how plain and simple our ‘Student Opportunities’ or ‘Courses’ pages were. This proves that the balance of conveying a lot of information needs to have certain spaces that are simple and not as flashy.</p><p>Overall, the usability tests proved their effectiveness throughout our redesign. It gave us different insights on what could be improved and was liked throughout the webpage. As a team we learned that everyone perceives an interface differently and we worked on trying to make it as accessible for as many people as possible.</p><h3>Developer &amp; Professor Feedback</h3><p>After iterating our website from our usability feedback, we produced a new version that was shown to other design teams. They liked several elements, such as the header structure and the overall simplicity. They commented on the ease of navigation due to the inactivity of our website’s hierarchy and on pages like the course comparison tools. Calling the feature “genius and “fascinating.” They also enjoyed the orange color in our header, a color of Macalester they felt was underutilized in the current site.</p><p>However, we also received new areas for improvement, such as concerns about the faculty font feeling too playful and needing a more professional typeface. This drove us to change to a font with a more professional and academic feel. There were some concerns with inconsistent spacing, box size inconsistency, and box not feeling button-like. This led us to change all the boxes and create a rounded edge across all of them to make them feel more button-like, creating a standard size of 325 x 275 px for all buttons. There were also concerns about page margins that felt inconsistent in white space, making the page feel unfished. We, in turn, adjusted all pages so they had similar margins, but for some pages, we left white spaces as we thought this contributed to our overall goal of simplicity and not overwhelming the user.</p><p>It was interesting to see the differences in the types of feedback we received from the other developers vs. the users. The user’s feedback was focused more on content and usability, and the designer’s feedback was focused on visual and structural quality, showing the benefit of getting feedback from different groups.</p><p>We showed the same prototype we showed the developers to our professor, Lauren Milne, who provided us with her feedback. One of her points is the Calendar on our CS page to replace it with the actual Google calendar on the current website, making our site feel more real. She also suggested the button boxes were bland and could benefit from a background image. This added to the page’s style, and we were able to make the addition while maintaining simplicity and not increasing clutter. Another concern was the format of the course page. The block differed regarding sizing from page to page, so we adjusted the course dropdowns accordingly. There was a difference between our CS and Home pages, and Lauren suggested we make the same format for consistency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aExWlGX7RMRqhSpwwzPlQg.png" /><figcaption>Side by Side of Final Home Page and Computer Science Page</figcaption></figure><p>We did this by taking the orange header we established on the home page as the primary heading message instead of the previous blue box within the text. We also adjusted all other elements of the CS page to mirror the Home page format.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4a_tZwY_X2nEQ4-9vIag6g.png" /><figcaption>Side by Side of Final CS Courses Page and Internships Page</figcaption></figure><p>This gave us the idea to do something similar with the internship page and make it look like the Computer Science course page regarding the dropdown, allowing us to establish consistency in the looks of all dropdowns.</p><h3>Presentation Comments</h3><p>Our final round of feedback came from the audience during our final presentation. The room of developers provided input using sticky notes categorized as “I like…”, “I wish…” and “What if…” At the end of the presentation, we received these notes, allowing us to reflect on their insights and make further iterations based on their feedback. During the presentation, it went smoothly; however, we did realize a bug in our mapping where we had not linked the pages to the course comparison correctly unless you used the FAQ, but if you used the transfer button on the course page, it skipped a step. It made us think about how, when in those situations, maybe it is best just to keep going instead of bringing it up, as the audience likely would not have known it was a bug unless it was for us saying it was something to keep in mind.</p><p><strong><em>I like…</em></strong><br>Of the 16 “I like…” comments we received, 12 were about the simplicity of our page, stating it was “very simple and concise” or saying something along those lines. This was great as one of the key goals of the page was to present the information with concise and straightforward navigation. The rest was centered around features that were new to our website, and the current ones do not have them, like the course comparison page and frequently asked questions areas, both of which people felt contributed to the ease of use and accessibility of our site.</p><p><strong><em>I wish…</em></strong><br>Out of the 10 “I wish…” comments received, all were unique commenters. Such as on our button, we remove the click here button to make it feel less phish-like. We had iterated from a previous version this week vs. this month, and now we’re presenting a monthly calendar, so this was an easy fix. Others like adding credits per course to make it easier for transfer students to compare, but overall, this gave us some good ideas for future work without indicating any factual errors, as none of the comments were repeated.</p><p><strong><em>What if…</em></strong><br>Of the 9 “What if…” comments received, they were also all unique critiques. One was about the color of the school buttons matching the color of the other blocks on the other page, and this change was implemented immediately after the presentation. The other gave us some good ideas for future work, like including a space for students to send questions and comments.</p><h3>Final Thoughts</h3><p>Reflecting on our design process, we believe that through these iterations and our process, where with every decision we made, we were guided by user feedback and usability principles, we were able to successfully create a final prototype that aligns with the core goal we set out to accomplish of making the MSCS website simple and easy to use for transfer students. The current site presents usability challenges for transfer students navigating course equivalencies, faculty information, and major requirements and resources. Our redesign directly addressed these issues, improving simplicity, accessibility, and ease of navigation, as confirmed by the comments we received in our final presentation. Overall, this project gave us an excellent opportunity to step into the mindset of our target users and design a website that truly meets their needs, allowing us to practice our user-centered design skills.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=080eff43cc39" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macalester-hci/redesigning-the-mscs-home-page-by-team-seek-080eff43cc39">Redesigning the MSCS Home Page — by Team Seek</a> was originally published in <a href="https://medium.com/macalester-hci">Macalester HCI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>