<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Natalia Blaszczyk Alves on Medium]]></title>
        <description><![CDATA[Stories by Natalia Blaszczyk Alves on Medium]]></description>
        <link>https://medium.com/@natalia-alves?source=rss-8129ef1636ef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rkkK13wI6Ll0aG8NYlRyfg.jpeg</url>
            <title>Stories by Natalia Blaszczyk Alves on Medium</title>
            <link>https://medium.com/@natalia-alves?source=rss-8129ef1636ef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:01:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@natalia-alves/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How You Arrive at an AI-Native Design Workflow]]></title>
            <link>https://medium.com/outsystems-engineering/how-you-arrive-at-ai-native-design-workflow-638481a732e8?source=rss-8129ef1636ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/638481a732e8</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Natalia Blaszczyk Alves]]></dc:creator>
            <pubDate>Thu, 21 May 2026 08:56:00 GMT</pubDate>
            <atom:updated>2026-05-21T08:56:00.698Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>One small step at a time, with some digital workout</em></h4><p><strong>TL;DR</strong></p><ul><li>Designers have always lived with a gap between what we design and what actually ships. AI enables us to close that gap.</li><li>I started small, using AI to summarize meeting notes. Eighteen months later, I was orchestrating it to asynchronously implement GitHub issues while I worked on something else entirely.</li><li>Along the way, our UX team built a working prototype environment with a real design system, interactions and a data model that behaves like the actual product.</li><li>Now I’m experimenting with Claude Routines to close the loop between design feedback and code implementation with minimal babysitting.</li><li>The biggest thing I learned: AI doesn’t replace thinking. It removes the friction that gets in the way.</li><li>This is what becoming AI-native actually looks like — a series of small workflow shifts that slowly change how you build products.</li></ul><p>Last year, I was copy-pasting meeting transcripts into a chat window and asking for bullet-pointed notes. Now, I have an AI agent picking up GitHub issues it had written itself from feedback our team gave during a prototype review and implementing them while I’m doing something else entirely.</p><p>That’s not a before-and-after story. It’s a slow accumulation. And that’s the part that usually gets left out when people write about AI at work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jK8WbA1rn7F8p-TXvesLEw.png" /></figure><h3>Where it started: the boring stuff</h3><p>In late 2024, I started using Gemini, mostly to summarize meeting recordings, research notes, user interviews and usability tests.</p><p>It was useful in a quiet, unfancy way. I’d turn on transcription for every call, save the file, drop it into Gemini, and get a summary I could share with the team. Nothing that would make a conference talk, but it was saving me real time, and more importantly, it was building a habit: <em>capture everything, then let the AI process it.</em></p><p>In mid-2025, I was working on an architecture-tricky, UX-heavy initiative involving multiple rounds of solution design workshops, user interviews, and usability testing. I created a Google NotebookLM for the project and fed it everything relevant: meeting transcripts, interviews, usability session transcripts, Confluence docs, public product documentation, and even cherry-picked Slack conversations.</p><blockquote>It became something I genuinely relied on. It held context that would have otherwise lived only in my head.</blockquote><p>When someone asked me a question, I’d validate my response in the notebook first. When I needed to write a summary for stakeholders, I’d ask it to draft one based on what we’d discussed over the past weeks. But the biggest shift happened during the second round of usability testing.</p><p>Before AI, running five usability sessions meant roughly a week of follow-up work: re-watching recordings, writing up observers’ notes, creating an affinity diagram to find patterns, and building the slide deck to present findings. One week for the sessions, another week just for the write-up, because the rest of the calendar doesn’t pause for research.</p><p>With the notebook already loaded with the first round of results, and with transcripts from the second round fed in immediately after each session, I produced a comparative report within two hours of finishing the last session.</p><blockquote>It wasn’t that the work got easier. It was that the tedious part disappeared. No more re-reading, pattern-matching across dozens of notes, and filling in the results presentation template. The thinking and the judgment were still mine. The grind wasn’t.</blockquote><h3>Learning to code (sort of)</h3><p>In November 2025, I installed Cursor. I’d been watching colleagues use it, and my manager <a href="https://www.linkedin.com/in/filipalexasousa/">Filipa Sousa</a> had been encouraging the whole team to explore AI tools seriously. She’d been running regular AI benchmarking sessions where we’d spend an hour experimenting with new tools and sharing what we found.</p><p>I started working on a GitHub repository for ODC Portal (OutSystems Developer Cloud management console) prototypes a fellow designer had created. Which meant I also had to start learning Git. Suddenly, I was stepping directly into the shoes of a developer, that is, the persona we’d been designing for all along, the user whose shoes we’d always tried to imagine. Now we don’t have to imagine anymore.</p><p>For the first few weeks, I didn’t really understand what the AI agent was doing on my behalf. I was giving it instructions and trusting the process. Then I lost a full day of work because I didn’t know I had to commit before pulling. I pulled, merged, and overwrote my local uncommitted work. That was when I realized I couldn’t treat the tool as a black box. I had to understand what was happening under the hood. I started reading the agent’s reasoning before accepting its suggestions. I started asking it <em>why</em>. I created the user-level md file to tell the agent my profile: what I know and don’t know, what I’m learning (“I’m learning git. I want you to explain git commands so I can run them myself in the Terminal.”) and how it should talk to me (ELI5 software development).</p><blockquote>The agent wasn’t just my minion anymore, it became my teacher and my rubber duck.</blockquote><h3>Code closes the gap and unlocks better design</h3><p>Until recently, there’s been a gap between the complex enterprise workflows, multi-stage interactions, data-heavy interfaces we design and what actually ships. Product prototypes had to fake things. If a user went off the happy path, they were asked to imagine what would happen. We skip complex interactions because they are too tedious to mock up. Then, when delivery is running at full speed, developers often design the edge cases themselves because designers don’t have the time to define them. As a result, something always gets lost between a Figma mockup and production code.</p><blockquote>For years, designers worked around that gap. It was just part of the job. And now AI coding tools give designers a way to close the gap themselves.</blockquote><p>The UX team at OutSystems built an AI-native prototype environment without needing to bug any engineer. Asking the agent to implement some of our design system components started as an experiment, but now it has grown into a living replica of the whole OutSystems platform. We can quickly spin off prototypes for new features we’re building together with engineers and product managers. These prototypes aren’t approximate mockups anymore, our test participants interact with something that looks, behaves, talks, and shows data like the real product.</p><p>Our repository now features not only our whole design system but also:</p><ul><li>A mock database mirroring the platform’s real data model.</li><li>Service calls that match real production API contracts.</li><li>An inspector layer that lets us see exactly what design system components are in use and which variant of each.</li><li>Custom AI “skills” trained on our ways of working: how to write UI copy according to our product style guide, how to run git operations, how to generate handoff documentation, and even how to run design critiques and brainstorm alternatives when you need a thought partner and no one’s free to meet.</li></ul><p>Importantly, this also brought us closer to our engineering peers. Building in code means thinking about scalability, data constraints, and edge cases as real problems, not abstract ones.</p><h4>Test anything, now that you don’t need to fake everything</h4><p>One of the features we were designing involved scheduling software updates across multiple deployment stages. The date picker had to work so that the selectable date range for each stage adapted dynamically depending on what had been selected for the others, which enforces a real business logic constraint. When we changed the maintenance window or update cadence, the full timeline preview updated live.</p><p>This kind of conditional logic is impossible to simulate faithfully in Figma. In a code prototype, it just works. Which meant we could actually observe a real-life scenario and surface corner cases, not just whether someone could navigate a mockup with a predetermined answer.</p><h4>Add use cases on the day of the test</h4><p>The day before a round of usability testing, the product manager mentioned it would make sense to include an email notifications configuration pop-up in the feature we were testing. In Figma, I’d have skipped it. There were too many components and variants to build and wire overnight. Instead, I took a screenshot of a similar existing feature in our portal and gave it to the agent. Half an hour later, the flow was in the prototype. I tested it with real users the next morning.</p><h4>AI designs what you forget to</h4><p>Building in code forces you to be explicit about edge cases that static design tools let you leave vague. While building the scheduling prototype, I noticed a “Discard unsaved changes?” confirmation dialog, which I hadn’t asked for. The agent had added it proactively because it understood the interaction well enough to know that navigating away from an unsaved form without a warning would be a broken experience.</p><blockquote>Building in code makes visible what you were implicitly leaving undesigned. It makes you a more thorough designer.</blockquote><h3>Closing the feedback to code loop</h3><p>But after several months, I started getting fed up with mentally compiling what needed to change, opening Cursor or Claude, typing out the requirements, answering the agent’s questions, and clicking “Allow” repeatedly. My developer colleagues have a name for it: babysitting the agent. That’s what pushed me toward the next phase.</p><p>My team runs recurring solution design review sessions. Together, Product, UX, and Engineering look at the current state of a prototype of a feature we’re designing. The feedback is valuable yet easy to lose. We discuss lots of details and days later, no one remembers exactly what was decided. I’m building a workflow to fix that loop:</p><ol><li>After the recorded session, I download the transcript.</li><li>Claude reads the transcript and turns the feedback into a structured to-do list in the form of GitHub issues, written in accordance with the repo context.</li><li>I review and validate the issues. When they’re right, I add the label claude-ready.</li><li>A Claude Routine, a recently released feature that lets you define conditions under which an agent acts without you in the loop for every step, picks them up and implements them — asynchronously, while I work on something else.</li></ol><p>The first time I tested it, the results were humbling. The implementations required more iteration than I’d hoped because the issues needed to be more specific than I’d expected. But this friction turned out to be useful. To make this workflow work, I had to get precise about things I’d previously left implicit: what is the definition of “done” for a piece of design feedback? How do you translate an ambiguous idea into a context an agent can act on, and how can you validate the output?</p><blockquote>Making the implicit explicit is just a better design practice, independent of any automation.</blockquote><h3>What I’d say to someone starting this journey</h3><p>None of this started with “let’s build an AI-native feature design workflow.” It may take you longer than you think. But that’s not a problem. The journey counts as much as the end goal. Each step may feel small, but they compound and each one only becomes possible because of the one before. You can’t skip to the orchestration phase.</p><p>My advice to someone who hasn’t started is not to wait for someone to show you the way. You learn it by doing it, breaking it, and figuring out why. I think you’ll find that more engaging than following a ready-made process someone else defined for you. At its core, it’s still the same thing good design has always required: clarity, systems thinking, iteration. That’s just design thinking with a new medium.</p><p>And one last thing: I work in design, not engineering. I didn’t come into this with a coding background. If you’re reading this, thinking <em>this isn’t for me, I’m not technical enough</em>, I’d gently push back. The hardest part of this journey wasn’t Git or GitHub or prompting. It was getting comfortable with uncertainty and iteration.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=638481a732e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/outsystems-engineering/how-you-arrive-at-ai-native-design-workflow-638481a732e8">How You Arrive at an AI-Native Design Workflow</a> was originally published in <a href="https://medium.com/outsystems-engineering">OutSystems Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ideation of an IDE: Making Better UX Decisions When Racing Against Time]]></title>
            <link>https://medium.com/outsystems-engineering/ideation-of-an-ide-making-better-ux-decisions-when-racing-against-time-2aa3eae6b283?source=rss-8129ef1636ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/2aa3eae6b283</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[outsystems]]></category>
            <dc:creator><![CDATA[Natalia Blaszczyk Alves]]></dc:creator>
            <pubDate>Fri, 08 Oct 2021 19:33:29 GMT</pubDate>
            <atom:updated>2021-10-11T14:51:57.680Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_3NPSaoQmtBp4nYITg0Z6Q.png" /></figure><p>Is there anything worse as an UXer than knowing your users are having a less than ideal experience? I know; we’ve all felt that pain before.</p><p>All companies sometimes face the formidable challenge of focusing on a specific market segment. Inevitably, whether by sheer impossibility or curated decision-making, some of your users will be left behind.</p><p>At OutSystems, that’s exactly how we felt about our integrated development environment (IDE), Service Studio. It worked great for our Windows users. For those running macOS? Well, not so much.</p><p>But the good news is that <a href="https://www.outsystems.com/blog/posts/introducing-outsystems-for-mac/">OutSystems launched a new version of its IDE in July 2021</a>. Now, there’s a cross-platform Service Studio that allows our users to natively run our IDE on Windows or macOS. This was a massive migration challenge, and <a href="https://www.outsystems.com/blog/posts/dot-net-react-js-a-love-affair/">we already went into detail about the Engineering decisions behind it</a> from the perspective of one of our principal software engineers.</p><p>As Product Designer for this major project, I will give you the scoop on all the UX work behind the screens and guide you along our thought process so that if you ever face such a massive challenge, you can better prioritize.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rDs4fArIN9-xIyo0" /><figcaption>Our IDE, Service Studio, before</figcaption></figure><h3>A Compromised Experience</h3><p>There’s no other way to say this: Service Studio was built for Windows. Our Mac customers were facing the added cost of providing their OutSystems developers with Virtual Machines (or computers running Windows) or dealing with the suboptimal experience offered by Service Studio’s Wine version.</p><p>Believe me, this was not something we could blissfully live with. At OutSystems, we take pride in our UX Team and <a href="https://www.outsystems.com/blog/posts/grow-ux-practice-for-max-product-impact/">are committed to growing our practice</a>, consistently delivering a product that users will love.</p><p>So, we were driven by giving our users a version of Service Studio they could natively run on their Macs and an IDE we could improve faster. This was not an easy task because we’re dealing with such a complex product.</p><h3>A Single Stack Service Studio</h3><p>As we began looking for optimal solutions, we knew we had to compromise between technology, user experience, and time. We had several options on the table — a fully-native Mac version, a Web IDE, a Wine version, a partially-native Mac version — and we needed to start ruling them out.</p><p>There was already an experimental Wine version of the Service Studio. Wine is a compatibility layer that allows software developed for Microsoft Windows to run on Unix-like operating systems. That was our attempt to cut off time, but the result could be considered sufferable from a technology and UX point of view. We felt it was not the way to go.</p><p>After evaluating the technical feasibility, development and maintenance efforts, and the user experience of each solution, we decided that single stack, installable versions for both Windows and Mac were the best approach we could currently provide.</p><p>But deciding to compromise was just the first of an array of difficult decisions we had to make along the way.</p><h3>Decisions, Decisions</h3><p>First: technology. The team chose ReactJS for its front-end technology, as we had to migrate the entire Service Studio’s interfaces. We meticulously listed all the dialogs and parts of the main interface to estimate the migration effort.</p><p>The list rounded off at 70 editors because we treated dialogs and parts of the main interface as editors along with 14 infrastructures. The migration estimate with the team we had at the time? Two and a half years. You read it right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*AjifLRhMYlu7gYXhp840Qw.png" /></figure><p>Needless to say, we weren’t happy to make our users wait that long — it was time to contemplate trade-offs. The first step was running some user experience research to figure out how to cut the Service Studio elephant into pieces. At the time, we aimed to get <em>the </em>best minimum viable product (MVP) and subsequent milestones to iterate before having a complete version with all the migrated editors.</p><p>From the dev side, the strategy was to kick off the migration process with the most straightforward editors, such as Login, Progress, or About dialogs, so that the team could learn the technology and work out the most efficient path.</p><p>The most extensive, complex editors — we’re looking at you, User Interface (UI) editor — were left for later. This decision naturally impacted what the MVP would be.</p><p>As part of our research, we surveyed our community of Mac users, did user interviews, and analyzed telemetry data to discover the most common use patterns regarding the Service Studio functionalities. With this data input, we considered possible MVPs and analyzed their value for users:</p><ul><li>Services-only version: we discarded it because it brought little value, failing to leverage user adoption and, therefore, feedback.</li><li>Front-end development version: we discarded it because it was difficult to specify a valid front-end user journey. In other words, it’s impossible to work on the app’s UI editor without having logic and data editors.</li><li>Back-end development version (logic and data): this was our first chosen MVP — as you might have guessed, we left the UI-related editors for later. They were more than we could chew at that moment.</li></ul><p>At the same time, designers started the mockups for the new version. This was a long-awaited opportunity to create and implement a design system — making our product more consistent, prettier, and easier to use. <a href="https://www.outsystems.com/blog/posts/a-talk-about-design-systems/">You can read more about this in a series of articles highlighting how our UX/UI Team tackled the new IDE challenge</a>.</p><h3>Picking the Low-Hanging Fruit</h3><p>When you start updating an existing project, you always want to improve it to the best of your ability, and Service Studio was no exception. We had a long list of possible improvements, <a href="https://www.outsystems.com/ideas/?page=1&amp;q=&amp;t=&amp;s=&amp;c=&amp;o=trending&amp;scat=ideas">some of which were submitted by our community of developers programming with OutSystems</a>. A migration seemed like an excellent opportunity to do it all. However, as always, there were constraints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*xHFu0-FIZwAvnmby" /></figure><p>One of the things we couldn’t compromise was the users’ familiarity with the Service Studio interface. If we did something too revolutionary, users would lose their precious time learning how to navigate it, which would go against our productivity principle. We aim to boost users’ productivity, not hinder it. So, instead of being revolutionary, we opted for an evolutionary approach.</p><p>If you’re still thinking about our two-year deadline, let me assure you that Service Studio is a <em>big </em>tool. Two years was actually a tight deadline and an extremely optimistic estimate based on the solution we had.</p><p>Did this deadline factor in enough time for potential changes and improvements? *<em>Ahem</em>* But you know how it is when it comes to estimating software development efforts, don’t you? 😁</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/0*SAGbnN1cVNrh3DkF" /></figure><p>So, with the clock ticking, we didn’t really have time to design or test massive changes or even the improvements we wished to add. We had to make decisions and make them wisely. If we proposed an improved solution that was more complex to implement, we’d be delaying the final delivery date. To win the race against time, we decided to focus on the low-hanging fruit: high-impact UX improvements with low cost of delivery.</p><p>Let’s take the widget Tree as an example. We often observe that new users struggle to understand and find the small button that displays the Tree. In the cross-platform IDE, we created two tabs: Elements and the widget Tree. To change to the widget Tree view we no longer have a small, easily missed button, but a tab — a big hit target that gives the widget Tree the much-needed visibility. Easier to click, easier to use.</p><p>On the other hand, it takes up the vertical space from the module Tree, but we decided it’s a worthy trade-off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*TuqZuFeR4EZb1Tf2gUgk3A.png" /></figure><p>Another example where we had to compromise is the Properties pane. It used to be a table, but now we have labels and inputs in the new cross-platform IDE. We’ve designed a better version, where the boolean properties, for example, appear as switch buttons or advanced properties in an accordion-style menu. Still, it’d be too costly to implement at that time.</p><p>As it stands, we’re aware it takes up more vertical space than it should, and we’ve already received our users’ feedback on it. All we can ask them is to bear with us; this is just the first step of the improvement path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*A3BzcKVOJ0Qv0uVlMxEpFg.png" /></figure><h3>Telemetry As a Proxy of Your User Needs</h3><p>One could expect that deciding on what to compromise would become easier along the way, but that was definitely not the case. As the final delivery date approached, it was harder and harder to let some things go. It was time to embrace an even more meticulous approach, and one tool that helped us achieve that was telemetry.</p><p>With telemetry data, we could pinpoint where users interacted the most (or not at all) with the software, which then guided us to migrate the most common use cases first, leaving less used features for later.</p><p>One such example was the often ignored Structure editor — RIP — which we did not migrate as its functionalities are now available within the Tree and Preferences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*G39Lcu2rlfNiGiijZhQR5g.png" /></figure><p>We also decided to implement a simplified version of the Entity editor, which contains only the settings that are not available in the Tree and Properties pane.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*O7Ywf3WMeOnTCUTXrFr6mA.png" /></figure><h3>A Bug That Became a Feature</h3><p>But the drop list does not end here. The Data Type dialog endured a similar fate, and we let it go due to a bug. Our telemetry data later backed up the decision.</p><p>In Service Studio’s Record Data Type, we show the user the data type structure in the Tree. In the previous version of Service Studio, you couldn’t edit it.</p><p>However, in the new version, we realized we could edit the structure in the Properties, which sparked an idea: why don’t we edit the Record and the Record List data types there, so we don’t need a dialog anymore? These can be edited as simple data types that don’t require in-memory structure and can be easily defined in the Properties.</p><p>This was an important lesson learned: finding redundancies within your product can help you save time and effort when upgrading it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*KyOulrhqS0OsWPvWX_U2DA.png" /></figure><p>In fact, what we managed to save in dev costs by not migrating some dialogs, we used in feature improvements whose costs would be otherwise harder to justify. Savings made by dropping the Data Type dialog were invested in further developing the Autocomplete and Search capabilities in the Data Type property dropdown, which previously offered a somewhat cumbersome interaction experience.</p><h3>Card Sorting With a Twist</h3><p>Since time was of the essence, another tool that helped us prioritize the work was card sorting. Usually, the card sorting technique is used to understand how your users organize information or create an information architecture, such as a menu on a huge website. We added our own little twist to it and ran an online card sorting exercise with our users to gather feedback and better understand our priorities.</p><p>We put each missing feature on a card and asked them to drag each card into one of the following buckets:</p><ul><li>I need these features ASAP.</li><li>I need these, but I can wait.</li><li>I need these eventually.</li><li>I don’t use these.</li><li>I didn’t know these existed.</li></ul><p>This gave us an insight into what our users were expecting. Some of the results surprised us: features we thought were must-haves were not that crucial for users. The first law of good UX? Never assume you’re the user 😉​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pl8t_g4ORiabwJFP" /></figure><h3>The Hardest UX Compromise</h3><p>Like so many other products, Service Studio comes with its own set of tutorials to guide the users on what they should do. What’s quite unique about it is that it also validates the users as they follow our instructions — if the user strays, then the IDE’s tutorial will help them return to the main guided track; when they perform an action, the tutorial lights the way, indicating the next steps. It all happens with a little helping arrow that points users to the elements they need to interact with to complete the task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/0*Uu6gbn00tx0BuShY" /></figure><p>Unfortunately, this capability has an extremely high dev cost. The tutorial is essential because it’s there for the user from the very beginning. Still, on the other hand, each user only goes through it once and for a few minutes — thus, it may be considered insignificant for the product experience as a whole.</p><p>However, these few minutes are crucial to lure in users or show newbies the value of OutSystems. It also entices them to explore the IDE further. Again, we had to agree on a compromise.</p><p>We came up with an incremental solution. First, we made an MVP: when the user clicked on the Tutorial in the Help menu, they were taken to a website with a video recording of a person building the tutorial app and explaining every step. This solution was clearly insufficient — the user would have to juggle between the browser and the IDE, try to remember the steps, and pause or rewind while fiddling with an imprecise playback slider. So, in the meantime, a different group of devs worked on a solution: the “walktorial” (at least that’s how we code named it).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bQ_DkYLVmts2fjBv" /></figure><p>Now, what exactly is the walktorial? We had the idea to create our initial tutorial using the already migrated walkthrough infrastructure. This meant it wouldn’t have the key capability of validating the user’s actions. The user would have to navigate independently, clicking on the Next button after performing the instruction or clicking on the Previous button if they got lost.</p><p>In sum, there is a lot less hand-holding. We also had to ditch the helping arrow because we weren’t validating the users’ actions and risked having it pointing to the wrong element. During the usability tests of the MVP solution, we learned that watching the video of someone interacting with the IDE really helped users even if the user experience we provided was far from excellent. This sparked an idea to include animated gifs in the walktorial to better guide our users and ensure a pleasant experience.</p><p>We did some user testing and were relieved to see that users completed the walktorial as easily as with the original tutorial. Another one bites the dust.</p><h3>Changing the Wheels on a Moving Car</h3><p>One of the most challenging things for a product designer or anyone building software is that any changes to your product or its user experience will be subject to heavy scrutiny by users and will eventually need to be readjusted. During the process of creating the new cross-platform IDE, we learned that the hard way.</p><p><a href="https://www.outsystems.com/blog/posts/dot-net-react-js-a-love-affair/">As my teammate and Principal Software Engineer João Neves explained in his article</a>, we released the new migrated editors in the legacy (Windows-only) version. Yes, that’s right, our users were partly experiencing the cross-platform Service Studio even before its launch. For instance, one of the first dialogs we migrated was the one displaying the Shortcut keys, which was first released to Beta users and then made available to all users in April 2019.</p><p>We created a theme that blended well with the legacy interface to make the migrated editors look consistent. At the same time, <a href="https://www.outsystems.com/blog/posts/how-we-landed-products-visual-sophistication/">we worked on two new beautiful looks for the new version of the IDE</a> — the light and the dark theme.</p><p>Although we automated the theming as much as possible, <a href="https://www.outsystems.com/blog/posts/redesigning-icon-system/">it still added extra work to the checklists of designers and developers</a>. To avoid dealing with a gazillion color variables, we intended to derive the dark theme from an inverted version of the light theme.</p><p>But, as we learned:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*Lr_TuH7ma9V_y-g5cNC5NA.jpeg" /></figure><p>It just didn’t look good. The dark mode, for example, should have a softer contrast and less vibrant colors. We had to make adjustments, mainly in the text color rules and background colors of some components, such as tabs and inputs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gpVH8giXOdu7St4A" /></figure><p>On top of that, we had different sets of icons for the current and latest versions. As we didn’t want to end with separate icon sets for the light and dark themes — raising the number of icon sets we would have to deal with to three — we decided to compromise once again and find an icon color palette that would work for both themes. <a href="https://www.outsystems.com/blog/posts/redesigning-icon-system/">It was more challenging to design and test</a> but also more straightforward to implement and less costly to maintain and change when needed.</p><p>The story pretty much repeated itself when it came to illustrations. Once more, there were two different sets of images for each version (old and new), and we struggled with the very same color palette challenge.</p><p>Now, exceptions had to be made when creating some icons or illustrations, especially for the dark theme, as our creations wouldn’t always work for both. Since we were dealing with a single code, we had to implement a fall-back mechanism:</p><ul><li>The system checks if the user is running the old version.</li><li>If so, it loads a legacy image.</li><li>If not:</li><li>Is the user using the dark theme?</li><li>If so, the system checks if there’s a dark image available, and if there is, it will load it.</li><li>If not, it will load the light theme image.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*6xtr3mE72noWFU8A-H8t7w.png" /></figure><p>This required tremendous discipline when creating and committing any image assets, as well as meticulously curating the CSS differences between each theme. Testing also extended for longer than anticipated as every piece of the interface had to be implemented and then tested in all three themes.</p><h3>How to Keep Everyone on the Same Page</h3><p>This project started small, with one dev team, but more and more people joined. At some point, we had up to 50 developers, QAs, designers, POs, and tech leads working on this project. At OutSystems, we follow the SAFe methodology in which we have a week of planning for the following five sprints (the so-called Product Increment or PI for short). It helps especially with managing dependencies between teams in large organizations like ours.</p><p>Having five teams working on the same project, we realized we needed a central prioritization tool to align everyone with the goals and priorities. We decided to use the user story mapping, a technique promoted by <a href="https://www.oreilly.com/library/view/user-story-mapping/9781491904893/">Jeff Patton in his book of the same title</a>.</p><p>We organized our pending work along two vectors: the user journey (from installing and opening the IDE to building an app, publishing, testing, debugging, and distributing) and the PIs schedule.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n-fvhup0sdj7V5tG" /></figure><p>We held weekly meetings where we discussed the items (user stories) on the map: if their priority should rise or fall based on the telemetry data, card sorting, and feedback from customers and users.</p><p>Before each PI planning, we decided what we wanted to accomplish based on these priorities and the teams’ delivery capacity. We’d put these user stories in the top-most row of the map. Then we’d distribute them between the groups so that each team knew their work scope for the upcoming PI. This way, we could detect dependencies sooner and avoid them by better distributing the user stories between groups or PIs. Doing this made PI planning, including the dependencies management, much smoother and more predictive.</p><h3>Perfect Is the Enemy of Done</h3><p>We were still immersed in doubts, despite two and a half years of hard work in which we tried to achieve all of our goals as quickly as possible. We’re perfectionists who always believe there’s something to improve, and this was no different.</p><p>We didn’t feel ready to go into general availability: some features, including one that we found crucial — the edition of the UI on Traditional Web apps — were missing. Besides, we had reported 250 bugs and counting. The quality we aimed for wasn’t there yet. To top it off, the new Service Studio kept crashing more than its predecessor.</p><p>We felt trapped in this unsolvable dilemma represented by the famous triangle:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*MbgJdMrUlQMPi_OULaT0Fg.png" /></figure><p>Eventually, we decided it was more valuable for Mac users to have a new and improved version, even if it lacked all the features of the previous Windows version. The attempt release date was set. We stopped development and focused on fixing bugs, adding two extra teams. Moreover, we kicked off the Bugmageddon initiative — in five weeks, we fixed 84 bugs. In this period, we also reached target stability. But more on that on an upcoming blog post.</p><p>Finally, on July 29, 2021, the new Service Studio was out, and all we could do was anxiously await our users’ reactions. So far, we’ve been getting a great response.</p><p>Some users give positive feedback…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K8H01e0K18HZ8xiw" /></figure><p>Others are helping us improve…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n8xNNhSP6x2u9U-5" /></figure><p>But, because we value our users’ feedback above everything, we’re actively working on bettering the new version. We are migrating features, fixing bugs, and completing more under-the-hood work (including things our users don’t experience and which we, therefore, deprioritized, such as the telemetry that enables us to monitor the product’s usage and make decisions about its evolution).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O4BwtOckAwdv9O2s" /><figcaption><em>The new cross-platform IDE</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GUl0k6E0ldbQVarm-474kg.jpeg" /><figcaption><em>Cross-platform IDE’s team</em></figcaption></figure><p>If you’re using the new Service Studio at the moment, bear with us. We are working on it every day, consistently improving it. For others, I hope you now understand a bit better all the choices and compromises you have to make when you are building such a complex software product. Hopefully, you will be able to apply some of our decision-making solutions to your UX problems.</p><p>Either way, keep sharing your feedback with us!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RFvmznRPrWIB9LPzt47bgQ.png" /></figure><p><em>Originally published at </em><a href="https://www.outsystems.com/blog/posts/making-better-ux-decisions-when-racing-against-time/"><em>https://www.outsystems.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2aa3eae6b283" width="1" height="1" alt=""><hr><p><a href="https://medium.com/outsystems-engineering/ideation-of-an-ide-making-better-ux-decisions-when-racing-against-time-2aa3eae6b283">Ideation of an IDE: Making Better UX Decisions When Racing Against Time</a> was originally published in <a href="https://medium.com/outsystems-engineering">OutSystems Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing Interfaces Like Master Painters]]></title>
            <link>https://medium.com/outsystems-engineering/designing-interfaces-like-master-painters-e261e473e315?source=rss-8129ef1636ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/e261e473e315</guid>
            <dc:creator><![CDATA[Natalia Blaszczyk Alves]]></dc:creator>
            <pubDate>Tue, 03 Nov 2020 11:09:18 GMT</pubDate>
            <atom:updated>2020-11-03T14:31:32.370Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0YpZCUs-or5F-t_mza1ETg.png" /></figure><p>For one of the<a href="https://medium.com/outsystems-engineering/build-a-product-design-team-build-a-product-your-users-love-c6917adb7f47"> Product Design team</a> building excursions, we decided to go to a painting workshop. To set the stage: we’re engineers, not artists. We don’t have much visual talent, really…our drawings speak to our artistic abilities:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*FMHwySe3ci_1EMCJuzm7Ng.png" /><figcaption><em>This is an exercise done during our team’s health check coaching. Not exactly works of art…</em></figcaption></figure><h3><strong>Why a painting workshop?</strong></h3><p>We decided to challenge ourselves and try something out-of-the-box from what we do every day (you ask what we do every day? Quite a lot, <a href="https://medium.com/outsystems-engineering/tagged/product-design">we’ve written several blog posts about it</a>).</p><p>Our two teachers during the workshop were two artists: Dinara and Stephanie Dindarova. One of the first things they explained was: “We don’t teach realism, impressionism or another style. We teach the artistic language.“</p><p>This language is used not only in painting but also in music, theater — it’s universal for all the arts. And as we’ve realized, while we were painting our masterpieces, it can also be applied to designing interfaces.</p><p>Beginners may think the clue to good UI design is to follow the newest trends, may it be “flat design” or “neumorphism”. While it’s important to keep the look and feel up-to-date, the trends pass but what stays the same are the principles — the aforementioned language.</p><p>We want to share what we learned about art and how we see it applied in interface design.</p><h3>Find Your Master</h3><p>Did you know that the famous painter Peter Paul Rubens had so many disciples who actually painted the works he later only signed? Fellow painters called his studio “a factory”. Since forever, art was a discipline where masters passed their knowledge to disciples. The student would have to first observe how the masterworks, then copy their works, then help paint some less important parts until they learned all the craft.</p><p>Painters learn from masters, UX designers should too.</p><p>No one starts as an expert, even though nowadays it may seem like people expect that. Find someone with more experience and ask them to mentor you. If you don’t know anyone like that personally, use networking, go to meetups, take a course, get to know recognized UX experts by reading their publications and follow what they preach. Having a mentor will make you a better professional faster and with less stress.</p><h3>Don’t Start Without the Idea</h3><p>Painters must ask themselves: why do I want to paint that particular topic? What message or story do I want to convey? What do I want my audience to think or feel or see when they look at my art?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*C4GAIAWahVnNveAB" /><figcaption><em>The goal of sacral art in the Middle Ages cathedrals was to teach the Bible to illiterate people. (</em><a href="https://en.wikipedia.org/wiki/The_Last_Judgment_(Bosch_triptych)"><em>image source</em></a><em>)</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c4WoMX7EvwaNLoZZ" /><figcaption><em>Paul Gauguin called this piece “Where Do We Come From? What Are We? Where Are We Going?”, giving us a hint that his work is a symbolic riddle. (</em><a href="https://commons.wikimedia.org/wiki/List_of_paintings_by_Paul_Gauguin#/media/File:Paul_Gauguin_142.jpg"><em>image source</em></a><em>)</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vNvHmv-sFxEcRpxa" /><figcaption><em>In Guernica Picasso depicted the horrors of war to advocate against it. (</em><a href="https://commons.wikimedia.org/wiki/List_of_paintings_by_Paul_Gauguin#/media/File:Paul_Gauguin_142.jpg"><em>image source</em></a><em>)</em></figcaption></figure><p>When starting designing an interface we also have to first ask: what’s the goal? What is this screen, page, or pop-up for? What do we want the users to do? How can we help them achieve their goal? How do we want them to feel?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sw9r5WnPC2q-QspVVaGh_g.png" /><figcaption><em>The goal of this pop-up is to get to know the available screen flows and pick one to add to your application (OutSystems Experience Builder)</em></figcaption></figure><h3>I Have an Idea…Now What?</h3><p>When her students stare at an empty canvas and ask her, “what do I paint first?”</p><p>Dinara responds jokingly: “God started with creating the earth and the sky, and only then rivers and mountains, then plants, animals and so on. You should do the same.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b-h_pjBTfj1y4J2O" /><figcaption><em>The painter starts with the horizon line, puts the color on the sky and the ground. Then gradually a road and single trees appear before the whole forest emerges.</em></figcaption></figure><p>And the same applies to designing interfaces. You don’t start with the position, style or the copy of each UI control, sometimes you don’t even know yet which UI components will be best.</p><p>You start by sketching the main areas of the interface using boxes and just draw some lines where the text will be. Then some small rectangles where you foresee having input fields or buttons. And you don’t even think about any exact images, you just draw a square with a cross in it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*-0HVmcYXmLxuwI8t" /><figcaption><em>Draft from a design session for the Merge feature.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*SyNUxor6Bn3ZQnHq" /><figcaption><em>Healthcare app first prototype.</em></figcaption></figure><h3>Adapt the Style to the Time you Have</h3><p>Realistic painting takes many days to complete. Impressionists painted their works in one afternoon. And you can take the same approach with interface design. At first, you want to quickly test your ideas so you want little time investment in preparing the interface. You can do the first round of user testing using a wireframe prototype, focusing on the most important parts only.</p><p>Iterating wireframes is fast and that’s what you need in this phase of the project when you’re learning a lot. It’s like impressionism. With time you go more into the design details but keep low-fidelity. When you’re confident that your solution is the right one, then you finish it in pixel perfect detail, like a realistic painting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*Eyfxm8BdzWHoS5-C" /><figcaption><em>Quick and dirty wireframe for the Theme Customizer feature.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*86ssBoEio5uWE_VW0ZXJ0g.png" /><figcaption><em>Styles Editor feature: low fidelity paper prototype and high fidelity digital (still static) prototype.</em></figcaption></figure><h3>Paint What You See, Not What You Know</h3><p>It’s easy to tell an amateur painter from a professional — the first paints what they know, the latter what they see.</p><p>A beginner approaches painting with the brain, rational thinking. We have to paint everything with all the details and every detail has the same importance in the overall composition. An observer doesn’t know what to look at, there’s no central thread that tells us the story.</p><p>An experienced painter, on the other hand knows there’s no need to show everything — they highlight what they decide to be most important in the composition. They’ll place in the shadow what doesn’t matter and will lead the eye of the observer across the painting just as they want them to do, without the observer even being aware of it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/520/0*godSTlj8BsFQwrtk" /><figcaption><em>The glitter of the earring immediately draws our eyes, even though we hardly see the girl’s ear. Vermeer used the contrast of light and shadow to lead our eye through his portrait. (</em><a href="https://en.wikipedia.org/wiki/Girl_with_a_Pearl_Earring#/media/File:Meisje_met_de_parel.jpg"><em>image source</em></a><em>)</em></figcaption></figure><p>In the interface, the user doesn’t know the mental model of the system. They don’t even care about it, nor should they even have to know it. Instead, they only need to focus on what they see and interact with. The role of the designer is to hide the underlying complexity, giving the user only the controls that matter to them to complete their task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*4-GMQ-oLulLvvkz6" /><figcaption><em>In Service Studio Aggregates, the SQL query complexity is translated into a fast and easy to understand interface.</em></figcaption></figure><h3>When is Your Masterpiece Finished?</h3><p>Leonardo da Vinci retouched Mona Lisa’s face several times, repainted her hand and changed his mind about the background at least once. He made the changes painting on top of his masterpiece several times and it was only recently revealed thanks to X-ray analysis.</p><p>Retouching or even repainting is a common practice in art, and so it should be in interface design. It’s an iterative process that may never end. Just take a look at how the interface of Service Studio has been changing over the years…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XYLeH8yXSny_oGdU" /><figcaption><em>Service Studio 4.0.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/0*tZvq537pN-VBE0yQ" /><figcaption><em>Service Studio 8.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jJfnY8OWwIbcdMUL" /><figcaption><em>Service Studio 11.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UHR3tF0pZMtoNILB" /><figcaption><em>Service Studio in the near future.</em></figcaption></figure><p>So, here are our masterpieces:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*lFOtcy0vxh-DNV0f" /></figure><p>Our colleagues in the office don’t believe it, but we did these paintings in only two hours!</p><p>In the end, they look great. But we struggled quite a lot throughout the process. We had many doubts, didn’t know how to paint some of the parts, or know which parts we should focus on next. In those moments, our teachers reminded us about the rules of the artistic language.</p><p>As you can see, even engineers can become painters! You don’t need to be ridiculously talented if you know the rules and practice patiently. The same applies to designing interfaces — everyone can learn to do it.</p><p>So, sorry to let you know developers — no more justifying bad interfaces with the lack of visual skills, and no more excuses to avoid working on UI with designers! If you’re still unsure about it — we highly recommend taking up painting as a hobby.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e261e473e315" width="1" height="1" alt=""><hr><p><a href="https://medium.com/outsystems-engineering/designing-interfaces-like-master-painters-e261e473e315">Designing Interfaces Like Master Painters</a> was originally published in <a href="https://medium.com/outsystems-engineering">OutSystems Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do you have the Second Baby Syndrome?]]></title>
            <link>https://natalia-alves.medium.com/do-you-have-the-second-baby-syndrome-17158db20df2?source=rss-8129ef1636ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/17158db20df2</guid>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[parenting]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[funny]]></category>
            <category><![CDATA[second-baby]]></category>
            <dc:creator><![CDATA[Natalia Blaszczyk Alves]]></dc:creator>
            <pubDate>Wed, 09 Oct 2019 09:45:07 GMT</pubDate>
            <atom:updated>2019-11-03T11:26:48.323Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tiRimZnt-c_5kbDJ3phGhQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@tgrossen?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Travis Grossen</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>So you’ve become parents for the second time. Congratulations! Now surely you want to check if you have the Second Baby Syndrome (SBS). Below you’ll find a list of symptoms typical for parents — especially moms — who have the syndrome.</p><ol><li>You’ve forgotten to tell that your new baby was born to (delete — or not — as appropriate): one of your best friends, a family member, your manager.</li><li>You don’t schedule visits for the first two weeks after your new baby was born. After this period, when you receive guests, you don’t get to the hassle of serving them cake and coffee. Or even water. You show them where the tap is.</li><li>You don’t keep track of every feeding, poop or bath anymore. You used to use baby manager apps with Baby #1 but now you uninstalled them because the notification “You haven’t fed your baby in 2 weeks, 4 days and 23 hours” became quite irritating.</li><li>You don’t stress out if your new baby hasn’t pooped for 3 days or has been sleeping for 12 hours without feeding. Actually, you’re happy about it.</li><li>You finish your shower, even if the new baby starts crying.</li><li>You used to have a thermometer in the bathtub to make sure Baby #1 was washed in perfect water temperature. With Baby #2 you just check the water with your finger to ensure he won’t burn or turn into an ice cube.</li><li>Your new baby doesn’t spend 99% of the time in your arms. Even though it’s tempting because she’s so cute, you have other stuff to do. Such as: hugging your older kid who’s jealous, piggybacking him (because who wants to drive two strollers…), or just letting you back get fully deserved rest.</li><li>You don’t take a gazillion of photos of the new baby every day. But that’s not a problem, selecting photos for the Baby Photobook #2 won’t take you 3 months like with the Photobook #1. I mean, if you’ll do it at all. (You should, otherwise, Baby #2 will never forget you this unfairness). Sometimes you even forget to take any photos all day long. Well, unless the older kid does something cool. Because when he does it, it’s for the first time.</li><li>You don’t compare Baby #2 with babies of your friends and family but with your Baby #1. Having a gazillion of photos of Baby #1 helps a lot here.</li><li>For people who keep a journal: you don’t note down every smile, development milestone, or sleep regression. Actually, you stop having time to keep a journal.</li><li>After Baby #1 was born you read all the La Leche League manuals, sleeping survival guides and “Baby genius — how to boost your baby development from the day they are born”. So now you read books for pleasure.</li><li>You start to think that (cross out as appropriate): pacifier opponents, attachment parenting, reusable nappies, and using slings instead of the stroller are perhaps unnecessarily fundamental. Because you’re not ambitious anymore and everything that makes your life easier — without causing permanent damage to your kids — is a blessing you now gladly accept!</li><li>Many things that were a challenge with Baby #1 are a no-brainer with Baby #2. You’re not sure if this is because you’ve become a perfect parent or if you’re still lousy but now you have a rare example of a perfect child.</li></ol><p>If you find yourself having 3 or more of these symptoms— rest assured, you’ve got Second Baby Syndrome! But don’t fret! SBS is totally normal! Actually, if you don’t have it, you may need to go to a psychiatrist… or at least a good massagist!</p><p>Having kids changes you. Having the first one helps you get a healthy perspective on your hitherto life problems. And having the second one helps you get a healthy perspective on having kids.</p><p><em>Thanks to my friends for sharing their experiences and this way contributing to the list of symptoms. Can YOU think of more symptoms? Share them in the comments!</em></p><p><em>You may also like my article about </em><a href="https://medium.com/@astronaat/15-surprising-things-about-parenting-in-portugal-from-polish-perspective-afa57cadefa9"><em>15 surprising things about parenting in Portugal</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17158db20df2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[15 surprising things about parenting in Portugal (from Polish perspective)]]></title>
            <link>https://natalia-alves.medium.com/15-surprising-things-about-parenting-in-portugal-from-polish-perspective-afa57cadefa9?source=rss-8129ef1636ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/afa57cadefa9</guid>
            <category><![CDATA[poland]]></category>
            <category><![CDATA[parenting]]></category>
            <category><![CDATA[expat]]></category>
            <category><![CDATA[portugal]]></category>
            <category><![CDATA[cultural-differences]]></category>
            <dc:creator><![CDATA[Natalia Blaszczyk Alves]]></dc:creator>
            <pubDate>Mon, 19 Aug 2019 20:42:38 GMT</pubDate>
            <atom:updated>2022-01-20T23:07:13.906Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6T2DJmgG46qDTHPB" /></figure><p>I’m Polish and I moved to Portugal 10 years ago. I married a Portuguese and we have two kids. There are several things about parenthood I found surprising in Portugal when compared to what I knew from Poland.</p><p><em>Disclaimer: everything you’ll read below is derived from my personal observations, not elaborated statistical analysis, so you may find it doesn’t match your perspective. I’m just giving you my point of view and you’re welcome to take it with a grain of salt :)</em></p><h3>#1 Attitude towards kids</h3><p>Attitude towards kids is very caring in Portugal.</p><p>Kids go with their parents to restaurants and cafes where they often roam loudly over the esplanade. In Poland, you would get stares of disapproval.</p><p>What surprised me was that men–even the “macho” ones–are very sweet with kids. It’s not uncommon to see a man coo to a baby, carry her around or play with toddlers and kids. It’s not considered as “being too feminine”, even though in most families it’s still the women who do all the house chores.</p><p>Strangers show a lot of care towards kids. For example, if someone sees a child in an unsafe situation with no parents in sight, they don’t hesitate to step in to avoid something bad happening. Another thing: when a little baby is crying people comment “He must be hungry! Isn’t it time to feed him?” (as if there existed no other reasons to cry). That one drives me nuts because it seems like they’re implying that the mom doesn’t know when to feed her baby.</p><h3>#2 Addressing parents</h3><p>In conversations at school, daycare or in the healthcare facilities, parents are not called “Ms” or “Mr”, but “mom” or “dad”. Their names and surnames are omitted. For example, in Poland they would ask me: “Ms Natalia, what do you think about this?“ (“Pani Natalio, o pani o tym myśli?”). In Portugal: “What does mom think about this?” (“O que a mãe acha?”). In Poland talking to people this way is considered rude. Here, however, it’s the polite form.</p><p>Addressing people in third person in Poland means “We are strangers and we need to keep distance”. In Portugal, in some families, children address their parents and other elders this way instead of treating them by “you” to show respect.</p><h3>#3 Touching</h3><p>Portuguese are very social and that also manifests in physical contact. They give two kisses for greeting, even if they’re meeting someone for the first time (that also applies to kids). Even strangers touch pregnant bellies and tousle kids’ hair.</p><h3>#4 Toxoplasmosis phobia</h3><p>During pregnancy, women are super careful with washing the vegetables or fruit because of the risk of getting toxoplasmosis. For some women washing with pure water is not enough, so they add drops of vinegar or bleach as a disinfectant. They don’t eat raw vegetables or fruit, like salads, in restaurants, because they may be not washed well enough. I think this is an exaggeration because the odds of actually encountering contaminated produce are very low.</p><h3>#5 Working while pregnant</h3><p>Both in Portugal and Poland women tend to go on parental or sick leave in their last weeks or months of pregnancy. Unfortunately, the sick leaves are often abused. I was working until the last day before the delivery in both my pregnancies and this was shocking for most people.</p><h3>#6 Pain relief during the delivery</h3><p>I have great memories from both deliveries but when I talk to Polish women the vast majority of them had traumatic experiences. In Poland, women are discouraged and even impeded to take pain relief drugs, especially the epidural, during the delivery. In comparison, on my birthing course in a Portuguese public hospital, we had a meeting with the anesthesiologist who told us that the objective is a no-pain delivery. Also, during the delivery, I was treated with the utmost respect. Imagine how that’s in Poland, where there’s an <a href="https://www.rodzicpoludzku.pl/About-us/Who-we-are.html">NGO and a social campaign called “Childbirth with Dignity</a>”…</p><h3>#7 Parental leave and social security</h3><p>Due to low birth rates, governments in both countries provide support for families with children.</p><p>In Poland, the paid parental leave is as long as 1 year. Afterward one of the parents can take another 2 years of unpaid leave. Every family, no matter their income, receives 500 zloty per month (equal to about ⅓ of the net minimum salary) per child. Poorer families also receive a one-time bonus when a baby is born. Healthcare in Poland is free for everyone.</p><p>In Portugal the first 6 weeks after birth are obligatory for mothers and during this period the fathers have obligatory 2 weeks plus non-obligatory 3 weeks. As of 2019, you can choose the following modalities of the parental leave:</p><ul><li>4 months for 1 parent paid 100% of their salary or 5 months paid 80%</li><li>To one of the above options you can add 1 month for the other parent</li><li>After that you can opt for up to 3 months for either one of the parents, paid 25% (so, if both take it, it’s 6 more months of care for the baby)</li></ul><p>So the total time of parental leave in Portugal is also 1 year, but only if 4 months are taken by the father and you get less money the longer you stay.</p><p>In Portugal you pay symbolic fees in public healthcare, however pregnant and postpartum women as well as children are treated for free. There’s also this small yet significant law of giving priority in queues to pregnant women and people accompanied by kids less than 2 years old.</p><h3>#8 Breastfeeding</h3><p>Breastfeeding is highly encouraged and there’s no problem in doing it in public. However, there’s a lot of misconceptions around breastfeeding and little support in challenging situations. I had troubles after my son was born and I received a lot of wrong advice about how to breastfeed him at the hospital.</p><h3>#9 Bedtime</h3><p>Even small kids go to bed the earliest around 9 PM because Portuguese usually have dinner around 8 PM or later.</p><p>In Poland, bedtime is around 7–8 PM. People there start work at 8 AM and breakfast is a substantial meal so usually they get up around 6.30 AM.</p><p>In Portugal many people start work at 9–10 AM and they don’t spend much time over breakfast which is light and… well, fast :) so they can get up later. I think that’s why the bedtime is later.</p><h3>#10 Having help at home</h3><p>Majority of women in Portugal work. It’s common (not only among families with kids but also couples and singles) to hire a cleaning lady to come once or a few times a week. Some families have a housekeeper who cooks, cleans and takes care of kids while both parents are at work.</p><p>In Poland, people are rather wary of letting a stranger in their house to help with such private tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VmB-glcgQuXZp0Dl" /></figure><h3>#11 Daycare</h3><p>Many Polish people believe that it’s the best for the baby to stay at home with mom for the first 3 years. Portuguese want their kids to socialize in the daycare from the very beginning. In Portugal, the shortest parental leave is 4 months so daycare accepts babies as young as that. From my observations, most babies go to daycare at around 1 year of age.</p><p>In most daycares it’s obligatory to wear a uniform, usually it’s an apron. Each kindergarten has its own design. In Poland, I guess this would be considered limiting one&#39;s individualism :)</p><p>The vast majority of daycares have outdoor playgrounds and because the weather in Portugal is so warm, kids spend whole days outside. In summer the beach trips are organized.</p><p>The craziness of “extra-curricular” activities starts already at daycare. You can sign your baby/toddler up for yoga, judo, karate, swimming, dance, music or English, all at an extra cost of course. I guess just leaving them play is overrated! ;)</p><p>Daycares in Lisbon are open long hours, because Portuguese work long hours. To the typical 8-hour workday add a 1-hour break for lunch and another extra 30–60 minutes because leaving work punctually is not in the culture. And then take into account the traffic which makes the commute be another 1–2 hours. Unfortunately, it’s not uncommon to have kids stay at kindergarten from 7.30 AM till 7 PM. In Poland you’d be considered a bad parent!</p><p>Another difference is that in Poland children arrive at daycare to have breakfast around 8 AM. In Portugal the breakfast is not served at daycare.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CggK6maa1SVW7xOZ" /></figure><h3>#12 Helicoptering parents</h3><p>In my opinion, both Portuguese and Polish are overprotective towards kids and that doesn’t foster independence. My son had to be transferred to an older group at daycare because in his age group the parents forbade to take the kids to the outdoor playground “because they can get hurt”. On public playgrounds sometimes there are more parents than kids, the adults helping them climb the equipment and protecting the kids not to fall. We’ve seen kids outdoors and indoors in helmets! My two-year-old on a run bike makes people awe on the street. At our kindergarten, the teachers are told off if a child has a scratch or was punched by another kid.</p><p>In my generation (people born in the 80s.) walking alone to school was perfectly normal. Today kids are driven everywhere by car by their taxi driver parents or grandparents. That actually causes a lot of confusion and car accidents on the street near schools! Sometimes people drive literally a couple of hundred meters instead of walking. On my son’s daycare group photo we noticed that he was the only child whose shoes soles were dirty from walking on the street — all the other kids are driven by car and carried everywhere.</p><h3>#13 Changing shoes</h3><p>In Poland people change their shoes indoors to slippers or just go in their socks. In Portugal they don’t bother — and in winter it would actually mean frozen feet! This results in not exactly clean floors which was uncomfortable for me when my son was crawling on all fours. Going barefoot or in socks is frowned upon. Portuguese believe that good shoes for a toddler are rigid ones because they “give better support to the feet”. As consequence kids don’t walk barefoot or in soft shoes which would promote the formation of feet muscles.</p><h3>#14 Sidewalks</h3><p>Portuguese sidewalks were definitely not designed with strollers in mind. Traditionally the sidewalks are paved with small white square bricks which are called calçada. It’s used only in Portugal and Portuguese ex-colonial countries. It looks enchanting and enlightens the street, but it’s bumpy and dangerously slippery. The sidewalks are usually narrow, have cars parked on top of them or street lamps and other posts, as well as electricity boxes right in the middle which leaves no space for a stroller to pass — you have to walk on the road!</p><h3>#15 Language</h3><p>I knew Polish is very difficult to learn but speaking it to my kids made me realize it even more. Portuguese words are shorter, simpler, easier to pronounce and there’s less of them. For example when my kid says <em>bola</em> in Portuguese, in Polish he may be referring to <em>piłka</em> (a ball), <em>bila</em> (a billiard-ball), <em>kłębek</em> (a ball of wool), <em>bąbel</em> (bubble), <em>bańka</em> (soap bubble)<em> </em>or<em> kulka</em> (a small hard round object).</p><p>Most baby’s first words are so much easier in Portuguese, for example:</p><ol><li><em>Olá / </em>hi / <em>cześć</em></li><li><em>Avó</em>, <em>avô</em> <em>/</em> grandma, grandpa <em>/</em> <em>babcia</em>, <em>dziadek</em></li><li><em>Tia</em>, <em>tio</em> <em>/</em> aunt, uncle <em>/</em> <em>ciocia</em>, <em>wujek</em></li><li><em>Mano</em>, <em>mana</em> <em>/</em> bro, sis<em> / brat</em>, <em>siostra</em></li><li><em>Mais</em> <em>/</em> more <em>/</em> <em>więcej</em> or <em>jeszcze,</em> depending on the context</li><li><em>Bebé</em> <em>/</em> baby <em>/</em> <em>dzidzia</em></li><li><em>Chora</em> <em>/</em> is crying <em>/</em> <em>płacze</em></li><li><em>Cama</em> <em>/</em> bed <em>/</em> <em>łóżko</em></li><li><em>Cara</em> <em>/</em> face <em>/</em> <em>buzia</em></li><li><em>Para</em> <em>/</em> stop <em>/</em> <em>stój</em> (stand still) or <em>przestań</em> (stop what you’re doing)</li><li><em>Pato</em> <em>/</em> duck <em>/</em> <em>kaczka</em></li><li><em>Rato</em> <em>/</em> mouse <em>/</em> <em>mysz</em></li><li><em>Vaca</em> <em>/</em> cow <em>/</em> <em>krowa</em></li></ol><p>Just look at the Polish words to see how differentiated, longer and harder to pronounce they are. And then comes the grammar. Polish verbs conjugate (depending not only on the person and tense but also on gender), nouns, pronouns, and adjectives are declined in seven cases. The orthography is dreaded even by Poles. There are sounds which have the same pronunciation despite being written with different letters. Half of the times you know how to write a word because there are rules but the other half are exceptions which you must learn by heart.</p><p>I thought that raising kids as bilingual will come in naturally and effortlessly — that it’d be enough just to talk to them in Polish all the time. I was wrong and I guess this was my biggest surprise of parenting abroad.</p><p>That’s it! These are the things I found surprising about parenting in Portugal. How about you, are you an expat who got surprised after becoming a parent in the country of your residence? Share your stories!</p><p><em>You may also like my satiric article about </em><a href="https://medium.com/@astronaat/do-you-have-the-second-baby-syndrome-17158db20df2"><em>The Second Baby Syndrome</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afa57cadefa9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Emotional Design. Adding a little cherry on top of your product’s UX.]]></title>
            <link>https://medium.com/outsystems-experts/emotional-design-adding-a-little-cherry-on-top-of-your-products-ux-bf8816c3b40d?source=rss-8129ef1636ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf8816c3b40d</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[enterprise-software]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[emotional-design]]></category>
            <dc:creator><![CDATA[Natalia Blaszczyk Alves]]></dc:creator>
            <pubDate>Sun, 10 Jul 2016 23:53:52 GMT</pubDate>
            <atom:updated>2020-04-21T09:30:34.297Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WqUdVNVNdlsl7kM1-p94gQ.jpeg" /></figure><p>Last year I took part in a workshop about emotional intelligence with a group of software engineers. Engineers believe in systematic thinking, algorithms and analytics. They don’t believe in emotions. When the workshop’s instructor asked if psychology was a science, they giggled. That’s a very common reaction.</p><p>One of my favourite <a href="https://www.ted.com/talks/guy_winch_the_case_for_emotional_hygiene?language=en">TED talks is one by Dr. Guy Winch</a>. He’s spent 9 years earning his doctorate. When he meets new people, the conversation usually goes something like this:</p><p>“What do you do in life?”<br>“I’m a doctor.”<br>“What specialty?”<br>“I’m a psychologist.”<br>“Oh… so, not a real doctor.”</p><p>Just to set expectations right, he put it on his business card:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/947/1*A1EgUV31PFoyWz3bqHvRvA.png" /><figcaption>Image captured from Guy Winch TED talk</figcaption></figure><p>In his talk, Winch points out that society tends to favor the body over the mind. We often hear that we should eat healthy, avoid smoking, pass on good habits to our kids and do many other things that are good for one’s body. But few people apply the same general habits to psychological health.</p><p>We live in an age that favors reason. Emotions carry a negative connotation. Being <em>emotional</em> is perceived as being weak and unstable. We like to think of ourselves as perfectly reasonable creatures, but emotions do influence our choices a lot. And that’s not a bad thing!</p><p>Emotion and reason complement each other; those are the foundations on which our brains are established. We cannot separate thinking and feeling. We cannot get rid of emotions; we should not ignore them. They are useful for enabling the cognitive part of our brains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*9ivsBeTrnsAj1lMmGcNA2g.png" /></figure><p><a href="https://www.technologyreview.com/s/528151/the-importance-of-feelings/">António Damásio studied people</a> whose parts of the brain were damaged, particularly those responsible for the emotional system. He discovered that they lost their ability to make plans or make decisions.</p><p>First impressions are an emotions-based phenomenon with huge, long-term impact on perception. It is due to emotion that we are able to remember. We slot life events triggered by strong emotions into our long-term memory and remember them with great detail. Negative ones like our first fender bender or being victims of pickpocketing and positives ones, like our first crush or our first kiss.</p><p>The strong emotions associated with these events make them important for us. All of this is encoded in our genes as a survival mechanism. It is thanks to emotion that we learn what’s good for us, what we need to seek for and what is bad for us, what we need to avoid.</p><h3><strong>What is emotional design?</strong></h3><p>Emotional design is not a design discipline, like graphic design or car design. It’s also not a step in the UX design process, like interaction or visual design. Emotional design is a layer, a perspective. It should be sprinkled on top of the whole experience. It’s the little cherry on top, the extra mile that makes people love a product.</p><p>There’s no recipe for success, but there are some guidelines for adding an emotional aspect to your designs.</p><h3><strong>Empathy for Users</strong></h3><p>Product design shouldn&#39;t come out of the void or grow inside closed office doors. Get a grasp of your product&#39;s users, learn who they are, understand their needs, habits and routines. Address their feelings.</p><p>It might happen that you&#39;re also a user of the product you are designing and that might give you extra insight, an advantage. But be careful with personal bias. Consider that other users may face other challenges, have different work routines and that their company culture might differ from yours — their boss might be trickier to deal with than yours, for instance. (Mine’s perfect to deal with, by the way.)</p><p>When you’re testing for usability, don’t focus just on usability issues. Observe the users’ emotional responses when dealing with the product. This is the process that what will help you find the moments when you can <em>wow</em> them.</p><p>Some time ago, we had an AMA (Ask Me Anything) session with some of our most special community members here at <a href="https://www.outsystems.com/?utm_source=medium&amp;utm_medium=middle_of_article&amp;utm_term=OutSystems&amp;utm_content=Emotional%20Design.%20Adding%20a%20little%20cherry%20on%20top%20of%20your%20product%E2%80%99s%20UX.&amp;utm_campaign=blog">OutSystems</a>. Our developers were eager to know what our users wanted to change in our product. When they mentioned stability, we asked one of the guys:</p><p>“Do you submit bug reports? You know, on the little pop-up that comes up whenever there’s a crash?”<br>“No, I don’t!”<br>“Why not? Come on, man! You should do it. Sometimes it’s the only way we get to know what the problem is and get to fixing it!”<br>“But I don’t have internet access… I’m inside an internal enterprise network. And I also had no idea sending this feedback was so crucial for you.”</p><p>(It is.)</p><h3><strong>Mood influences people’s cognitive skills</strong></h3><p><a href="http://www.factorhappiness.at/downloads/quellen/S11_Isen.pdf">Psychologist Alice Isen discovered that people are better at finding solutions when they are happy</a>. During her experiment she asked people to solve difficult problems, which required creativity and out-of-the-box thinking. One group of participants started immediately trying to solve the problems, while the other was given a bag of candy and watched a bit of a comedy film before undertaking their tasks.</p><p>It turns out that the second group ended up being better problem solvers, because they approached it feeling better and more relaxed. When people are anxious and stressed, they narrow their thought process and can’t come up with many solutions.</p><p>If we think about people using technology in these two types of circumstances, we can imagine happy users being more tolerant of crashes, for instance, and more willing to try harder when using software to achieve their goals.</p><h3><strong>Functionality is not enough</strong></h3><p>Some may say that functionality trumps usability or even the pleasure of use. Some think that if the functionality is there, if the product is robust and powerful but not necessarily pretty or easy to use, people will still end up using it.</p><p>That may not be entirely true. Attractive things work better, as was <a href="http://www.jnd.org/dn.mss/CH01.pdf">proven in a study conducted by two Japanese researchers </a>— Masaaki Kurosu and Kaori Kashimura. They did usability tests with two ATMs. The functionality was the same; the number of buttons and steps people had to perform were the same.</p><p>But while one ATM was pretty to look at, the other one was ugly. It turned out that people preferred using the pretty ATM. This experiment was later repeated in Israel by Noam Tractinsky who thought the results were biased by cultural aesthetic preferences. His results were exactly the same.</p><p>Think about Apple. Are Macs functionally better than PCs? No, and they even are more expensive. Yet so many people prefer them. Apple gives a lot of attention to emotional design and they generate huge revenue.</p><blockquote>Happy users + pretty product = better experience</blockquote><h3><strong>3 levels of processing</strong></h3><p><a href="http://www.jnd.org/dn.mss/CH01.pdf">According to Don Norman, good design addresses 3 levels</a> of how people perceive and process the reality around them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*ZqypOU5GpzKvJET0U7DN-A.png" /><figcaption>Photo from Unsplash</figcaption></figure><p>The visceral level is subconscious, instantaneous and based on sensory information. It’s related to what we see, hear, smell or touch, everything that forms the basis of our first impressions. If something is sensuously pleasant, we start preferring it.</p><p>We are biologically prewired to like vivid colors, symmetrical faces or harmonious music, and to dislike bitter tastes, asymmetry or loud sounds. That’s why, for example, someone may choose to buy pricier bottled water due to its pretty packaging. Later they may even use it as a vase for flowers. They take the brand home.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*AJSjgMj6_4eIdqKLtfBzxg.png" /><figcaption>Photo from Unsplash</figcaption></figure><p>The behavioral level is also subconscious and has to do with our interaction with an object. Is it easy and effective to use; does it do what we expect? If it does, this will give us a feeling of control and, therefore, one of pleasure and satisfaction. The earlier visceral reaction will just reinforce the behavioral perception.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*xAeb3HtHQ6_LV1HsD8RJBg.png" /><figcaption>Photo from Unsplash</figcaption></figure><p>The reflective level is the only conscious one. When we start thinking about our experience with an object, our rationalization kicks in. We evaluate its functionality, value for our money and the advantages it brought to our lives. When we stick to a certain product for longer, it ends up acquiring a place in our lives. We get stories to tell our friends. We develop emotional bonds with this object.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*8sKsadDnngqNDZRxHIiK_A.png" /></figure><p>Here’s a personal example of how design can affect emotions. I don’t like being unpunctual. I start stressing out when I realize I’m about to arrive late. Stressing out is bad for my health, and since I tend to drive more recklessly when I’m in a hurry, it also gets dangerous for other people on the road.</p><p>When I started using GPS apps I noticed that a little piece of the user interface, the estimated arrival time, made a big difference! Knowing what time I will arrive makes me that much calmer… even if I’m going to be late anyway!</p><p><a href="http://mailchimp.com/">MailChimp</a> does an awesome job with emotional design. Creating email campaigns is their platform’s main use case. You may not realize it, but this actually takes a lot of work. MailChimp recognizes their users’ effort and praises them by presenting the final action of sending the campaign as the moment of glory!</p><p>Fred is MailChimp’s mascot, and the way MailChimp found to celebrate some of the users’ success was for Fred to raise his hand for as many high fives as users want. But his hand will get redder each time the users keep clicking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*Yx7VweG75wOF555aR6a6HA.png" /><figcaption>Design by MailChimp</figcaption></figure><p><a href="https://creativemornings.com/talks/aarron-walter">This went viral</a>. MailChimp users started sending them emails and posting pictures and videos on Facebook and Twitter of them high-fiving Fred. Someone even started producing these huge Fred gloves, with which people started having fun. All this generated huge hype. Just imagine the impact it had on MailChimp’s brand awareness and conversion rates!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/1*b9wQRvTjyTJqYuYt0bMwHw.png" /><figcaption>Images captured from Aarron Walter’s presentation (<a href="https://creativemornings.com/talks/aarron-walter">https://creativemornings.com/talks/aarron-walter</a>)</figcaption></figure><p><a href="http://v/">The Small Book of The Few Big Rules</a> is the culture book we have at <a href="https://www.outsystems.com/?utm_source=medium&amp;utm_medium=middle_of_article&amp;utm_term=OutSystems&amp;utm_content=Emotional%20Design.%20Adding%20a%20little%20cherry%20on%20top%20of%20your%20product%E2%80%99s%20UX.&amp;utm_campaign=blog">OutSystems</a>. It’s filled with illustrations and small comic strips featuring several characters. Our People Ops team recently had the brilliant idea of printing out real size characters and placing them all over our office to use them as a communication platform with employees.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Zwh0tST1HRreS0pZzhrZ0w.png" /></figure><p>This turned out to be much more effective than sticking A4 sheets of paper with announcements on the walls. Moreover, people started interacting with the characters. They write funny responses in the speech balloons and take the characters to office parties!</p><h3>Considering emotions in enterprise software products</h3><p><a href="https://www.outsystems.com/platform/#deploy-in-the-cloud?utm_source=medium&amp;utm_medium=middle_of_article&amp;utm_term=The%20intelligent%20application%20deployment%20process%20is%20one%20of%20OutSystems%20Platform%E2%80%99s%20most%20touted%20features&amp;utm_content=Emotional%20Design.%20Adding%20a%20little%20cherry%20on%20top%20of%20your%20product%E2%80%99s%20UX.&amp;utm_campaign=blog">The intelligent application deployment process is one of OutSystems Platform’s most touted features</a>. When we developed this system, we decided to enrich the user experience with an animation that literally illustrates the status messages received during the deployment process. When we created the first versions of the animation, some people were worried that they would not be appropriate for an enterprise-grade platform.</p><p>But the reception was great from our clients, as they really enjoyed watching it! Images and movement are more interesting than static and “dry” text status messages. Thanks to the animation, users get a better grasp of what is happening under the hood and they feel more in control of this complex process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9YX7NsdWNMW12hUmRz-Jmw.gif" /><figcaption>Software deployment process</figcaption></figure><p>The last example I want share is our latest design for the <a href="https://www.outsystems.com/platform?utm_source=medium&amp;utm_medium=middle_of_article&amp;utm_term=OutSystems%20IDE&amp;utm_content=Emotional%20Design.%20Adding%20a%20little%20cherry%20on%20top%20of%20your%20product%E2%80%99s%20UX.&amp;utm_campaign=blog">OutSystems IDE</a> installer and splash screen. The installation screen is part of the initial experience users have with the product. It’s an opportunity to make a good first impression. The splash screen is something they see every day when they launch the IDE to start their work. Therefore, it’s a way to create an emotional bond.</p><p>So, we made a design proposal and wanted to test if it would have a positive emotional impact. We made a simple prototype in InVision and showed it to several people in our organization. And we filmed their faces without them knowing! Check out the result in this short video:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FcVrM4JShk1c%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DcVrM4JShk1c&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FcVrM4JShk1c%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/458b24dd838890ebeeee8d0761693291/href">https://medium.com/media/458b24dd838890ebeeee8d0761693291/href</a></iframe><p>As you see, enterprise-grade software solutions don’t need to be ugly, serious, or boring. We can try to find some room for evoking positive emotions. Do you have ideas for putting a cherry on top of your product’s experience? Don’t be afraid to experiment! It’s cheap, fun and you’ll learn a lot in the process.</p><p>Small things can make a big difference and add value. When working on a product’s UX we shouldn’t just be removing the “OH, NOs.” We should be seeking for ways to add the “WOWs.”</p><p><strong>Natalia Błaszczyk</strong> | UX Designer at <a href="https://www.outsystems.com/?utm_source=medium&amp;utm_medium=author_blurb&amp;utm_term=OutSystems&amp;utm_content=Emotional%20Design.%20Adding%20a%20little%20cherry%20on%20top%20of%20your%20product%E2%80%99s%20UX.&amp;utm_campaign=blog">OutSystems</a></p><p>The ideas shared in this post resulted partially from the <a href="https://www.outsystems.com/financial-incentive-program/">research project RADicalize</a>, which was supported by the EU and PT2020.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf8816c3b40d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/outsystems-experts/emotional-design-adding-a-little-cherry-on-top-of-your-products-ux-bf8816c3b40d">Emotional Design. Adding a little cherry on top of your product’s UX.</a> was originally published in <a href="https://medium.com/outsystems-experts">OutSystems Experts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Logos: Lisbon and Łódź, two stories behind the cities’ visual identities]]></title>
            <link>https://natalia-alves.medium.com/logos-lisbon-and-%C5%82%C3%B3d%C5%BA-two-stories-behind-the-cities-visual-identities-f5bb22e9c105?source=rss-8129ef1636ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5bb22e9c105</guid>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[logo]]></category>
            <dc:creator><![CDATA[Natalia Blaszczyk Alves]]></dc:creator>
            <pubDate>Tue, 07 Apr 2015 23:20:44 GMT</pubDate>
            <atom:updated>2015-12-27T10:14:34.156Z</atom:updated>
            <content:encoded><![CDATA[<p>Having seen <a href="http://inkbotdesign.com/top-10-city-logos/">Iknbot Design’s blog post about Top 10 City Logos</a> I thought there are many interesting visual identity systems among cities and towns of the world — and many of them don’t get a proper recognition! So, trying to change this state of affairs, let me introduce you to two city’s logos I find interesting and inspiring. Coincidentally both cities are places I have lived in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*aMUTuTZRwMPwlvXj.jpg" /></figure><p><em>[image source: </em><a href="http://www.cm-lisboa.pt/typo3temp/pics/442c161b05.jpg"><em>City Hall of Lisboa</em></a><em>]</em></p><p>The Logo of Lisbon is a silhouette of a ship with two crows sitting on its sides. This symbol of the city, conveyed in its coat of arms, originates in an old legend of Saint Vincent. I appreciate a lot how this symbol is interlaced in the urban tissue. It decorates the street lamps in the old town — a detail probably not noticed by every <em>lisboeta</em> (as a citizen of Lisbon is called in Portuguese), it also appears in <em>calçada </em>(Portuguese pavement) patterns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*ice862vJKMFtht60.jpg" /></figure><p><em>[image source: </em><a href="http://www.google.pt/url?sa=i&amp;rct=j&amp;q=&amp;esrc=s&amp;source=images&amp;cd=&amp;cad=rja&amp;uact=8&amp;ved=0CAcQjRw&amp;url=http%3A%2F%2Fpressroom.visitportugal.com%2F2014%2F03%2F5-great-small-museums-off-the-beaten-path-in-lisbon%2F&amp;ei=tA8jVdaJKovwUqGyguAG&amp;bvm=bv.89947451,d.d24&amp;psig=AFQjCNHO2k7p-ujZv7D9U2g0dlrMrV73Yg&amp;ust=1428447480959996"><em>Visit Portugal</em></a><em>]</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*YD-x9sIJ9Bn69hoF.jpg" /></figure><p><em>[image source: </em><a href="http://www.pavconhecimento.pt/roteiro2_biodiversidade/en/04_corvos_lx.html"><em>Visit Portugal</em></a><em>]</em></p><p>What is the meaning of Lisbon’s logo?</p><p>The ship is a symbol of the Age of Discoveries, a period in Portuguese history that brings most pride to its citizens. Portuguese were the first Europeans to sail down the African continent, exploring and going around it to find alternative sea route to India (as the land route became too hazardous during Arab expansion in the Near East and the crusades). Bartolomeu Dias was the first to reach Indian Ocean, Vasco da Gama — to land in India, Pedro Alvares Cabral discovered Brazil and Ferdinand Magellan was the first to circumnavigate the Earth. What allowed Portuguese to advance in their explorations was a new type of ship — the caravel.<br> Now when I look again at the logo I can see not only a ship but in the same time an anchor — yet another nautical reference to the history of the country.</p><p>The crows were always baffling me, because you don’t see them often in Lisbon, yet they are one of the city’s most famous symbols (the other famous symbol being a sardine). In the legend of Saint Vincent these birds were flying over the place where the body of the saint was hidden, pointing the way for the Portuguese king Afonso Henriques to find the relics and bring them to the capital. The crows followed his ship and that’s how they became the city’s symbol. <a href="http://www.cm-lisboa.pt/en/city-council/city-council/coat-of-arms">You can read the full legend here.</a></p><p>I like Lisbon’s logo because of it’s simplicity — such an elegant representation of the tradition in a modern form (sans-serif FF DIN font face, simplified shapes and …rounded corners!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*Dtt5F_xWNr9OYOji.gif" /></figure><p><em>[image source: </em><a href="http://www.kreatywna.lodz.pl/page/19,nowe-logo.html"><em>Łódź Kreuje</em></a><em>]</em></p><p>Logo of Łódź (the third largest Polish city) was inspired by the modernist De Stijl and Constructivism art movements and works of such artists as Katarzyna Kobro and Władysław Strzemiński who lived and created in Łódź. It’s not the city’s official logo (it’s the identity of a project aimed at developing creative industry in Łódź) although some people would like it to be — and it actually stirs up an emotional public discussion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*_mxOpQc9ZS35PY9Z.png" /></figure><p><em>[Different language versions of the logo. Image source: </em><a href="http://www.kreatywna.lodz.pl/page/19,nowe-logo.html"><em>Łódź Kreuje</em></a><em>]</em></p><p>Many people don’t like it, they find it too weird and illegible (or <a href="https://adamjarecki.wordpress.com/2011/12/07/nowe-logo-lodzi/">resembling two pregnant women</a>). However, usually they don’t know the story behind this logo. The lettering was inspired by the alphabet designed by Władysław Strzemiński, one of the most important Polish avant-garde artists, who happened to be one of the founders of Łódź’s Academy of Arts. The shape of the logo also remains of sculptures of Katarzyna Kobro, Strzeminski’s wife and professor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*0NNYf9bqxI5nAcib.png" /></figure><p><em>[Alphabet designed by Władysław Strzemiński in 1932. Image source: </em><a href="http://www.kreatywna.lodz.pl/page/19,nowe-logo.html"><em>Łódź Kreuje</em></a><em>]</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*8WXKb-SzKDsF9hdI.jpg" /></figure><p><em>[Katarzyna Kobro’s ‘Spacial Composition 4’, 1929. Image source: </em><a href="http://www.presentandcorrect.com/blog/wp-content/uploads/2012/05/000329.jpg"><em>Pinterest</em></a><em>]</em></p><p>Both were pioneers of the constructivism avant-garde, influential artists of the pre- and postwar era. Making a reference to their creative output in the logo of a the city’s creative industry makes sense. The logo conveys the ideas of avant-garde: innovation, out-of-the-box thinking, challenging the status quo. In the same time it refers to Constructivism, “the art movement was in favour of art as a practice for social purposes” (quote after Wikipedia). Why not pass these ideas into the city’s identity?</p><p>Even though not official, it already has some influence — Łódź’s Airport logo looks like a clear derivative from it. I like the idea and I hope other important city entities will follow in creating a consistent and scalable visual identity system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*pAiCLQLwcEoSbF79.jpg" /></figure><p><em>[Image source: </em><a href="http://upload.wikimedia.org/wikipedia/en/b/b1/Logo_lodz_airport.jpg"><em>Wikipedia</em></a><em>]</em></p><p>Do you have your favourite city identities? Which ones? Why do you like them? Share your thoughts!</p><p><em>Originally published at .</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5bb22e9c105" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>