<?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 Alberto Andreetto on Medium]]></title>
        <description><![CDATA[Stories by Alberto Andreetto on Medium]]></description>
        <link>https://medium.com/@aandreetto?source=rss-ff4b9d4d6203------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cTcyD1nO9E3cTIorynLFVw.jpeg</url>
            <title>Stories by Alberto Andreetto on Medium</title>
            <link>https://medium.com/@aandreetto?source=rss-ff4b9d4d6203------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:05:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aandreetto/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[Designing my way out of a sleeping problem]]></title>
            <link>https://medium.com/@aandreetto/designing-my-way-out-of-a-sleeping-problem-1aa8357070dd?source=rss-ff4b9d4d6203------2</link>
            <guid isPermaLink="false">https://medium.com/p/1aa8357070dd</guid>
            <category><![CDATA[dashboard]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ai-vibe-coding]]></category>
            <dc:creator><![CDATA[Alberto Andreetto]]></dc:creator>
            <pubDate>Tue, 25 Aug 2026 16:48:04 GMT</pubDate>
            <atom:updated>2026-08-26T10:27:44.191Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eMKoYaR5yNcLyReax8bYXQ.png" /></figure><p>I’m a designer. I spend most of my days trying to understand complex problems, identify patterns, and design systems that make things easier to navigate.</p><p>In 2025, I decided to apply the same approach to something much more personal: my sleep.</p><p>I had never been the kind of person who slept until midday. I usually woke up early, and I had never considered falling asleep a serious problem. But during 2025, something changed.</p><p>I started having nights when I could not fall asleep. Then those nights became more frequent. The more it happened, the more difficult it became to approach bedtime without thinking about sleep.</p><p>The problem was no longer only not sleeping. It was also worrying about not sleeping.</p><h4>Starting a treatment</h4><p>In July 2025, I started seeing a psychiatrist. He prescribed Trittico, the Italian brand name for trazodone hydrochloride, with different doses over time: 50 mg, 75 mg, and 150 mg per night.</p><p>Trazodone is a psychopharmacological medication primarily approved as an antidepressant. Because it can have sedating effects, it is also prescribed off-label at lower doses to support sleep in some cases. It is not something to self-prescribe or adjust independently; in my case, the dosage was changed according to my psychiatrist’s instructions.</p><p>I’m not writing this as medical advice, and I’m not trying to draw conclusions about the treatment itself. The medication was one part of a broader period in which I was trying to understand what was happening to me.</p><p>I wanted to observe my sleep rather than rely only on how I remembered it.</p><h4>The simplest possible system</h4><p>I wanted to track my sleeps but I cannot wear a smartwatch while I sleep. I find it uncomfortable, and I didn’t want to introduce another device into the night.</p><p>So I went back to a very simple solution: a Google Form.</p><p>Every morning, I filled it in manually. The form asked:</p><ul><li>What time did I go to bed?</li><li>What time did I fall asleep?</li><li>What time did I wake up?</li><li>Did I have any awakenings?</li><li>How many dreams did I remember?</li><li>Did I have nightmares?</li><li>How would I rate the night from 0 to 10?</li><li>How much Trittico did I take?</li><li>Did I train that day?</li><li>Did I sleep alone?</li><li>Did I sleep at my house?</li></ul><p>Every answer went into a Google Sheet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jrA1UxaHswnAgWl_G0I68Q.png" /></figure><p>The whole process took around one minute.</p><p>One minute is not much. It was short enough to make the process sustainable, but long enough to create a surprisingly detailed record of my nights.</p><p>All the questions were mandatory. Every morning I had to complete the form, even when the previous night had been particularly bad.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4zPtIFE9G43J7jJUGqZoww.png" /></figure><p>I did this for exactly one year, from July 2025 to July 2026: 364 nights of sleep, or at least 364 attempts to describe it.</p><h4>The first analysis</h4><p>At the beginning, the Google Sheet was enough.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0jXscXRo1NPxOUdTOi5dMQ.png" /></figure><p>I could sort the rows, compare nights, calculate averages, and look for simple patterns. It gave me something that memory could not: a continuous record.</p><p>Memory is very good at preserving the most intense moments. It remembers the night when you stared at the ceiling for hours. It remembers waking up repeatedly. It remembers the morning after a terrible night.</p><p>It is much less good at remembering the ordinary nights.</p><p>Once the data was collected, I could see all of them together: the difficult nights, the normal nights, and the nights I had almost completely forgotten.</p><p>The spreadsheet helped me start analysing the data, but it was not a particularly good way to explore it. There were too many rows and too many relationships between the variables.</p><p>I wanted to see the system.</p><h4>Designing Sleep</h4><p>This is where my background as a designer became useful.</p><p>Instead of treating the spreadsheet as the final product, I started thinking about how I would design an interface for someone who needed to understand a year of sleep data. A data layer to structure in order to build something more user friendly that reads that layer.</p><p>The project became called <strong>Sleep</strong>.</p><p>The first step was not coding. I created a `design.md` file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u9QqQoEcZZYKsGJr4rbJtw.png" /></figure><pre>did# Dreams frontend design guide<br><br>## Purpose<br><br>This document defines the visual and interaction direction for the `Dreams` frontend: a rational, technical dashboard for sleep data with precise boundaries, square geometry, and restrained color use. The interface should feel engineered rather than decorative, with a layout language closer to specification sheets, technical systems, and modern Swiss-inspired digital tools than to a soft wellness app.<br><br>## Design intent<br><br>The product should communicate clarity, precision, and calm control.<br><br>- Rational, technical, and disciplined.<br>- White background with black content in light mode.<br>- Dark mode should preserve the same structure and contrast logic.<br>- Thin lines define structure and hierarchy.<br>- 90 degree corners everywhere.<br>- No rounded cards, pills, bubbles, or soft shadows.<br>- Minimal but not empty.<br>- Data should always feel readable first, decorative second.<br><br>The overall feeling should sit between a technical manual, a specification sheet, and a precise data workstation.<br><br>## Typography<br><br>### Font system<br><br>Use IBM Plex Mono as the main interface font for titles, labels, metrics, chart values, timestamps, tooltips, tags, and technical annotations. Use Inter only for long explanatory blocks, onboarding text, empty states, and supporting descriptions.<br><br>### Font rules<br><br>- Do not force font styles that are not loaded.<br>- Use IBM Plex Mono italics only for a few emphasized words or short fragments.<br>- Avoid excessive font variation.<br>- Prefer spacing, weight, and alignment over decorative hierarchy.<br>- Use tabular numerals for KPIs, dates, and time values whenever possible.<br>- Keep uppercase for micro-labels only when it improves clarity.<br><br>### Suggested scale<br><br>- App title: IBM Plex Mono, 28-36px, medium.<br>- Section titles: IBM Plex Mono, 16-20px, medium.<br>- KPI values: IBM Plex Mono, 28-40px, medium.<br>- KPI labels: IBM Plex Mono, 11-12px.<br>- Body copy: Inter, 15-17px.<br>- Meta labels: IBM Plex Mono, 11-13px.<br>- Tooltip values: IBM Plex Mono, 12-14px.<br><br>## Color system<br><br>The base interface should stay nearly monochrome, with accent colors reserved for meaningful states. The palette should work in both light and dark mode.<br><br>### Light mode<br><br>- Background: `#ffffff`<br>- Primary text: `#111111`<br>- Secondary text: `#555555`<br>- Faint text: `#8a8a8a`<br>- Primary line: `#111111`<br>- Secondary line: `#d9d9d9`<br>- Panel fill: `#ffffff`<br>- Hover fill: `#f3f3f3`<br>- Selected fill: `#ebebeb`<br><br>### Dark mode<br><br>- Background: `#0b0b0b`<br>- Primary text: `#f5f5f5`<br>- Secondary text: `#b8b8b8`<br>- Faint text: `#808080`<br>- Primary line: `#f5f5f5`<br>- Secondary line: `#2a2a2a`<br>- Panel fill: `#111111`<br>- Hover fill: `#1a1a1a`<br>- Selected fill: `#222222`<br><br>### Accent palette<br><br>- Signature accent: `#00E5FF` for selection, focus, active chart elements, and the main brand signal.<br>- Secondary accent: `#FF5722` for warnings, mixed nights, poor balance, and critical alerts.<br>- Support green: `#148a44` for balanced nights and positive signal states.<br>- Support amber: `#d17a00` for caution and intermediate states.<br><br>### Color rules<br><br>- Never use accents as large background washes.<br>- Keep most of the UI black, white, and neutral gray.<br>- Use accents in lines, dots, tags, markers, deltas, and selected-state details.<br>- One data point should have one primary meaning color.<br>- Avoid stacking many unrelated colors on the same element.<br>- Signature accent should be the main brand signal across the product.<br><br>## Shape language<br><br>Everything should be square and exact.<br><br>- Border radius: `0` everywhere.<br>- Buttons: rectangular.<br>- Panels: rectangular.<br>- Tooltips: rectangular.<br>- Inputs: rectangular.<br>- Chart frames: rectangular.<br>- Selection states: hard-edged and precise.<br><br>No soft shadows. Depth should come from linework, contrast, spacing, and occasional filled regions rather than blur.<br><br>## Layout system<br><br>The layout should feel grid-based and engineered.<br><br>### Spatial rules<br><br>- Use a strong outer frame around the app.<br>- Separate major areas with 1px lines.<br>- Use consistent gutters and spacing increments.<br>- Prefer columns, modules, and stacked bands over floating cards.<br>- Keep alignment strict.<br>- Use whitespace to create rhythm, not softness.<br><br>### Page hierarchy<br><br>1. Top header bar.<br>2. KPI band.<br>3. Main chart zone.<br>4. Selected-night annotation panel.<br>5. Supporting analysis blocks.<br><br>### Section treatment<br><br>Each section should read like a module in a technical dashboard:<br>- top label,<br>- thin divider,<br>- content area,<br>- optional footer note or metric context.<br><br>Avoid generic rounded cards. Use framed areas with hard edges and internal alignment.<br><br>## Component language<br><br>### Header<br><br>- Strong horizontal bar feeling.<br>- App name in IBM Plex Mono.<br>- Date range and dataset status aligned in columns.<br>- Thin line above and below the header area.<br><br>### KPI modules<br><br>- Rectangular blocks with 1px borders.<br>- Large metric value.<br>- Small label and delta note.<br>- Optional tiny sparkline.<br>- Keep charts inside KPI cards minimal and technical.<br><br>### Filters and controls<br><br>- Use segmented rectangular toggles.<br>- Active state should invert or accent the border.<br>- Avoid pill chips.<br>- Hover state can use a very light gray fill in light mode or a subtle dark lift in dark mode.<br><br>### Main chart<br><br>This is the visual anchor of the page.<br><br>- Use thin axes and precise ticks.<br>- Use black or gray default lines.<br>- Use the accent palette only for meaningful categories or selected states.<br>- Use a crosshair or vertical guide on hover.<br>- Tooltip should feel like a technical readout.<br>- Selected night should remain visible with a clear marker and an annotation panel update.<br><br>### Detail panel<br><br>- Present as a rigid information slab or side module.<br>- Use key-value pairs aligned on a grid.<br>- Use monospaced rhythm and thin separators.<br>- Show tags such as `alone`, `training`, `out`, `balanced`, `fragmented` as small outlined labels.<br>- Use the signature accent on the current selection.<br><br>### Tables and lists<br><br>- Think specification sheet, not settings page.<br>- Use horizontal rules.<br>- Avoid zebra striping unless very subtle.<br>- Right-align numeric columns.<br>- Use IBM Plex Mono for values and labels when readability holds.<br><br>## Chart styling rules<br><br>Charts should feel analytical and crisp.<br><br>- Thin strokes.<br>- No decorative smoothing unless analytically justified.<br>- Prefer straight or slightly softened lines.<br>- Use grid lines sparingly and lightly.<br>- Use square markers or minimal dot markers.<br>- Avoid large gradients.<br>- Use selection states clearly.<br>- Allow breathing space around the plotted data.<br><br>### Central chart logic<br><br>The main sleep view should support reading a night both as a point and as part of a larger system. A date-based mixed visualization is the right approach: sleep duration as the primary series, a rolling average overlay, and contextual markers for score, training, alone, out, or medication state. Hover should reveal precise nightly values; click should pin that night into the detail panel.<br><br>## Motion and interaction<br><br>Motion should be subtle, fast, and functional.<br><br>- No springy or playful transitions.<br>- Prefer 120ms to 180ms transitions.<br>- Hover changes should be immediate and crisp.<br>- Selection should feel like activating an instrument panel.<br>- Tooltips and detail panes should appear with minimal fade.<br>- Selection should be reinforced by the signature accent and a dedicated annotated panel.<br><br>## Imagery and decoration<br><br>Avoid decorative imagery unless it serves the data story.<br><br>- No organic illustrations.<br>- No soft gradients.<br>- No glowing backgrounds.<br>- No wellness-app moons, stars, clouds, or calm blobs.<br>- If using icons, keep them line-based and technical.<br><br>## CSS token direction<br><br>Implement the UI with a token system.<br><br>```css<br>:root {<br>  --bg: #ffffff;<br>  --text: #111111;<br>  --text-muted: #555555;<br>  --text-faint: #8a8a8a;<br>  --line: #111111;<br>  --line-soft: #d9d9d9;<br>  --panel: #ffffff;<br>  --hover: #f3f3f3;<br>  --selected: #ebebeb;<br><br>  --bg-dark: #0b0b0b;<br>  --text-dark: #f5f5f5;<br>  --text-muted-dark: #b8b8b8;<br>  --text-faint-dark: #808080;<br>  --line-dark: #f5f5f5;<br>  --line-soft-dark: #2a2a2a;<br>  --panel-dark: #111111;<br>  --hover-dark: #1a1a1a;<br>  --selected-dark: #222222;<br><br>  --accent-brand: #00E5FF;<br>  --accent-warning: #FF5722;<br>  --accent-success: #148a44;<br>  --accent-caution: #d17a00;<br><br>  --font-ui: &#39;IBM Plex Mono&#39;, monospace;<br>  --font-body: &#39;Inter&#39;, sans-serif;<br><br>  --radius-none: 0;<br>  --border-thin: 1px solid var(--line);<br>  --border-soft: 1px solid var(--line-soft);<br>}<br>```<br><br>## What to avoid<br><br>- Rounded corners.<br>- Glassmorphism.<br>- Large shadows.<br>- Purple/blue gradient AI-dashboard aesthetics.<br>- Too many accent colors.<br>- Centered marketing layouts.<br>- Soft health-app visuals.<br>- Decorative animation.<br>- Excessively dense tiny text everywhere.<br><br>## Final guidance<br><br>The frontend should feel like a calm technical instrument for reading sleep, not a wellness product. Keep the base monochrome, use the signature accent with discipline, let the mixed chart carry the story, and use the selected-night annotation panel to make each night legible at a glance.</pre><p>Above the design.md file</p><p>I used AI to help me think through the structure and provided different design references as inspiration, for doing that I used Perplexity. The goal was to create a shared direction before writing the interface: visual language, hierarchy, types of information, possible sections, and the way the data could be browsed.</p><p>This was important to me.</p><p>When I work on a digital product, I don’t usually start by drawing isolated screens. I try to understand the system first. What information exists? What relationships matter? What should be visible immediately? What can remain available for deeper exploration?</p><p>The same approach worked here, even though the product was only for me. So the next step was to creating an agents.md file that explains the purpose and the data structure to the AI. I always create these two files, design and agents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T81_M2vQav_d8savypc2UQ.png" /></figure><pre># agents.md<br><br>## Purpose<br><br>This project uses a normalized sleep dataset generated from the Google Form export file `28.07.2026.csv`.[file:3]<br>The goal is to keep a stable machine-friendly dataset for a frontend dashboard while preserving the CSV as the raw ingestion format.[file:3]<br><br>## Files<br><br>- `output/sleep_normalized.csv`: cleaned tabular dataset for inspection and backup.<br>- `output/sleep_normalized.json`: frontend-ready dataset for a dashboard app.<br>- Raw source: the latest exported CSV from Google Forms, currently based on `28.07.2026.csv`.[file:3]<br><br>## Canonical schema<br><br>Each row represents one sleep date after deduplication.[cite:1]<br><br>| Field | Type | Meaning |<br>|---|---|---|<br>| `sleep_date` | string | ISO date `YYYY-MM-DD`. |<br>| `bed_time` | string | Time you went to bed. |<br>| `asleep_time` | string | Estimated sleep onset time. |<br>| `wake_time` | string | Final wake time. |<br>| `score` | number | Subjective sleep quality score. |<br>| `awakenings_count` | number | Number of awakenings or encoded count. |<br>| `dream_count` | number | Number of dreams remembered. |<br>| `nightmares_count` | number | Nightmare indicator/count from source data. |<br>| `slept_alone` | number | 1 yes, 0 no. |<br>| `slept_out` | number | 1 yes, 0 no. |<br>| `trazodone_mg` | number | Numeric trazodone dose. |<br>| `trazodone_formulation` | string | `standard` or `retarded`. |<br>| `training_flag` | number/null | 1 yes, 0 no, null unknown. |<br>| `sleep_latency_min` | number | Minutes from bed time to asleep time. |<br>| `sleep_duration_min` | number | Minutes asleep until wake time. |<br>| `time_in_bed_min` | number | Minutes in bed from bed time to wake time. |<br><br>## Normalization rules<br><br>The agent must always apply these rules when the CSV is updated.[file:3][cite:1]<br><br>1. Read the newest raw CSV export.<br>2. Rename columns into the canonical schema.<br>3. Parse `sleep_date_raw` into ISO format.<br>4. Convert numeric-like columns to numbers.<br>5. Normalize `training_flag` so `1/0/si/no/yes/no data` become `1/0/null`.<br>6. Split `Trazodone hydrochloride mg` into:<br>   - `trazodone_mg`: numeric dose.<br>   - `trazodone_formulation`: `retarded` or `standard`.[file:3]<br>7. Recompute derived fields:<br>   - `sleep_latency_min`<br>   - `sleep_duration_min`<br>   - `time_in_bed_min`.[cite:1]<br>8. Deduplicate by `sleep_date`.<br>9. If more than one row exists for the same `sleep_date`, keep the last row in file order because it is the most likely correction entry.[cite:1]<br>10. Write both normalized CSV and JSON outputs.<br><br>## Update workflow<br><br>When the source CSV gains one or more new rows, the next agent should continue from the files, not from chat history.[file:3]<br>The agent should treat the raw CSV as append-only input and rebuild the normalized outputs from scratch on every run.[cite:1]<br><br>### Agent instructions<br><br>Use this exact operational flow:<br><br>1. Open the latest raw CSV file.<br>2. Generate a fresh normalized dataset using the canonical schema and normalization rules above.<br>3. Overwrite `sleep_normalized.csv` and `sleep_normalized.json`.<br>4. Check whether new dates were added.<br>5. Check whether an existing date now has multiple entries.<br>6. Keep only the latest entry for duplicated dates.<br>7. Report:<br>   - how many rows were read,<br>   - how many valid dated rows were kept,<br>   - how many duplicate dates were resolved,<br>   - which new dates were added since the previous normalized file, if any.<br><br>## How to detect newly added rows<br><br>If a previous `sleep_normalized.csv` already exists, compare the old and new normalized outputs by `sleep_date`.[cite:1]<br><br>- New row = a `sleep_date` present in the new file but not in the previous normalized file.<br>- Updated row = a `sleep_date` present in both, but one or more fields differ.<br>- Duplicate resolution = more than one raw row maps to the same `sleep_date`; keep only the last raw row.[cite:1]<br><br>## Recommended project structure<br><br>```text<br>project/<br>├─ data/<br>│  ├─ raw/<br>│  │  └─ 28.07.2026.csv<br>│  └─ processed/<br>│     ├─ sleep_normalized.csv<br>│     └─ sleep_normalized.json<br>├─ scripts/<br>│  └─ normalize_sleep.py<br>├─ src/<br>│  └─ dashboard frontend<br>└─ agents.md<br>```<br><br>## Suggested agent prompt<br><br>Use this prompt in your IDE agent when the CSV gets updated:<br><br>```md<br>Read the latest raw sleep CSV in `data/raw/`. Rebuild the processed sleep dataset using the rules in `agents.md`. Deduplicate by `sleep_date` keeping the last row in source order. Output both `data/processed/sleep_normalized.csv` and `data/processed/sleep_normalized.json`. Then summarize new dates added, updated dates, duplicates resolved, and any parsing anomalies.<br>```<br><br>## Notes<br><br>This file is based on the cleaned structure found in `28.07.2026.csv`, which is currently the best source among the provided variants for dashboard ingestion.[file:3]<br>The raw CSV should remain the archival source, while the normalized outputs should be the only files consumed by the frontend.[file:3][cite:1]<br><br>## Frontend analysis modules<br><br>The dashboard (`src/`) includes reusable data analysis built on the normalized JSON:<br><br>| Module | Purpose |<br>|---|---|<br>| `src/lib/data.ts` | Type definitions, data loading, enrichment |<br>| `src/lib/metrics.ts` | Averages, rolling windows, period comparisons, grouping |<br>| `src/lib/correlations.ts` | Pearson r, correlation matrix, condition effect comparisons |<br>| `src/lib/format.ts` | Human-readable formatting for dates, durations, percentages |<br>| `src/lib/scoring.ts` | Night classification, color assignment, badge logic |<br><br>When adding new analyses, prefer extending these lib modules over inline logic in components.</pre><p>Once the design and the data direction was clear, I moved to the code.</p><h4>Zed, OpenCode, and React</h4><p>I used Zed as my IDE.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YjP2FAJGak83ksouRTTN7g.png" /></figure><p>I like Zed because it is neat, simple, fast, and clean. It does not feel overloaded, but it is still powerful enough for serious development work.</p><p>I used OpenCode separately as the AI coding tool. OpenCode Go is a subscription that provides access to open coding models. Zed was the environment where I worked, while OpenCode was the AI agent I used to help analyse the data and write the code.</p><p>The project was built with React.</p><p>My role was not to ask an AI to “make me a dashboard” and accept whatever appeared. I directed the process.</p><p>First, I used AI to clean and analyse the data. An IDE environment is a super powerful tool, you can also just use it to analyse a data set or an entire project the same way you upload docs to the KB in ChatGPT or Claude, just way more powerful. Then I used it to help build the interface. I reviewed the output, corrected it, asked new questions, changed the direction, and refined the result.</p><p>The process was closer to directing than delegating.</p><p>I had the data and the questions. The AI helped me move faster through the technical work, but I still had to decide what was meaningful, what was misleading, and what deserved to be visible.</p><p>The project was eventually deployed as a live website:</p><p><a href="https://www.aandreetto.me/sleep/">Dreams - Sleep Dashboard</a></p><h4>Browsing 364 nights</h4><p>The first thing the page shows is a set of high-level insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RsgaDbOZbVeCPyhCMVvSHg.png" /></figure><p>The dataset contains 364 nights, and each night is represented as a double line: one line for the time it took me to fall asleep and another for the time I spent sleeping.</p><p>This became one of my favourite parts of the project because it makes the year feel tangible.</p><p>A spreadsheet gives you rows. The timeline gives you a rhythm.</p><p>You can see when I went to bed, when I finally fell asleep, and how long I slept. You can see periods that look relatively stable and others that become more irregular. I wanted to be able to see the big picture as the single night detail.</p><p>After the timeline, the interface includes a series of charts:</p><ul><li>Sleep duration compared with subjective score</li><li>Average latency by condition</li><li>Monthly trends</li><li>Sleep-duration distribution</li><li>Night-quality categories</li><li>Dream frequency</li><li>Training versus no training</li><li>Awakenings and score</li><li>Correlations between the different fields</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*keLnbSVrxwF1uTYL8fzCMw.png" /></figure><p>The interface is not trying to be a medical tool. It is a way to browse a personal dataset and ask better questions.</p><h4>What the data showed me</h4><p>The first thing I understood was that my perception of my sleep was much worse than reality (common pattern among people with sleeping problems.</p><p>I thought I was sleeping less than I actually was. The data did not show perfect sleep, but it showed something more nuanced than my memory.</p><p>The dashboard reports an average of 6.9 hours of sleep across all nights (positive trend, last year was around 5), and 7.1 hours over the last 30 days. The average time to fall asleep was 43 minutes, and the average subjective score was 5.6 out of 10. Sixty percent of the nights included awakenings.</p><p>These numbers do not describe a good or bad sleeper. They describe a pattern.</p><p>One of the clearest lessons was that sleep duration and perceived sleep quality were not always connected.</p><p>A night when I slept for eight hours could still receive a score of 4. Another night could receive a much better score despite a shorter sleep duration.</p><p>This is probably obvious when stated in isolation, but it was not obvious when I was living through each individual night.</p><p>When I woke up feeling terrible, that feeling became the definition of the night. The data made it possible to separate the experience of the morning from the measurable characteristics of the night.</p><p>Neither one was “the truth” on its own. They were two different descriptions of the same event.</p><h4>The training assumption</h4><p>Before analysing the data, I was convinced that training influenced my sleep.</p><p>I exercise regularly, and it seemed reasonable to assume that physical activity wouldn’t help me fall asleep more easily. I had the precise feeling that in those nights I was taking way longer to fall asleep.</p><p>The data did not support that assumption.</p><p>The average latency after training was 39 minutes, compared with 50 minutes without training. That difference was visible, but it did not tell me that training had a decisive effect on my sleep, actually more the opposite. The wider dataset showed a more complicated picture, and I could not turn this observation into a simple cause-and-effect conclusion.</p><p>The most useful result was not proving that training helped or did not help.</p><p>It was discovering that my intuition was not reliable enough to be treated as evidence.</p><p>I had a theory. I collected data. The data forced me to make the theory more precise.</p><h4>Treatment and trends</h4><p>I also noticed a trend toward more sleep during the treatment period.</p><p>The data showed an increase in sleep duration over time, especially when looking at the monthly trend. But this project was observational, not a controlled experiment.</p><p>There were too many variables involved: the medication and its changing dosage, my expectations, daily routines, stress, training, and the natural variation between nights.</p><p>So I cannot say that the treatment alone caused the change.</p><p>What I can say is that the trend was visible in my data, and that it matched the general feeling that things had started to improve.</p><p>That distinction matters.</p><p>Personal data can help you notice patterns, but noticing a pattern is not the same as proving a cause.</p><h4>When tracking became the problem</h4><p>The most important thing I learned was not in any of the charts.</p><p>At some point, tracking my sleep started to become a job.</p><p>In the beginning, the Google Form was useful because it gave me perspective. It helped me understand that my perception was often worse than the data.</p><p>But after months of filling it in, the act of monitoring became increasingly important.</p><p>I started thinking about the form, the numbers, and the quality of the coming night. The measurement was no longer only observing my sleep. It was becoming part of my sleep experience.</p><p>The system I created to reduce uncertainty was creating another kind of attention.</p><p>Every night had to be recorded. Every morning had to be evaluated. The score had to be chosen. The experience had to be converted into data.</p><p>At some point, monitoring my sleep became more important than sleeping.</p><p>That was the moment when the project reached its real conclusion.</p><p>A system can be useful and still become too demanding. A dashboard can clarify a problem and still encourage you to look at it too often. More information is not automatically better information.</p><h4>Designing a personal tool</h4><p>This project started because I had a personal problem and wanted to understand it better.</p><p>It became a data-collection exercise, then a spreadsheet, then an analysis project, and finally a React interface built with Zed and OpenCode.</p><p>But the most interesting part was not the technology.</p><p>It was applying my professional way of thinking to a private experience.</p><p>As a designer, I am used to breaking down complexity, making invisible relationships visible, and creating interfaces that help people navigate information.</p><p>This time, the person was me.</p><p>The user research was my own memory. The input method was a one-minute Google Form. The backend was a Google Sheet. The dataset was 364 nights. The interface was a small React application.</p><p>And the final insight was that the best-designed system is not necessarily the one that collects the most data.</p><p>Sometimes the most important thing a personal tool can tell you is when to stop using it.</p><p>This post was written with the support of an AI.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1aa8357070dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI-Enabled Experiences: a designer team’s logbook]]></title>
            <link>https://medium.com/sketchin/ai-enabled-experiences-a-designer-teams-logbook-cd4c8608ffad?source=rss-ff4b9d4d6203------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd4c8608ffad</guid>
            <category><![CDATA[ixdesign]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[ai-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[microsoft-copilot]]></category>
            <dc:creator><![CDATA[Alberto Andreetto]]></dc:creator>
            <pubDate>Fri, 14 Nov 2025 09:30:47 GMT</pubDate>
            <atom:updated>2025-11-14T09:30:47.555Z</atom:updated>
            <content:encoded><![CDATA[<p>In this logbook, we share what we learned while creating conversational assistants, with ten practical lessons for designers ready to take on these challenges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dlTOfhZ2wlyLaSm5PTh4HQ.avif" /></figure><p>This article is a short guide written by designers for designers.</p><p>It’s not a technical piece or an academic paper, but an honest account of what we learned working on projects where generative AI and conversational agents weren’t just one tool among many, but the real core of the designed experience.</p><p>If you’re looking for a catchy quote to share on LinkedIn, this article might not be for you. <strong>Here we talk about hands-on design, the kind made of trials, mistakes, and constant iterations. </strong>It’s a story meant for those who, like us, are “in between”: between strategy and the final outcome, between vision and implementation.</p><p>Recently, we worked on two very different projects, both driven by the same goal: <strong>building a conversational AI assistant that is useful</strong>, accessible, and aligned with people’s real needs.</p><ul><li><strong>Nexi</strong> — Alberto worked on a virtual customer care assistant. It was a 9-month project where, together with Nexi’s internal Design Studio, we analyzed different business areas to understand where generative AI could have the greatest impact on end users. After evaluating KPIs and ROI, customer support turned out to be the most promising field: the goal was to move from generic support to a tailor-made service, able to provide targeted and relevant answers.</li><li><strong>Lenovo</strong> — Gea worked on LIA (Lenovo Intelligent Assistant), a 6-month project in the B2C retail context. We have been collaborating with Lenovo for many years on several initiatives, but this was an experimental stream, created to test the application of AI in retail spaces and understand what real value it could bring. <br>LIA is an AI assistant that simplifies product selection within a very broad catalog, adapting language and content to the user’s level of expertise. The experience combines a modular interface, light animations, and a distinctive physical presence in-store. The system integrates multiple layers (from data sources to frontend) and is built on an AI architecture able to understand user needs and return concise, technical, and personalized answers.</li></ul><p>After explaining “how it’s done” too many times to colleagues and curious friends, we decided to gather what we learned into ten points and share it with others who, like us, are facing these challenges from scratch or almost. These are not absolute truths, but lessons born from attempts, successes, and above all mistakes. Maybe they’ll be useful for you too.</p><h3>01. Concreteness first</h3><p>A conversational assistant only makes sense if it’s <strong>useful</strong>. And to be useful, it has to be clear, immediate, and action-oriented. The user wants to get an answer in just a few steps, without unnecessary extras. This means designing <strong>simple interfaces, short but sharp responses, and smooth interactions.</strong></p><p>Behind this apparent simplicity, though, lies a <strong>complex structure</strong>: intents, datasets, smart fallbacks, continuous iteration between design, data, and development. All of this has to stay backstage. The user should never notice it. What matters is that the assistant enables a new way of conversing, just as natural and immediate, but also consistent with the brand’s identity and values.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*UnH0kWr9PE2V9h2WH4ybxQ.gif" /><figcaption>Nexi conversational chatbot</figcaption></figure><blockquote><strong><em>Tips for designers</em></strong></blockquote><blockquote><em>To get a feel for interactions and content, start by </em><strong><em>writing answers as if you were quickly chatting with a colleague</em></strong><em>: no more than three sentences, verb at the beginning, and a closing action (“Want to see the models?”, “Here’s what you can do now…”).</em></blockquote><blockquote><em>For the interface, make sure to</em><strong><em> map all the sites and properties where your assistant will live.</em></strong><em> Define the right placement for each of them, and design accordingly based on how much visual attention it will get.</em></blockquote><blockquote><em>Once you’ve imagined the flow, try to </em><strong><em>reduce the number of steps needed to reach an answer</em></strong><em>: every extra click or input is unnecessary cognitive effort. Plan shortcuts and smart suggestions, and decide whether your assistant should be proactive and engaging.</em></blockquote><h3>02. Language is design (and vice versa)</h3><p>Writing for an AI assistant is not the same as writing for a website or an app. Every word, every tone, every pause is part of the experience. The language has to adapt to the audience while staying consistent with the brand identity.</p><p><strong>This means working on the assistant’s voice, not as sound, but as personality</strong>: attitude, style, and way of responding. With LIA, for example, we defined a professional yet simple tone, in line with the experience of a retail store. For Nexi, instead, we designed a reassuring voice: authoritative, but without being formal or distant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pbvIQBP_pC1qoWumtk6ZOw.avif" /></figure><blockquote><em>Tips for designers</em></blockquote><blockquote><em>From the start, </em><strong><em>create a guideline document with tone, words to avoid, and good vs. bad examples</em></strong><em>. Use it as a living, updatable reference for the whole team. It doesn’t need to be perfect, but it’s essential to align and collaborate even before you have a testable product.</em></blockquote><blockquote><strong><em>Write answers as if they had a body, a posture, an intention.</em></strong><em> Always ask yourself: “What attitude am I conveying?”If it helps, try role play: imagine how other brands (especially competitors) would express the same concept. Or choose a public figure as inspiration for your bot’s style and tone. At Nexi, for instance, we looked at Cecilia Sala’s way of speaking: direct, friendly, young but also authoritative and reliable.</em></blockquote><blockquote><em>If you’re still unsure about the direction, you can always </em><strong><em>run A/B tests with different tones of voice for the same answer.</em></strong><em> You’ll quickly see what builds trust, clarity, or empathy depending on the context. You can test everything, from reply formats to character traits. Pro tip: it can even become a fun exercise for the team to check if everyone imagines the assistant the same way, with the same voice, tone, and personality.</em></blockquote><h3>03. Animation is content</h3><p>When designing an assistant, identity, visuals, and animations play a key role. They’re not decorative extras but help make AI feel tangible, whether in a digital or physical context.</p><p>With LIA, we chose to give the assistant a visual presence, without falling into the trap of over-personification. With Nexi, on the other hand, the absence of strong animations, personification, or branded elements was a deliberate choice. Even absence is a message: it allows users to focus more on the content. <strong>Every movement, every pause, every transition tells something about the experience you’re offering.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*y2LikyCMG9-yhMXu5a2UdA.gif" /></figure><blockquote><em>Tips for designers</em></blockquote><blockquote><em>Define when and why the assistant (whether avatar or interface) moves, and how those movements are (or aren’t) part of its identity. </em><strong><em>Every animation must have a purpose</em></strong><em>, such as marking a pause or confirming an action.</em></blockquote><blockquote><em>Response times can easily kill the “mood” and make attention vanish in an instant.</em><strong><em> Use micro-delays and transitions to handle AI timing</em></strong><em>: they cover dead moments and make waiting feel less cold.</em></blockquote><blockquote><em>Avoid overly human gestures or movements unless they’re a defining trait of the agent you’re designing.</em><strong><em> Make the assistant feel alive, but not caricatured.</em></strong><em> Aim for a sober, recognizable balance that fits the content, the brand, and user expectations.</em></blockquote><h3>04. AI is more than just a feature, it’s a whole system</h3><p>An AI assistant isn’t just a function you turn on with a click. <strong>It’s a complex system where the interface is only the tip of the iceberg. </strong>Everything else, data ingestion, intent mapping, reducing unnecessary calls, fallbacks, and the UI, needs to be designed in an integrated way.</p><p>Teamwork is essential here; no one can work alone. You need a multidisciplinary team including designers, developers, data analysts, and product owners. You also need an iterative process: design, test, adjust. More times than we’d like to admit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5QWwDLAuZI7WpUo_Tcy4yA.avif" /></figure><blockquote><strong><em>Tips for designers</em></strong></blockquote><blockquote><strong><em>Knowing where the assistant will be used is fundamental to its design. </em></strong><em>Depending on the platform, many things can be completely different. This affects the design environment, the interface, and even how interactions start and end within the broader experience.</em></blockquote><blockquote><strong><em>Design the entire conversational ecosystem</em></strong><em>, not just the screens: include intents, fallbacks, voice interactions, and human escalation. Think especially about what happens before and after the interaction with the assistant.</em></blockquote><blockquote><em>Organize co-design sessions between design, development, and data teams: </em><strong><em>a change to one intent can affect the entire experience. </em></strong><em>To make it more engaging, try switching roles within the team and revisit decisions already made: how would someone from data design this micro-interaction?</em></blockquote><blockquote><strong><em>Document the assistant’s evolution over time with dynamic flow maps. </em></strong><em>They’ll help you track discarded options, considered alternatives, or ideas you initially set aside that might become useful later.</em></blockquote><h3>05. The cost of AI</h3><p>Generative AI is powerful, but it comes at a cost, not just financially, but also in terms of <strong>efficiency and environmental impact</strong>. In some cases, deterministic responses work better: they’re faster, more reliable, and less expensive.</p><p>In the Nexi project, for example, <strong>only 37% of over 130,000 monthly intents are handled with generative AI</strong>. The rest operates deterministically, without using AI for every single request. This approach helps control costs while maintaining high performance, especially for a tool accessed by tens of thousands of users every day, 24/7.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Yf1OYNJOGYWdcKf9uleNg.avif" /></figure><blockquote><strong><em>Tips for designers</em></strong></blockquote><blockquote><strong><em>Identify “repetitive” tasks that can be automated with fixed rules</em></strong><em>, using lists of common user queries (e.g., FAQs, hours, product info). This reduces calls to AI by providing deterministic answers.</em></blockquote><blockquote><em>Pair each answer with a follow-up question </em><strong><em>to shorten interaction times</em></strong><em>, lower costs, and guide users through a proactive conversation.</em></blockquote><blockquote><strong><em>Create dashboards with cost metrics per interaction.</em></strong><em> Use them to decide what to optimize, reduce, or disable. This makes it easier to deliver the desired answer more efficiently.</em></blockquote><h3>06. Data: the real elephant in the room</h3><p>Data is the foundation of any assistant. It’s the knowledge base that the assistant relies on to generate responses. Often, it’s the biggest challenge: data can be messy, unstructured, or inaccessible. Before thinking about crafting a good conversation,<strong> you need to get your data in order.</strong></p><p>In some cases, collecting, cleaning, organizing, and updating data becomes a project within the project. And no, opening unrestricted access to the internet is not the solution. The more open the system, the higher the risk of hallucinations or inaccurate answers.</p><p>Data quality remains the real critical point, especially when dealing with company information to ensure consistency with the brand. For example, if product line data is inaccurate or outdated, the assistant might provide wrong information or even redirect users to content that doesn’t accurately represent the brand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*urKi5rytXih79zuK-7mpHw.gif" /><figcaption>The complexity of the data that powers the LIA assistant, hidden behind the user interface.</figcaption></figure><blockquote><strong><em>Tips for designers</em></strong></blockquote><blockquote><em>Take a </em><strong><em>structured inventory of your data before starting</em></strong><em>: list what exists, what’s missing, and the quality or accessibility of each data point.</em></blockquote><blockquote><strong><em>Clean and normalize content</em></strong><em> into AI-readable formats: any anomaly can compromise responses.</em></blockquote><blockquote><strong><em>Define the scope of your assistant’s knowledge</em></strong><em> in advance: it’s better to have limited but reliable knowledge than broad but potentially incorrect information, especially when it comes to company data or unverifiable information online.</em></blockquote><h3>07. Testing is the hardest (and most useful) part</h3><p>Testing an interface is relatively simple. <strong>Testing a conversational assistant is much more complex. </strong>There are thousands of possible combinations, and you can’t predict everything. It takes weeks of testing, trial runs, and error analysis.</p><p>For Nexi, nearly half of the project time (4–5 months out of 9) was dedicated to testing: we ran prompt tests, simulations, collected user feedback, and iterated continuously. It’s a long and not always rewarding process, but it’s what makes the difference between an assistant that truly works and one that leaves you hanging mid-sentence, or even gives a wrong answer or one that doesn’t align with the brand’s values.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*-BH-cnx_JtQ5KuXMhnsz1A.gif" /><figcaption>Excel sheet representing the complexity of the Nexi customer support service.</figcaption></figure><blockquote><strong><em>Tips for designers</em></strong></blockquote><blockquote><em>If you can’t test extensively with real users, </em><strong><em>build a conversational test suite with realistic</em></strong><em>, imprecise, and poorly phrased questions. Simulate real users, not ideal ones. Use the flows you designed at the start to follow all branches and ensure the assistant provides the intended answers.</em></blockquote><blockquote><strong><em>Keep a conversation log</em></strong><em> to classify errors: language, tone, understanding, or data. Every mistake is a goldmine of information.</em></blockquote><blockquote><strong><em>Conduct qualitative tests with real users</em></strong><em>, in person or remotely. Body language often tells more than words, and you can always ask follow-up questions to better understand expectations and frustrations.</em></blockquote><h3>08. Design is also education</h3><p>An AI assistant doesn’t just respond; <strong>it educates and guides user choices. </strong>And with that comes responsibility. Designing a clear, ethical, and understandable experience also means helping users navigate what they can and cannot ask. Transparency, simplicity, and an approach that considers different levels of attention or knowledge are essential. Even behind an automatic response, there’s a design intention that can improve (or worsen) the user’s experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*1-U-3y1Et22b_3L0t_Wudw.gif" /><figcaption>LIA answers a user’s question by clarifying that Lenovo Yoga devices have no gender distinction.</figcaption></figure><blockquote><strong><em>Tips for designers</em></strong></blockquote><blockquote><strong><em>Design a conversational onboarding</em></strong><em> that immediately shows users what they can do and how. Using natural, conversational interactions makes it easier for users to get oriented, making the onboarding more effective.</em></blockquote><blockquote><strong><em>Avoid vague messages</em></strong><em> like “How can I help?” Be specific, e.g., “I can help you choose a computer or find a compatible accessory.” This reduces costs while increasing user understanding and clarity.</em></blockquote><blockquote><strong><em>Include responses that positively acknowledge the AI’s limits</em></strong><em>: “I can’t do X yet, but I can help you this way…” It’s not about the assistant being able to do everything, but about doing what it was designed for accurately and excellently.</em></blockquote><h3>09. Reduce overload, maximize understanding</h3><p>Every word counts, and every image must serve a purpose.<strong> The goal is to deliver the message as simply as possible. </strong>We worked a lot on balancing text, images, and voice. Users don’t have time or patience to read long paragraphs. Design must consider cognitive limits and support comprehension, even when users are multitasking. A good assistant is one that doesn’t make you think too much but helps you get what you need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ES_7Fh_01V5d90I11Y2XXA.gif" /><figcaption>LIA interface displaying Lenovo product search results.</figcaption></figure><blockquote><strong><em>Tip for designers</em></strong></blockquote><blockquote><strong><em>Write in a pyramid structure</em></strong><em>: start with the answer, then add details, and finally provide deeper information if requested. This simplifies the conversation flow and reduces the number of interactions. A user who quickly finds what they need is a happy user.</em></blockquote><blockquote><strong><em>Simplify visuals and text </em></strong><em>until it feels almost too minimal. Then remove a bit more, if it still feels essential, you’re probably at the right level.</em></blockquote><blockquote><strong><em>Test interfaces in real conditions</em></strong><em>, on the move or while multitasking. If it works there, it will work anywhere. You can even conduct some user tests in these scenarios.</em></blockquote><h3>10. Do or do not, there is no try (Yoda)</h3><p>Many things that seem obvious to us today were learned through mistakes. No course or article (even this one) can replace direct experience. We learned by collaborating with developers, iterating on conversations, and reviewing answers a thousand times. And we’re still learning. The best advice we can give? Start. Try. Fail. Repeat.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*jGUv6hnCaLyXZrrYRB4K4w.gif" /></figure><blockquote><strong><em>Tip for designers</em></strong></blockquote><blockquote><em>At the beginning, </em><strong><em>set up a small experimental environment to test new features</em></strong><em>, even unfinished ones: it’s better to fail on a small scale. You can even create GPTs to help, you’ll see it’s really simple.</em></blockquote><blockquote><strong><em>Establish a shared process with developers</em></strong><em> to log and analyze every mistake, turning them into opportunities for improvement. Use gamification to make it fun, like a points game or a fantasy contest.</em></blockquote><blockquote><strong><em>Schedule monthly retrospectives</em></strong><em>: what did we learn? What didn’t work? What will we try next? This will help you develop your own way of working and collaborating on new challenges.</em></blockquote><h3>Conclusion</h3><p><strong>Designing an AI assistant is, above all, a team effort.</strong> There are no rigid roles or clear boundaries: interaction designers, visual designers, copywriters, developers. All must work together, share decisions, debate, and be willing to change their minds. No one designs alone, and no one reaches the finish line by themselves. In our projects, the most effective solutions emerged during intense collaboration, when we combined different skills and perspectives.</p><p>We wrote answers together, tested conversations in Excel sheets, discussed animations in Figma, and refined microcopy directly in the code. The final result was never a single moment of inspiration, but the sum of many shared iterations.</p><p><strong>If there’s one takeaway, it’s that conversational design isn’t just a new type of design.</strong> It’s a new way of collaborating and being a designer within a team.</p><p>This article has been written with <a href="https://www.linkedin.com/in/gea-sasso/">Gea Sasso</a>, checked by the Sketchin Edge team and fixed with use of AI. Published first <a href="https://www.sketchin.com/foresight/ai-enabled-experiences-10-lessons/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd4c8608ffad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sketchin/ai-enabled-experiences-a-designer-teams-logbook-cd4c8608ffad">AI-Enabled Experiences: a designer team’s logbook</a> was originally published in <a href="https://medium.com/sketchin">Moving forward</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interaction design is everywhere. How to design human interactions mediated by technology]]></title>
            <link>https://medium.com/sketchin/interaction-design-is-everywhere-dc4971434178?source=rss-ff4b9d4d6203------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc4971434178</guid>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[human-interaction]]></category>
            <dc:creator><![CDATA[Alberto Andreetto]]></dc:creator>
            <pubDate>Sun, 21 Aug 2022 20:23:43 GMT</pubDate>
            <atom:updated>2022-09-06T15:14:54.444Z</atom:updated>
            <content:encoded><![CDATA[<h4>Interaction design is a discipline that rules how a user interacts with a service or a product. Despite this, it’s mainly recognised in how we design an app or a website.</h4><p>Before getting into the core of this article, I just wanna point out a concept that we use so many times on a daily base without paying too much attention: Touchpoint.</p><p>A <a href="https://www.nngroup.com/articles/channels-devices-touchpoints/"><strong>touchpoint</strong></a><strong> </strong>represents a specific interaction between a customer and an organisation. It includes the device being used (a smartphone, a laptop or a tv), the channel used for the interaction (phoning, app, social media), and the specific task to be completed (need of assistance, buying something or requesting a ride). Said that here few examples of what is not a touchpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ho6BeZCCbf7P3DVmAGgWFA.jpeg" /><figcaption>An iPhone, an iPad and a desk. Those are not touchpoints</figcaption></figure><p>So, requesting an Uber via the app, looking for a specific movie on Netflix on your tv or calling for assistance are touchpoints. What all these have in common is that they are moments of interaction between a user and a service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KBuK3TpsiedlyfW12BBoZQ.png" /><figcaption>Thank you, Don, for explaining what a touchpoint is</figcaption></figure><p>We experience hundreds of interactions moments during our life every day, we have digital interactions when we browse a website or an app. We have physical interaction when we do laundry or when we withdraw cash at the ATM. BTW, have you ever thought about this simple action? We get back first the card and then the money because otherwise, the majority of the users would forget the card. It’s designed to be like this. Nowadays, we are more and more overwhelmed by voice interactions every time we talk with Siri or Alexa. The last interaction I want to cover is probably the most important one. Human interactions, every time you interact with the delivery guy or with the employee at the airport gate, you are experiencing that.</p><p>So basically, we’ve seen that interaction design is not only about apps but also about people. I don’t wanna talk about the normal human interaction we have every day, I’d like to focus on technology-mediated human interaction. As designers, we should shift a little bit from spending hours crafting that animation of the button on Figma to designing an experience that somehow involves also an app, not only an app. There are thousands of situations in which we have to design something where an app is not involved, so why do we all focus on that? Probably because is simpler to just attend a Figma course (btw, I love Figma, just saying) than challenge ourselves on how to fix a problem beyond an app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OU-y7ekcrJVbfRG2_GZGjQ.jpeg" /></figure><h3>From screens to real life</h3><p>One example of when we should go beyond the app is when we talk about embodied interactions. Smartphones and screens are just a means to achieve goals, they are not the focus of our job. Think about the paying experience, we were used to the credit card, then it went inside our phone first and our watch later till became an RFID chip under our skin. Or diabetes-controlling systems used to be bulky devices before becoming an app and finally moving into an always-on sensors. Those two examples explain perfectly that the app is not the final step of what we do; the experience is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OK04xftSvMMeE8joowMgAg.jpeg" /><figcaption>Right to left — From a physical card to something that is invisible to the sight</figcaption></figure><p>I spent a few years in Sketchin desiring technology-mediated human interactions, and I saw some patterns and tips that maybe could help everyone else when approaching the same challenge. Here we go.</p><h4>01. Consistent experiences</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*eKbCR6xYnP8TLthjV_B7Gw.gif" /></figure><p>Doesn’t matter if you are designing an app for a completely remote check-in or an in-person check-in. Both<strong> have to provide the same experience to the final user</strong>. The only difference we can design is if we want to push one kind of interaction or the other. In that case, the experience can be different.</p><h4>02. Micro journey</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*x5eHA3iW-dO4J_a63lPHfA.gif" /></figure><p>Instead of focusing on the single moment of interaction and spending hours thinking about that button, pay attention to <strong>where the user is coming from and where is going</strong>. If we are designing an app for a doctor, maybe he/she just made an exam on a patient on another system. If we need to design a booking system for a marina, remember that the user could be sailing at that moment with a poor connection. Go a little bit wider when you think about the specific interaction.</p><h4>03. Common sense</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*kWqnGbk40NBphQc2UhR-ow.gif" /></figure><p>Ok, this is the biggest learning of my career. We’re not rocket scientists, and <strong>we don’t save lives,</strong> so please use a little bit of that common sense to design something easy to use and not a nightmare. If we have to design an ordering platform for a barista, remember that he/she has busy hands and a lot of customers waiting for their coffee, she’s not using the dashboard on a couch holding the iPad with two hands. Same for a driver app. He/she’s driving. In that case, probably, the CTAs have to be bigger than 44x44 points.</p><h4>04. Design the moment placefullness</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*DjxxuVPCRyytnXM_Ab-LIw.gif" /></figure><p><a href="https://www.mobileuserexperience.com/design-talk-68-the-future-is-in-the-air-mark-rolston-co-founder-argodesign/6663/">Placefulness</a> is a concept by Mark Rolston in which a digital asset acquires properties within a specific location in the real world. I’d like to extend a little bit this idea, <strong>not only in a specific location but also in a specific moment</strong>. Think about the insurance app that understands you just had a car accident and calls the emergency numbers for you, and that starts a report to the company automatically. Imagine a medical app that provides info to the patients based on a specific location in the hospital or after a specific exam.</p><h4>05. You can’t control everything</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*0M89AqpYvRpfqaGCeD4gOQ.gif" /></figure><p>This is something we need to deal with if we design a financial app we can control every dead-end path and every interaction if we design a technology-mediated human interaction we can push this to a certain limit after that we just have to hope for the best. We can design the best way to show a path to go from A to B on an app to request a drive, but then we have a real person picking up our user. The driver maybe is aware of something we don’t and will change the route or will forget to ask the user to do something we require for our service. <strong>Deal with it, you can’t design people</strong>.</p><h4>06. Training</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*LHpSCg8z_TnpYd45HnDPsw.gif" /></figure><p>If you design human interactions, then you’ll have to train the actors of your service on how to behave and what to do. Again, on a financial app, probably no one has to be trained, but on a food delivery system, you have to, do not forget that <strong>untrained people will ruin your service</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dE8K-vS5TasYEboA2_zgHg@2x.png" /><figcaption>The training session we designed for D-Marin took place in Göcek, Turkey</figcaption></figure><h4>07. What makes the difference in a situation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*9RoALV8J4Uc7WGhElHvPpw.gif" /></figure><p>When involving human interaction in a service, we have a<strong> huge variety of possible scenarios</strong>, we can guide the experience towards the ideal one, but we know that there is an infinite scenario that can happen apart from the desired one. We have to go with them, keeping them in our design.</p><h3>Hey, where is the technology?</h3><p>We just saw some concepts to keep in mind when desiring human interactions mediated by technology, but let’s focus a moment on the last part of it. Technology. Where is it in all this? It is not the focus of everything, <strong>tech is just an enabler to reach the best experience ever. It is never the starting point of anything when designing something, it’s more the arrival</strong>. We can find a completely different scenario if we look at a research lab of an IT company. They start from technology and try to find a use for it. For us is the other way around. We design the experience, and then we use technology to make that vision come true.</p><p>But let’s go a little bit deeper with some real examples of human interaction Sketchin designed in the last few years.</p><h4><a href="https://www.sketchin.com/project/sky-wifi/">Sky Wi-Fi</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uMtuP90r3ieqv0dxedk0sg.jpeg" /><figcaption>Yes, he’s the testimonial for Sky Wi-Fi. Click on the title to take a deeper look.</figcaption></figure><p>I was personally involved in the project for almost 17 months, we designed the customer journeys of the whole experience of adopting a new internet fibre provider, and we managed to design all the small details of it. The project took a few years, and in that period, we barely designed any interfaces (no Figma involved here apart from designing flows).</p><h4>D-Marin</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*Xf4arJ2zg08AobC_EQawaQ@2x.png" /><figcaption>In the picture is one of the marinas where the project took place. Click on the title to take a deeper look</figcaption></figure><p>During the last year, we completely re-designed the experience of 10 different marinas in the Mediterranean Sea, starting with how the staff has to behave on a new arrival till new services and digital assets are launched to support the desired experience.</p><h4><a href="https://www.sketchin.com/project/silversea-silver-origin-galapagos/">Silversea</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gSpJI1VXiYU4F3K-VtFslQ.png" /><figcaption>We designed both the led screen and the content. Click on the title to take a deeper look.</figcaption></figure><p>In a complex project that involved Sketchin for many months, we designed a completely new way of living a luxury cruise through the use of a huge led display onboard the ship.</p><h3>The IX designer to be</h3><p>I just described a world of interaction in which apps aren’t anymore the core of it, some skills (prototyping a digital asset) would be less useful, and others will become more and more important. Let’s dig into how I think an interaction designer to be should be for designing this kind of experience.</p><h4>h/m shape</h4><p>Do you remember the old T-shape designer? Well, forget about it. Being vertical in one single discipline isn’t enough anymore. Welcome to the h-shape designer or to the even more complex m-shape designer that is <strong>vertical in two or three disciplines and horizontal in the rest of them</strong>. If you are asking yourself if adding more and more verticalities to the skills will flatter everything, you are not the only one. We’ll see.</p><h4>Curious</h4><p>This is a close call with “common sense” I talked about before for the most obvious statement (promise won’t be the last one) but to design human interactions, we have to be curious, challenge every statement, and <strong>not give anything for granted and always dig in every hypothesis</strong>.</p><h4>Empathic</h4><p>This is crucial when we design how two persons interact with each other. If we are the best designer ever to prototype an animation in Principle, maybe we can also be zero empathic, and that’s ok, but if we want to imagine how the user will interact with the delivery guy, we need to put ourselves in their shoes. Be aware that<strong> this is far from just using our own experiences to design something</strong> (btw this is the worst mistake a design could ever make), but it’s more about trying to think as our users.</p><h4>Systemic approach</h4><p>The interaction designer has to be able to talk about the small detail and the context at the same time without any problem.</p><p>So, IX design is changing nowadays, much more than visual or service design is doing, and so we must change as well along our discipline. We need to be able to work at different scales of design. On a scale that goes from the small interaction to the overall context of the project passing through the moment in which the interaction is taken and the service itself, we need to be able to work on each scale without any problem. Even more complex, we have to go from one scale to the opposite one in a few because the interaction tells us what the user is doing, but the context answers another question. Why the user is doing that interaction? <strong>In a world made of multimodal interactions, we have to switch scales constantly.</strong></p><blockquote>The interaction tell us what the user is doing but the context answers to another question.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*ZV3joEX5nUAmBDMkFlWvKg.gif" /></figure><h3>What’s our goal?</h3><p>I’d like to quote Mark Rolston again, “<strong>The future of computing is less about building a new world in the computer and more about adapting the computer to our world”</strong>. We shouldn’t forget that our goal is not to design a digital experience for the sake of it but more about designing the best experience the user can live. This is true from the metaverse to the food delivery service. In the end, we’re always talking about connections between humans and not computers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc4971434178" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sketchin/interaction-design-is-everywhere-dc4971434178">Interaction design is everywhere. How to design human interactions mediated by technology</a> was originally published in <a href="https://medium.com/sketchin">Moving forward</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 things I learned designing in UAE]]></title>
            <link>https://medium.com/design-bootcamp/5-things-i-learned-designing-in-uae-930e9e2b406a?source=rss-ff4b9d4d6203------2</link>
            <guid isPermaLink="false">https://medium.com/p/930e9e2b406a</guid>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[uae]]></category>
            <dc:creator><![CDATA[Alberto Andreetto]]></dc:creator>
            <pubDate>Tue, 26 Oct 2021 19:28:24 GMT</pubDate>
            <atom:updated>2021-10-28T00:57:02.249Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>I spent one month running a research design project in Dubai, these are my thoughts and learnings or how to plan and manage a design project far from your usual environment.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*78tX2dmCWrmCv5lLHTxY_A.jpeg" /></figure><p>On December 2020 I went for a month to Dubai to run a research project for a client of Sketchin. The client is a world leader tech brand that is in need of understanding how the brand is perceived in different countries across EMEA.</p><p>That’s why I flew to Dubai, UAE was one of the first country in which we did this research study. I had 4 weeks to plan my trip there during a pandemic, make 10 1to1 user interviews, conduct 9 mystery shop across 7 retailers in malls, analyse 5 different online stores and unbox 4 devices and test them. To remotely help me while I was in Dubai there was <a href="https://www.linkedin.com/in/sachasergi/">Sacha</a>, a colleague of mine from Milan.</p><p>Those are few things I learned on the way</p><h3>1 — Find a local design agency to help you with recruitment.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dkq3nO5IQs8YW1vfSiRJuQ.jpeg" /><figcaption>The room I did run the interviews in Dubai</figcaption></figure><p>Recruiting users sometimes can be a pain, but thanks god Google is my friend. I found few different design agencies before even leaving my country. I contact them asking if they could make the job within my deadlines and asking for a quotation. Some of them answered and I went for the smallest and quicker one. I looked for them on linkedin, stalked the founders, compared the economics and then I chose them. Usually an agency needs from 3 to 7 days to provide you with the first user to interview so always remember to start with this asap if you want to make the interview inside your deadline. I always choose small local agencies instead of big ones because they know better the territory and they can help you out with a lot of stuff (no shows, scheduling interviews, nda…) without many problems and without asking you a fee for everything. This one also gave me one room to conduct the interviews for a really reasonable price.</p><h3>2 — Forget about interviewing people in stores</h3><p>As designers we are used to stop people on streets to ask them questions, to offer them a coffee at Starbucks for testing an interface and to ask them few questions about something they are buying in a store. Ok, this is not something you can do in UAE. Depending on your target you could make it with few users or not at all. If you need emirati people just forget about it, you can’t just stop them to ask questions, they will never answer you and security in a mall will stop you in a few.</p><h3>3 — Don’t think you can just walk around in stores</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vFCOe7gdbwEovQdRe5rH6g.jpeg" /><figcaption>Yellow shirt = clerks. How many of them you see?</figcaption></figure><p>Something you’ll understand in a few as soon as you’ll get into a store in UAE is that clerk wise the situation is really on another level compared to Europe. I’m not exaggerating if I say that the ration between Europe and UAE for clerks is 1 to 7. It’s barely impossible to just walk around the store as you’d do in Europe without being stopped by a clerk every 30 seconds, so if your plan is to do some shadowing and take a look at the behaviour of users in the store just forget about it, doesn’t work.</p><h3>4 — Run your own mystery shop</h3><p>If you need info and there is nobody you can interview you have to take care of it yourself, so just deal with it and run as many mystery shop as you can. Go in stores and pretend you are the customer, you can get really a lot of insights. If you need to share those insights with someone you can put one airpod on and call your colleague, doing this you can share your experience and let somebody else take notes.</p><h3>5 — UAE means expat for 95% of people</h3><p>If you need to interview users in UAE remember that 95% of people are expat and 60% of them are people form Asia that actually are there only to be involved in the construction industry. So your users will mostly be European or American users. Recruit native Emirates is barely impossible, they are really a few compared to the others and they don’t really need your 100 euro Amazon voucher.</p><p>Thanks for reading, if you are interested in something i spoke about just reach me out here on LinkedIn.</p><p>Bonus pic, Sacha and me posing for a selfie before an interview.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tQ7MnfHc12vZ1eW3Wd4IuQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=930e9e2b406a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/5-things-i-learned-designing-in-uae-930e9e2b406a">5 things I learned designing in UAE</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How my design background helped me to raise 25K euro in 2 weeks for Covid-19]]></title>
            <link>https://medium.com/sketchin/how-my-design-background-helped-me-to-raise-25k-euro-in-2-weeks-for-covid-19-e9ccc99497c0?source=rss-ff4b9d4d6203------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9ccc99497c0</guid>
            <category><![CDATA[coronavirus]]></category>
            <category><![CDATA[volunteering]]></category>
            <category><![CDATA[helping-others]]></category>
            <dc:creator><![CDATA[Alberto Andreetto]]></dc:creator>
            <pubDate>Sat, 02 May 2020 21:09:38 GMT</pubDate>
            <atom:updated>2021-10-15T06:58:39.555Z</atom:updated>
            <content:encoded><![CDATA[<h3>How my design background helped me to raise 25K euro in 2 weeks for Covid-19 / 2021 update</h3><blockquote>I gave a talk about this topic at <a href="https://medium.com/u/b8297ccacea0">Talent Garden</a>, if you wanna skip the reading part and just listen to it scroll to the end of the post.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BVxOf_zPKtBiPEc8cWWM8g.jpeg" /></figure><p>I’m a designer, I’ve nothing to do with charity and NGO but somehow by mistake in 2 weeks I raised 25k euro and I helped out few hundreds families, here I’ll explain how I managed this.</p><p>Before getting into details I just wanna give a brief overview of how’s going on in <a href="https://enricotedoldi.it/covid-19-data/">Italy</a> (great website about Covid numbers in Italy coded by my colleague Enrico). I live in Milan, my region is Lombardy, we’re in complete lock down since beginning of March, everything is closed, we can go outside only for grocery shopping or emergency. We cannot go out for a walk, for meeting friends or anything else. Bars and restaurants are closed, shops too. Today is my 42nd day of quarantine. I work remotely so I’m a lucky one but a lot of friends lost their jobs and many people gets trapped in a city they don’t know without a job.</p><blockquote>Many people gets trapped in a city they don’t know without a job.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Bk0Lv8b9TdvqZIh0Le16A.png" /><figcaption>My first post, then updated with the google form</figcaption></figure><p>I live in an area of Milan called NOLO (North of Loreto) and few weeks ago I wrote a post on the Nolo Facebook page (10k members) <strong>“Hey I’m lucky, I still have a job and if you cannot afford a grocery shopping just text me and I’ll do it for you”</strong>. The idea was simple, I just wanted to give a grocery shopping to a family that lost everything with this quarantine.</p><p>Unfortunately nobody answered my post, I guess the public shaming is too much, expose yourself asking for help to a stranger is not easy. Actually I got the opposite, around 15 people wrote me to give me some money. They wanted to help me out with the shopping bill. Late that evening I edited the post stating that I was not looking for money but I was looking to someone to give my money.</p><blockquote>Solidarity is not giving what u have leftover but giving what u lack of.</blockquote><p>It was a Saturday evening and I went to bed thinking about this. Why so many people wrote me to contribute on my shopping? Why they don’t just donate something to one of the many organisation that operate in the area? The day after I realised something, <strong>I used my post as a kickstarter campaign, I posted an idea and I saw that many people were interested in the same, I validated it</strong>. Unfortunately the public shaming of asking a stranger direct help was too much and nobody answered my post asking for a grocery shopping.</p><p>I did what I ask the client I work for to do, <strong>I escalated in a lean way</strong>. I created a simple google form with 3 options:</p><ul><li>I need food</li><li>I want to bring a grocery shopping to someone</li><li>I just want to contribute to a grocery shopping</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*vTkSvA5S3HMsSr3Mv_Rw0Q.gif" /><figcaption>The google form</figcaption></figure><p>I contacted the administrator of the Facebook page, Daniele. I never met him but I saw him managing the page, approving post, kicking out assholes and I thought would have been a good idea to have someone trusted by the community involved in this thing. He agreed to help me out and he posted the form in the page on a Tuesday morning. <strong>By the end of the day we had 100 people filling the form, some asking for help and the rest split by carriers and donors.</strong></p><p>Basically we started matching the people based on location, I was sending the contacts of someone in need of help to someone willing to bring them a grocery, <strong>I let them contact the family in need of help, my goal was only to put those 2 in contact</strong>, nothing more.</p><blockquote>There are 3 kind of poverty: economic, relational and cultural.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0bBgM4td7yY0Ge3d_l5rUw.jpeg" /></figure><p>Before going on I wanna explain the purpose behind this method. <strong>There are 3 kind of poverty: economic, relational and cultural</strong>. The first one is the kind of poverty we can have if we lose our job, it’s the easiest to explain and easiest to fix. But luckily me and probably who is reading this post are not gonna become poor if we lose our job. This is because I’m not having relational poverty and cultural poverty. If I lose my job I’ve a degree and skills I can use to find another one (opposite of cultural poverty) and I’ve a network of friends and family that are willing to help me (opposite of relational poverty). Many people in my area are suffering of the other two kind of poverty, so when they lose the job because of Covid they are gonna became poor in a few. <strong>This initiative I created aim to fill the gap in the relational poverty before than the economic one, a grocery shopping is not going to fix anything in your life but maybe connection with someone living next to you will.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U36L0v0jGpCHW4o_whmxGQ.png" /></figure><blockquote>A free shopping is not gonna fix anything, a friend maybe yes</blockquote><p>After the first week we already had hundreds of people asking for help and many others offering money and groceries. I contacted a couple of no profit organisation and I started doing grocery shopping for them with the money I raised. This is a pretty manual job, I contact one by one the people that wanted to donate money and I ask them to send me via PayPal or bank transfer and then I go to the supermarket with the organisation to make 1K grocery shopping every time. Then they distribute this food to a network of families they know.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JbqYXurAmelUtld4c-0z2A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SRExZkZOB1NoDF8nxWBMKg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MZD4kEspF_aBx-l741kKhw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6csp3YN8pmFoD6NoO-T_vg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M-CmRBChvv4izsBnAcxb_g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OESKAEquR1bitg34cxv1ag.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DKh1gtvJzLIo6ULvJPdKYg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kYpKtlHweZPaP0B-A4AGTw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eSx_H1dWCKzy6fN7QH_DQw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AfqIiWoM5scd1JOMmnGMmQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IVWEQ9J46kBq4d0IIUnk4Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BVxOf_zPKtBiPEc8cWWM8g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O3rQGMnDDMZcXkMrVeX3eg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T2Ek5XxR5RgagvDGdnlBug.jpeg" /><figcaption>How 1k grocery shopping looks like</figcaption></figure><p>After 2 weeks our google form exploded, we had nearly one thousand entry and many of them from other areas of Milan we could not go due to the quarantine. Luckily Francesco and Mattia, 2 friends of mine living in Madrid, Ilenia, friend of mine living in Munich and Angela ex colleague living in my area helped me out in bringing this to the next level. In one weekend we all together created a brand identity, a web page and a backend platform to managed all this. This was a huge improvement due to many reasons:</p><ul><li>The page checked the postal codes, we decided which ones to allow so we cut out all the other areas of Milan</li><li>The backend put in real time carriers and receiver on a map, letting us to match them directly</li><li>The logo it’s fucking beautiful (thanks Angela)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Id99m2CvPWocrK1i0BVGsw.png" /><figcaption>frontend of the page, illustrations from undraw.co</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dJTdpB3QlerJ9Bjgwwkt1Q.png" /><figcaption>Blue pin = I need help | Red pin = I wanna bring a grocery</figcaption></figure><p><strong>So far we matched more than 250 people, some of them living in the same building.</strong> We matched parents of same classroom kid, neighbours and people that are still in contact after one month. <strong>We did grocery shopping for associations for 8k euro and we are still matching people in those days.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zgvhTDJuF_09wPW-DE_l7A.png" /><figcaption>Just some of the 250 grocery shopping that people did</figcaption></figure><p>There are so many things I could tell about this, but right now I just want to push this out, probably I’ll write again on this and I’ll update this post.</p><h3>Update 2021</h3><p>Some time has passed since I wrote this post and i just want to publish some updates.</p><p>Daniele and I stopped this service when the first lockdown ended in June 2020, it was too stressful for us to keep on managing this as a side thing, I just wanted to help one family, I ended up helping hundreds of them. I was happy of the result.</p><p>Then in September 2020 Davide Fassi, a teacher at Politecnico di Milano contacted me. The message was like this:</p><blockquote>“Hey Alberto, as Politecnico di Milano we have an off campus in Nolo and we’d like to take over SpesaSospesa”</blockquote><p>I know Davide and i was excited about this idea so we met few times, we changed a little bit the service (now local stores are involved as well so we help people looking for food and local stores too) and they started a new version of SpesaSospesa.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DQ-voeLznuLXCJqY7nBD6A.jpeg" /><figcaption>Davide at the inauguration of OFF CAMPUS NOLO</figcaption></figure><p>Now they provide 20 grocery shopping per week to 20 families, they have to register on the same platform and Polimi staff just manage to contact contributors and reveicers.</p><p><strong>More than one year ago I started SpesaSospesa and i think now it’s time to give some numbers.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M-vc9dh0YYMyETjjGj1xqw.png" /></figure><p>Roughly 2000 families received a grocery shopping with SpesaSospesa, this is a number that takes in account all the different ways of giving one we had in the service so far (people bringing one, NGOs and associations, new service with Polimi).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LLDsliA9_1jcMUPTIcXeMw.png" /></figure><p>This is also an estimate value of how much we spent for groceries since the start, this takes in account the money that i personally spent for associations, the ones that people used for grocery shopping and the one used by Polimi.</p><p>And then one day <strong>I got an email from Beppe Sala, major of Milan</strong> that was thanking us, Life achievements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7_u87UlzakGeNAO8uYSKqQ.png" /></figure><p>At the end of the project I realised that there are some lessons that i learnt from a designer point of view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i43cYhS2DICw0o_fx-yjBg.png" /></figure><p>As designers we push our clients to use an agile incremental approach, now i know that it works. <strong>Doesn’t mean less effort but better results</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q8Y_6p0sZwAXuqLQDGbAhw.png" /></figure><p>Doesn’t matter how many empathy maps, user journey, personas we do. Getting in touch with the user is different, getting messages of people that are starving l<strong>et you see them in a completely different way</strong>. We should always remember that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*917GI8IOOT5Xxyh1NzKKhA.png" /></figure><p>Your service will work with or without all the terrific features that you dream the night. <strong>If the idea is good users will engage with it </strong>no matter if you have a super cool logo or just a name on a Google form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D7kwxrXlTPsgVc835JeC5Q.png" /></figure><p>If you cut the intermediate man you’ll get people more involved. <strong>They like to put their hands on</strong> something, leverage this and create a partecipative service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cfHYysHSpIrJs8j4KrlDRw.png" /></figure><p>We have powerful skills, we can change things to a lot of people. More than management or developers, <strong>we can shape services that have impacts on everyday life</strong>. Remember this next time you create a 20m long CJ that nobody will ever use.</p><p>Last week I gave a talk about this in an event for <a href="https://medium.com/u/b8297ccacea0">Talent Garden</a>, if you wanna take a look here is the video.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FzZRy4WWZ78g%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DzZRy4WWZ78g&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FzZRy4WWZ78g%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ca891dea1b59d9b84d3cd935136d3e05/href">https://medium.com/media/ca891dea1b59d9b84d3cd935136d3e05/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9ccc99497c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sketchin/how-my-design-background-helped-me-to-raise-25k-euro-in-2-weeks-for-covid-19-e9ccc99497c0">How my design background helped me to raise 25K euro in 2 weeks for Covid-19</a> was originally published in <a href="https://medium.com/sketchin">Moving forward</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 reasons why I love design flows + pictures (service blueprint, customer journey, cx flows…)]]></title>
            <link>https://medium.com/@aandreetto/5-reasons-why-i-love-design-flows-pictures-service-blueprint-customer-journey-cx-flows-dcd2485e745d?source=rss-ff4b9d4d6203------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcd2485e745d</guid>
            <category><![CDATA[customer-journey]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[blueprint]]></category>
            <dc:creator><![CDATA[Alberto Andreetto]]></dc:creator>
            <pubDate>Sun, 29 Dec 2019 20:29:11 GMT</pubDate>
            <atom:updated>2019-12-29T20:29:11.177Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i01LFUgWNXRJlFJc9mXaLw.jpeg" /><figcaption>This is Beatrice (colleague of mine) with the CJ we designed for Allianz Bank</figcaption></figure><p>I studied industrial design, how to design chairs, tables or electronic products, or like Rogers said back in the 1952 “from the spoon to the town”. Ho I ended up designing maps is not so clear even to me but here I am so I’m trying to explain what I like about what I do.</p><p>First of all let’s make clear what I mean with maps. If you are a designer you can skip this small paragraph knowing that I mean Service Blueprints, if you are not I’ll explain it in few words. When designing a service we design the experience the user will have, we design the ideal path (where everything goes ok) and also all the bad path (everything that can go wrong and how to fix it). In order to make it clear to every stakeholder this experience is mapped so everyone can agree on how it’ll be. Sometimes under this experience flow there are also some backend processes (the systems that let the user have the experience) mapped or some fronted or other stuff. In general we’re talking about long flow with every step the user can do in the use of the product/service.</p><h3>1 — make everything clear</h3><p>Designing a customer journey, a service blueprint or a customer experience flow makes clear to everybody what is going to happen to the user. In every company but especially in the big corps there are many meetings in which no one wants to take responsibility of anything, so you keep talking about the service you are designing for 2 hours and at the end nothing is left. No decision has been taken and you are exactly where you were before the meeting, except that everyone in the room think that you are ok with the information you got. Having a big canvas and being able to spot the experience point to discuss makes everything easier for everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cgREyR6O6oF4KcYRb9gyog.jpeg" /><figcaption>a design review I did on a User Flow we designed for Sky in 2019, more than 100 corrections to make</figcaption></figure><h3>2 — spot the pain points</h3><p>When you design a big service usually there are different areas involved and different level of stakeholders. I usually map the pain points in red on the flow. This let me highlight them and being able to tell to every stakeholder “hey this is a problem, what can we do about it? Who can decide?”. This is useful a lot if you are talking to the management, let them understand how many open points are still in the flow will make your job a lot easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D6LRQVRGdBrVcuXYm1M_VA.jpeg" /><figcaption>user flow I designed for an instalments card, you can read more about this <a href="https://medium.com/sketchin/from-branding-to-interaction-a-fintech-end-to-end-project-in-sketchin-549f0046311a">here</a></figcaption></figure><h3>3 — connect the dots</h3><p>Designing a service is not easy and as I said before, usually, a lot of different areas in the company are involved. Each of them take care of his own part and the job of the designer is to be sure that everything match in the big picture. Many times I found myself in the situation in which one department told me something that is completely the opposite of another one. Having a map of the experience lets you talk with them in order to design something that converge instead of something that diverge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8GFDk_8YGnbez69fofAkMQ.jpeg" /><figcaption>beatrice pointing out something on a blueprint in Sky, mapping is a collaborative process.</figcaption></figure><h3>4 — single point of truth</h3><p>Let’s talk about how beautiful is to go to a meeting and being the one that have the truth. If it’s written on the map it’s true and everyone will act at their best to make it happen. No one can say that did not understand because it’s written there and no one can change their mind from one meeting to the other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qPE3NurebIsVvhvE3rHCOg.jpeg" /><figcaption>sketches for a blueprint I designed this summer in Sogei for “lotteria degli scontrini” that will be live next year</figcaption></figure><h3>5 — explain the unexplainable</h3><p>Visualising a service is something really difficult to imagine and creating a customer journey is the way I use to make real something that is just a story. Usually the client has a lot of problems in explaining to every stakeholder how the service will be, a map will help them to do it and will help who will come after you to make a screen flow or an interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jXKgTPZ63iKCA0mJQ2csJg.jpeg" /><figcaption>early stage of a blueprint I designed for Enel back in 2017</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcd2485e745d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing in Angola — thoughts and instastories.]]></title>
            <link>https://medium.com/@aandreetto/designing-in-angola-thoughts-and-instastories-de7c130b035f?source=rss-ff4b9d4d6203------2</link>
            <guid isPermaLink="false">https://medium.com/p/de7c130b035f</guid>
            <category><![CDATA[oil]]></category>
            <category><![CDATA[interfaces]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[angola]]></category>
            <category><![CDATA[luanda]]></category>
            <dc:creator><![CDATA[Alberto Andreetto]]></dc:creator>
            <pubDate>Sun, 13 Oct 2019 20:23:56 GMT</pubDate>
            <atom:updated>2019-11-13T15:22:21.804Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Designing in Luanda, 2017 most expensive city in the world — thoughts and instastories.</strong></h3><p>How I ended up designing a dashboard in Luanda, <a href="https://www.mercer.com/newsroom/mercers-25th-annual-cost-of-living-survey-finds-cities-in-asia-most-expensive-locations-for-employees-working-abroad.html">the most expensive city in the world for expat in</a> 2017 and few thoughts about what I saw there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LYGcWI076W6NgugLnoQqIw.png" /><figcaption>Dashboard sketch file</figcaption></figure><h3>Designing a dashboard to monitor an FPSO</h3><p>Recently I had the chance to follow a design project in Africa. Every colleague and every friend is asking me how it was, I write this hoping to answer to all the questions I got in the past months. I’ll explain a little bit of the project and I’ll also cover other aspects that I found interesting.</p><p>June 2019, I got an email in my inbox from a colleague “hi everybody, we got an interaction design project in Angola, anyone willing to do it?”. I immediately answered I was.</p><p>The project was simple, based in Luanda, follow as an interaction designer a design sprint for an important Italian energy player. The energy company I worked for is one of the main energy supplier player in Italy and worldwide. They have oil wells in Angola and in many other parts of the world, the project consisted in designing a dashboard to monitor a FPSO that is front of Angola, in the middle of Atlantic Ocean.</p><p>At this point you are ask yourself what is a FPSO, and you’re right. Actually I had no clue about it before starting working with them. Basically a FPSO is a boat that act the same as an offshore platform for oil extraction. When the extraction point is too deep, when the oil field will last not enough or when is not profitable to build a pipe system that brings the oil to the land, instead of an offshore platform you can put there an FPSO. Basically a huge boat that sucks the oil and store it waiting for a tanker to empty it’s tanks. It can stay even 10 years or more in the same place, until there is no more oil.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q94Z1iItWFCVW3_iYipIcA.jpeg" /><figcaption>A picture of an FPSO. Yea it’s huge.</figcaption></figure><p>The team there was composed by:</p><ul><li>Me</li><li>Italian energy company employees</li><li>Angola energy company employees</li><li>FPSO employees</li></ul><p>The FPSO in this project was rented by the Italian energy company from a company that has several ones. Unfortunately I couldn’t visit the FPSO, by boat it’s a 7 hours trip, to take an helicopter you need to attend a 5 days class about flight security and most of all was not planned.</p><h3>Quick talk about design</h3><p>In 4 weeks we designed a dashboard that can monitor every kpi of the FPSO that the team thought useful to keep an eye on. I had some references from a project they previously run in Indonesia but I had the freedom to suggest improvements both from a visual and an interaction point of view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*8uK4ZCY_KRomySekxvdWfw.gif" /><figcaption>Almost 800 commits in 3 weeks in Abstract by me and my teammate</figcaption></figure><p>I won’t go too deep into the design decision I took for this project but I’ll post here some screenshot about the dashboard itself. I used sketch to build both the project file and the library and Abstract to manage the workflow. Unfortunately I can’t post something too detailed so here there are some screenshot about my sketch file that at least will let you understand how I organized it and how many screen I had to design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sx6AWvOldv7amn68FykTXA.png" /><figcaption>I had 12 pages in the sketch file, here one of them</figcaption></figure><p>Then with InVision I gave them a pretty accurate prototype of the platform. Since the interface was going to be coded in Appian, I had a daily call with an Appian engineer to test the feasibility of our decisions. As a designer this is an usual constrain, I always have to design an interface keeping in mind how hard to code will be and how much is the budget to code it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*O63r0EPed9T5c93tH33KDQ.gif" /><figcaption>The library I created for this project</figcaption></figure><p>The overall project was design sprint based. Two service designers helped in the first 2 sprints to assess the desiderata and to break down the ideas generated into cards. Each card had a PO (from the Italian team) that took care of refining it with the local team. I interacted both with the POs and the local teams in order to translate the card into an interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oblOU3aaBf88eW0TuFhWuw.jpeg" /><figcaption>Some sketches I did for the interface</figcaption></figure><p>In total I designed around 95 screens and countless interactions, for this project I didn&#39;t used Craft Prototype but if I look back now probably would have been better to use it. I really don’t like going on InVision and fix every hotspot manually, it takes a lot of effort to build it and most of all to mantain those links.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*_72dIPP8h1xs_c8sMYIejg.gif" /><figcaption>All screens in loop, enjoy</figcaption></figure><h3>Some thoughts about Luanda</h3><p>Moving from the design part to the social one I can just tell you about Luanda for what I saw. An expat living there for few weeks. I have for sure a huge bias but anyhow this is my point of view and it’s the only one I’ve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/337/1*MXPE9bm_hYolgD6Ka2PSDA.gif" /><figcaption>Streets of Luanda by night</figcaption></figure><p>Luanda in 2017 was still the most expensive city in the world for expat. Like many countries in the world they have a lot of oil but they still are a poor country. I believe this happens when the oil is not used to build a sustainable economy or when it’s not used to build the foundation of the “country to be”. Oil is not forever, is definitely the present but is not for sure the future and most of all oil price is volatile. In 2010 oil price was 150$ for barrel but in 2016 it had a drop till 36$. If you plan all your economy on it it’s a huge problem. Angola is not the only country that had problems with this, Venezuela had the same pattern, an economy fully based on oil till the price drop.</p><p>One of the tangibile effect of this drop are skyscrapers, when the oil price dropped time stopped in the same moment. Simply, building something was not profitable anymore, the result is a lot of unfinished skyscrapers in Luanda waiting for a spike in oil price to start build again.</p><blockquote>If you want to dig into this here the link you are looking for</blockquote><blockquote><a href="https://www.weforum.org/agenda/2015/06/why-is-angolas-capital-the-most-expensive-city-in-the-world/">https://www.weforum.org/agenda/2015/06/why-is-angolas-capital-the-most-expensive-city-in-the-world/</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HGxnzqS8t2YjKcHWKe92vg.png" /></figure><p>But how can a country with a GDP of 7700$ per year host the most expensive city in the world? Short answer is that after a 27 years civil war, in 2002, Angola had the chance to rebuild everything from scratch, with a lot of oil the country had a growth of 23% over year but with almost no infrastructure is really difficult to balance this growth. No highway to bring goods, no houses for expat and so on. This tells why a 3 room apartment in Luanda costs almost 10K per month, simply there aren’t enough and bring stuff there is extremely expensive.</p><p>Right now Luanda is not anymore the most expensive city in the world even if its prices are still pretty high. Average Angolan daily income is around 2$, but for a dinner you can spend 70$ without going too fancy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/338/1*ndkpmtMzwBAFox9f6htOxQ.gif" /><figcaption>Luanda’s nightlife</figcaption></figure><p>This tells you pretty much everything about Angola. There are 2 different countries within the same one, a country for Angolan people and another one for expat and rich Angolan. In general Luanda is not so dangerous but there is a huge problem of micro criminality and if you are white is easy to be recognize as an expat. Since tourism almost doesn’t exist is really difficult to see somebody with Caucasian traits in the street. I wasn’t allowed to walk down the streets for example and I always had a driver to go everywhere I wanted to, this was really frustrating since I always like to dig into the culture of the country I’m in but being there as an employee of the energy company have some security constraints that I can definitely understand.</p><h3>Let’s talk about money</h3><p>This is not what you are thinking about, we’re not talking about salary or income, we’re really talking about cash, Kwanza cash (Angolan currency). One of the most difficult things to do in Angola is get money. Basically most of European credit cards don’t work, or just work in few expat places, so you need cash, a lot of cash.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jsjWHipl3KMlLerfLFsfAA.jpeg" /><figcaption>200 Euros in Kwanza, I felt like Mayweather</figcaption></figure><p>A dinner can easily cost 50 times the daily income of an average Angolan person. This means that if you have to pay a bill at the restaurant, the amount of banknotes you need is huge and getting them is not so easy. If you live in Angola and you need to visit Europe or US you need cash but find a bank in Angola that can provide you Euros or Dollars is quite impossible. This is the assumption that moves bills around Luanda. You, as an expat that brings Euros into the country, provide Euros to Angolan people that need them to travel in Europe and they gives you back Kwanza. It’s quite a win-win solution and the result is that for 200 Euros you get back a lot of banknotes as you can see in the pic.</p><p>I’m telling this because i think it’s a simple message that can deliver another meaning. It’s weird to be in a place where you need this amount of bills to pay a dinner, it’s something you can see with your eyes, it’s the result of that crazy economy in front of you. You can feel that things works in a different way there, you can tell this right outside the airport arrival hall, where the only thing you see are men with oil companies sign. But all those feelings comes to something you can touch when you get the bill at the restaurant and you understand they don’t have banknotes with enough value because usually they don’t need them, you are living on a parallel country.</p><p>Unfortunately I had no chance to visit the rest of Angola, I saw the capital and biggest city in the country and I had the feeling that the environment I saw was artificial compared to the rest of the country.</p><p>I gave my best to explain how it feels like being there, if you have any question about the design project or life in Luanda feel free to reach me out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de7c130b035f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s behind Cambridge Analytica and how ethic deals with design]]></title>
            <link>https://medium.com/@aandreetto/whats-behind-cambridge-analytica-and-how-ethic-deals-with-design-e0800cc2b2bc?source=rss-ff4b9d4d6203------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0800cc2b2bc</guid>
            <category><![CDATA[design-ethics]]></category>
            <category><![CDATA[cambridge-analytica]]></category>
            <category><![CDATA[interaction-design]]></category>
            <dc:creator><![CDATA[Alberto Andreetto]]></dc:creator>
            <pubDate>Tue, 02 Jul 2019 19:33:04 GMT</pubDate>
            <atom:updated>2020-03-11T14:38:52.763Z</atom:updated>
            <content:encoded><![CDATA[<h4>How I designed a page that was used to collect 400 millions Facebook profiles and some thoughts about ethic in design.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ht5EdSBYemxzUIY01lHxFQ.jpeg" /><figcaption>Mark facing the congress about Cambridge Analytica</figcaption></figure><p>I took a very long time thinking about this article, thinking about a professional experience I had back in 2015 and how this impacted the world few years later. It’s not easy to write down the whole story but I think this could be a starting point to evolve the idea of us as designers.</p><p>Given how ramified and overreaching are the facts and how narrow my involvement was, I won’t be able to explain every detail of the story in this article. .I will therefore include a number of links pointing to sources written by people that knows the story better than me and that already documented and explained it. If you want to deep dive into the facts you can read more about it on newspapers and other sources. Here I just wanted to give a context to what happened.</p><p>I graduated in 2010 as Industrial designer, I worked few years in an architectural studio designing products and interiors, then in 2012 I joined a startup as interaction designer. My job was simple, I had to design the company web tool that customers could use to surf their data. This is a perfect job for an interaction designer, you have a set of data and you need to design something that will let other people slice and read those data.</p><blockquote>Data are not good or bad, they are just data.</blockquote><p>Data. I’m gonna use a lot this word here. Data are everything, and what I learned over time is that data are not good or bad, they are just data. It is the way you use data, that may change their nature. The data I was designing an interface for, were simple personal data coming from a Facebook app. If you have no clue about what a Facebook app is don’t worry, I’ve got you covered: every time you use the “Facebook login” function you are basically giving authorisation to an app to check your profile and get some of your data. The data the app has access to are normally describe on the app’s access page and/or in a data protection notice but, needless to say, no one ever reads the small print.</p><p>Let’s recap. The company A was asking my employer to create a Facebook app to set up a contest using the “Facebook login” function. People were logging in to attend the contest and my employer was collecting their data, presenting them via a web tool to the company A that after the contest could slice and analyse those data. Typically our clients used my employer’s services to get better insights into their customers: their age, where they were coming from, their preferred singer and other information that can be gathered from all the public data that you usually put on Facebook.</p><h4>How did I ended up designing a page for Cambridge University</h4><p>Then one day my company stumbles upon a website. The website was simple and really ugly but was introducing a mind blowing concept. You could login in via Facebook and, based on your likes, you could get an automated personality test summarizing your psychological traits based on a “five factor model” (which measures five key personality traits such as openness, extrovertion, conscientiousness, etc. You can read more <a href="https://www.123test.com/big-five-personality-theory/">here</a>.</p><p>That page was build by <a href="https://www.psychometrics.cam.ac.uk/">Cambridge psychometric center</a>, a research center of the Cambridge University. As part of one of their projects, they ran a survey by asking a pool of around 50K people to submit their Facebook likes and to complete the full “five factor model” personality test. By doing so they gathered, for each participant, all their Facebook likes and the personality test result. They searched for correlations between those 2 sets of data and surprise: they found them!</p><p>Basically they <a href="https://slate.com/technology/2014/10/youarewhatyoulike-find-out-what-algorithms-can-tell-about-you-based-on-your-facebook-account.html">discovered</a> that if you have a large enough set of data (i.e., enough Facebook likes) it’s relatively easy to determine one’s personality based on your Facebook interactions. For example, if you like Lady Gaga you are more likely to be open to new experiences, if you like French Fries you are probably emotionally stable and so on for thousands of likes.</p><p>My employer called this Cambridge psychometric center , explained them what we were doing and we started a collaboration. It was as easy as that: we sent them an email and few weeks later I was designing the new webpage for them. We didn’t ask money and they were happy to have someone helping them with the page. They even let us host the page on our servers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*CiBAbjZJDXqMBaGcfjMpQw.jpeg" /><figcaption>This is how the page looked like, lovely, isn’t it?</figcaption></figure><p>Here comes the tricky part. Our company built the Facebook app that the user had to use to login in order to take the personality test and set all the permission to ask. Of course we asked to see the user’s name, email, city and likes. In addition to asking permissions to see the user’s data, our company also asked users to “let this app see your friends data”. Yes. At that time, Facebook allowed developers to ask a simple permission that let them collect not only user’s data but also all of such user’s friends data (Facebook apparently got rid of this mechanism one year later documentation, although it seems that the system kept on working for another year). Do I think this is a good thing? Probably not, but back then Facebook’s policies were a lot more relaxed as nobody was asking for more privacy, so Facebook let allowed developers to do things and developers didn’t even ask themselves if such things that Facebook allowed were right or not. Facebook decided for the entire industry.</p><blockquote>338 is the average friends number on facebook</blockquote><p>338 is the number you are looking for. 338 is the average friends number on facebook. I think back in the time was quite lower but doesn’t matter. This gives you the right context. With just 1000 people taking the personality test, the Cambridge psychometric center (and the company I was working for) collected data from 338000 Facebook profiles. Needless to say that way more than 1000 people took the personality test, as in fact we collected data from around 300 millions of users, and with them a quite representative sample of all the people on earth. Yes, a sample of all the people on earth, with all data connected to them: age, location, income, job position and most importantly, likes.</p><blockquote>If you are brave enough here there is the 6 hours streaming of Mark Zuckeberg facing the congress.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FGQN4On0K7-w%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DGQN4On0K7-w&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FGQN4On0K7-w%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2bc63fa3527d9de2ee99b9a3ba0948ad/href">https://medium.com/media/2bc63fa3527d9de2ee99b9a3ba0948ad/href</a></iframe><p>The set of data my employer had access to was so large that we were able not only to run analysis on users that accepted the login of our client, but virtually on every human on this planet. It was easy for example to extract all the people that likes a major cola brand and rank the singer they liked, the city they came from, and so on. We could even run a psychometric analysis on those users and figure out if consumers of such cola brand were more open or introvert. We had a sample big enough to do this.</p><p>Long story short: based on the news, one year later Cambridge scientists appear to have sold those data to Cambridge Analytica. You know the rest. It is alleged that CA (or third parties that received data or services from CA) may have used those data in various occasions including in the context of political elections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/346/1*TL9G2T17-fY4HiT-CodAcw.gif" /></figure><p>Here few links if you have no clue what I’m talking about and wanna know more.</p><ul><li><a href="https://www.channel4.com/news/exposed-undercover-secrets-of-donald-trump-data-firm-cambridge-analytica">Exposed: Undercover secrets of Trump&#39;s data firm</a></li><li><a href="https://www.nytimes.com/2018/03/17/us/politics/cambridge-analytica-trump-campaign.html">How Trump Consultants Exploited the Facebook Data of Millions (Published 2018)</a></li></ul><p>If you want to know more about Cambridge algorithm go <a href="https://applymagicsauce.com/">here</a>.</p><h4>Is there any ethic in what we do as designers?</h4><p>Honestly, I don’t think my employer was aware ofwhat was happening and how those data could be used and neither did I, our company just used the data to run simple market research. I never thought about the idea that those data could be used in the context of political elections, as some journalists and investigations argued.</p><p>After some years here I am thinking about what I witnessed and all the choices I made in a small way and how those choices may have changed lives of others. I’m writing this article because I want to go a little deep into the relationship between designers and ethics. I realised that we have way more power that what we think, we are the connection between business and users, we are the ones that decide how a user will interact with a service and we can definitely have a take in that.</p><p>I worked for many clients, and every time something comes to my desk, especially after my experience described above, I always ask myself If I feel comfortable to work for that company. For example, recently <a href="https://medium.com/sketchin/from-branding-to-interaction-a-fintech-end-to-end-project-in-sketchin-549f0046311a">I designed an instalments card</a>. How do I feel about that is really controversial, I know the service is something that could trap people in an infinite level of instalments and debits. On the other side, designing the service I paid a lot of attention to the educational part of it, I designed it keeping in mind that users are not good in managing money. Now in the app there is a main section that show the client how he spent the money in the last month, how he is spending his money now and how he will spend in the future. I also took a lot of time talking with the client explaining why this part was important. Luckily he got it and I think this service now is a little bit better than how could be if I wasn’t involved in the design.</p><blockquote>We are the last protection of the user, our job is to help our client business keeping in mind that we have to protect the user.</blockquote><p>I have a responsibility that comes with my job, i like what my general manager says, we are the last protection of the user, our job is to help our client business keeping in mind that we have to protect the user. This responsibility is not taken in account in a serious way because many time we as designers look like the “creative ones” and people forget that everything the user will see and experience about a brand or a service will be what we designed. It’s easy for us to trick the user or to force them to take a choice or another one.</p><p>I don’t really know if this is just a way to wash my conscious and sleep well or if it’s really the right path to take but somehow thinking that it’s better if I design something instead of somebody else that won’t take in account the user makes me feel better. I’m nervously thinking about the day that a bet website or a political party will arrive on my desk, that moment will be crucial in my career and the choice I’ll take will be probably one of the hardest for me.</p><p>Im not the only one thinking about this kind of stuff, take a look to who took this very seriously.</p><p><a href="https://2017.ind.ie/about/">Ind.ie - About</a></p><p>I don’t wanna speak too much about it because my point is not sure yet, I’d like to know how you deal with this and what your choice would be. Thanks</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0800cc2b2bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From branding to interaction, a fintech end-to-end project in Sketchin]]></title>
            <link>https://medium.com/sketchin/from-branding-to-interaction-a-fintech-end-to-end-project-in-sketchin-549f0046311a?source=rss-ff4b9d4d6203------2</link>
            <guid isPermaLink="false">https://medium.com/p/549f0046311a</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[branding]]></category>
            <dc:creator><![CDATA[Alberto Andreetto]]></dc:creator>
            <pubDate>Wed, 08 Aug 2018 11:14:46 GMT</pubDate>
            <atom:updated>2018-08-10T09:58:34.320Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T_VF19h6-ZPh7zLZKlV5ew.png" /></figure><h4>Sketchin</h4><p>Here I’ll try to explain my first end to end project in Sketchin. I started working here in September 2017 and few months later I got the chance to work on a cool project involving service design, branding and interaction.</p><p>Sketchin is a smart design firm that shapes future experiences, today we’re around 100 people, working in different places around Europe and US, and counting. We work in both big service design project and small interaction ones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mWjhRdGy65PZrjMcyT6eFw.jpeg" /><figcaption>You can see some of us here — June 18</figcaption></figure><p>I’ll describe the experience from our point of view, what we did wrong, what we did right, what was unexpected and the final results, even the ones the client rejected.</p><p>Sketchin is a multidisciplinary studio and we work in teams and pipes. A team is formed by 2 pipes of 2 designers each and an architect that manage the connection with the client and the consistency of the project itself.</p><h4><strong>Brief</strong></h4><p>In late 2017 we’ve been contacted by a group of people that asked us to help them design a new fintech service. They already run a similar service in Russia and they wanted to expand their business in Europe first and South America later.</p><blockquote>The idea is pretty simple, designing an instalment card service that will let the user to buy everything just paying in instalments. The service works on agreements with partners shops. No fees or extra costs for the user.</blockquote><p>The whole project took us exactly 2 months of an interaction designer (me) and a visual designer (<a href="https://www.linkedin.com/in/gabrieledemarindesigner/">Gabriele Demarin</a>).</p><p>Ok, well, I’ll try to explain the service in few words. It took me weeks to get it but I’ll try to transfer all my knowledge to you in just 30 seconds. If you don’t really care about how this stuff works just skip this paragraph, you’ll understand the rest without any problem. (It’s like watching the new Blade Runner without the old one, you get everything)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D3HO5CQTsdl1xHSlpLgnug.jpeg" /><figcaption>The best representation of the service in a sketch we used ourself</figcaption></figure><p>I’ll try to explain this using my friend Rachel. She has a salary of 5 and a limit of 10 (the black triangle is the limit, spoiler, it moves), we’ll take a look about 4 months of use of the service as described in the chart.</p><p>The first month Rachel buys a TV that costs 6 with a 3 months instalments (2 per month) and at the end of the month she pays an instalment of 2, now the limit is 6 because he still has to pay 4.</p><p>The second month with a limit of 6 she spend 4 (green instalment of 4 months) for a n iPad, so during the month her spending capability is reduced to 2 but at the end he pays 3 instalments so she free the limit till 5.</p><p>The third month she spends 5 for a really cool pair of headphones and the limit goes to 0. At the end of the month she pays 4 instalments so the free 4.</p><p>The fourth mont she doesn’t spend anything so from a limit of 4 she goes till 6 because she pays an instalments of 2.</p><p>To sum up, Rachel has a limit (10) and can fill it with as many instalments she wants, every time she pays an instalment the limit become free again of the same amount.</p><h4><strong>Define and understand the experience</strong></h4><p>What I explained in the last paragraph looks pretty simple now. Well, it wasn’t when we started the project, actually took us quite a while to perfectly understand the concept of the service. The first thing we did was to set up a 2 days workshop with the team (from now on the team is the client + us) to understand their idea of the service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qRBytHchtqiM0p18awXrrQ.jpeg" /><figcaption>Visual exploration workshop in Milan — December 17</figcaption></figure><h4><strong>Visual exploration workshop</strong></h4><p>Gab and I got this project and the first thing that came up in our mind was that we didn’t know so much about the service and the context. We didn’t know anything about instalment cards (they are not so common in Europe) but we had a strong knowledge about fintech industry thanks to other projects we had in Sketchin. We had some experiences working with Russian but we didn’t know so much about their visual taste. Well, if you don’t know something there is only one thing you can do, study. We took few days to make a massive research in the industry, we didn’t choose only other instalments card but we opened our research to the whole fintech industry in order to understand the market and the players.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JVzWZMjAERekUhw51D0qKQ.jpeg" /><figcaption>Some of the brands we chose for the Visual Wks — December 17</figcaption></figure><p>We met the team in Milan and in a 2 days workshop we defined with them the visual strategy to follow. We asked them to spot the strength and weakness of every brand we found in order to understand their taste and idea.</p><p>Using other brand as an inspiration we helped them also to figure out the main pillars of the service we were designing, what came out was at the same time simple and so powerful, it helped us a lot to shape the service along with the value proposition that we ask them to write down. It’s always interesting how different people from the same project and team get to different conclusions when you ask them to create something real about their service. Asking them to fill the value proposition without talking to each other helped us to get to one shared idea of the service avoiding misunderstandings and wrong expectations.</p><h4><strong>Customer experience workshop</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NGIKxYj_BZ3UkwtWPum1bw.jpeg" /><figcaption>Creating the AS IS — December 17</figcaption></figure><p>What I explained in the last paragraph took us only one day and we had the team in Milan for another one. At that point we had a clear view of the visual expectations, the pillars of the service and a shared value proposition. What we needed then? Easy, understand how the service works. We knew they had something really similar running already in Russia so we decided to map out that service in order to:</p><ul><li>Understand how the service works, trust me, it’s not easy at all for an European</li><li>Pin out the needs of the user in the as is</li><li>Find out pain points in the flow to create new opportunities to explore</li></ul><h4><strong>Design the experience</strong></h4><p>What we did in the first 2 days workshop helped us to understand and better define what they asked us to design. The pure phase of research now ends to leave the scene to a more operational one.</p><h4><strong>Design strategy</strong></h4><p>Thanks to the insights and design opportunities identified during the previous activities, it has been possible to elaborate a series of guidelines that will be fundamental to:</p><ul><li>build a product / service design strategy and its possible future evolutions;</li><li>validate the design assumptions in order to start the design process.</li></ul><h4><strong>Naming</strong></h4><p>Based on the workshop we had in Milan we investigated different paths in order to come up with names with may backgrounds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0DVag7BxnnZDR6_o2SA_QQ.jpeg" /><figcaption>Gab writing some names on the board — January 18</figcaption></figure><p>We followed 3 main paths, an English one, using English roots to have internationals names. A Russian one, we took words from the Russian world making them more international and recognisable and a Latin one, taking something from the past in order to create unique names.</p><p>Designing a name is not just a matter of creativity. Numbers are involved too. We used an analytic approach in order to explores different paths and to have quick feedbacks on the names we found. On top of this for every names we came up with we run a check about web domain names and brands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_-_z5yaNhgwD1PvXEn-xWg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gP-NfKOD4wE3w0aqcp7gng.jpeg" /><figcaption>First survey with 9 names and 224 votes</figcaption></figure><p>After the first batch of names we collected many feedbacks from the client and we focused of some names creating derived ones and also on few new ones. We came up with 7 new names and a new survey</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T7DA6fSUQH0B-udx-4hutg.jpeg" /><figcaption>Second survey with 7 names and 112 votes</figcaption></figure><p>The client really liked the SOLVO one, they thought was really on point and perfect for the user, but it was too high, too unique and we were worry about being perceived like something not approachable for everyone. So we kept the root and we changed the end, from Solvo to Solvy to be more friendly and catchy.</p><blockquote>SOLVY is the chosen name from the client, friendly and catchy</blockquote><h4><strong>Co-design workshop</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*clBzbQwA2zN1LF0T6XlV4A.jpeg" /><figcaption>Our setup for the Co-Design wks, from left to right: Customer journey AS IS, Core values, Mapping TO BE, Prioritization canvas, Validation Canvas, Rip and Mix</figcaption></figure><p>After few weeks they came back in Milan and we had the chance to get them for another couple of workshops. We met them with the customer journey “as is” and together we mapped out again the whole experience, this time creating a “to be” scenario. No limits on the ideas, we wanted to create a real ideation moment, forgetting everything about costs, feasibility, time and technology. The result was really impressive, we collected more that 100 ideas about how improve the user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5xM3itKEKM8SbtPVT4lC-g.jpeg" /><figcaption>Gab here in his best mime skills</figcaption></figure><p>Of course you cannot use all these ideas and you need to drill down to something that the team could achieve. If putting a challenging goal is the best you could do to engage your team, putting impossible ones will have the opposite result. We used a board to create a prioritisation canvas with customer value on one axis and business value on the other one. Every idea we put on the upper right space is something the team has to follow, everything on the bottom left part is something you can forget about.</p><p>So now we now what is a must have and what is not. We still don’t have a clue about what is feasible and cost wise doable. That’s why we took all the ideas and we validated them on a validation chart, from easy to hard to do we put every post it having a better clue of what is important to do and how easy to achieve it is.</p><p>The overall result of this 2 days activity is the customer journey to be, an big level flow of every step the user has to do in order to use the service, it’s divided in 10 phases:</p><ul><li>Discovery</li><li>Onboarding</li><li>Engagement</li><li>First purchase</li><li>Post purchase</li><li>Use</li><li>Billing</li><li>Profiling</li><li>New limit</li><li>Offboarding</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DjXugki2dWqdoSfmNW8b8g.jpeg" /><figcaption>Customer journey TO BE</figcaption></figure><h4><strong>Branding and visual language</strong></h4><p>Well, this, along with the naming phase was the most difficult to achieve. It’s really easy for a client to have an opinion about a logo or a name, so we expected somehow to spend some effort on top here. We designed some different logos keeping in mind our target, someone in the mass area that wants to use an easy and free service. They need to trust the brand and see it approachable, not too far away, not too exclusive, not too elegant.</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DiP8bH7YRwzM&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FiP8bH7YRwzM&amp;type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7e2ddce7c9aa0125009e166272888f4e/href">https://medium.com/media/7e2ddce7c9aa0125009e166272888f4e/href</a></iframe><p>The final logo has a fresh, modern and trustable design that expresses not only the innovation of the service but its human side and at the same time its reliability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*CvRFjcQmUuddEIuUPd5o_w.gif" /></figure><p>The shapes of the positive and negative spaces of the logo creates a large variety of possibile declinations of the logo itself.</p><p>The smile can also be used during animation processes in order to express sentiments that can emphasize with the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m3Kd0zXSWVNB2YvIjx_9Jg@2x.png" /></figure><p>We designed the card as well. We used the logo in different shapes and colours in order to have a process that a single design. Every card it’s unique but still recognisable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*1wwkoJOGqLsQFr6nk1IIqQ.gif" /><figcaption>Some of the cards we designed, all different, all Solvy</figcaption></figure><p>The smile that been used as the shape to design the merchant sticker. This solution in perfect for an immediate impact being also very recognizable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xkHy4tcwzIl7Oqhz1_sq3Q.jpeg" /><figcaption>Application of the sticker</figcaption></figure><p>A full brandbook has been designed in order to give all the needed info to use and develop the Solvy brand. Card design, App design, icons, logo usage, fonts and typography and colors all in one book.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KYPmOGl7ILJUgIu7ReSH8w.jpeg" /><figcaption>The Solvy brandbook</figcaption></figure><h4>Let’s go to Moscow in February ✈️ 😱 ❄️</h4><p>Exactly after having designed all this stuff we went to Moscow. The client asked us to present everything we did to the investors. We had 3 days (weekend of course) to setup a keynote and to fly to Moscow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OeX1eS_sOEbnXM2j3-mdcg.jpeg" /><figcaption>Us + the client in the background after the investors keynote</figcaption></figure><p>Well, can’t go deep in details but that was the hardest presentation of my career. Moscow is beautiful but -20 degrees all day long can be annoying sometimes.</p><h4><strong>Mobile app</strong></h4><p>The client asked us to design the whole flux of the app, without going so deep as a screen flow but giving them all the tools to be able to do it. That’s why we created the app flux that investigate every single aspect of the app without describing details like buttons or interfaces. We also designed a single section of the app in detail in order to give them an idea of the layout and interactions. These two tools together are everything you need to create a great app.</p><h4><strong>App flux</strong></h4><p>Visualize and explain in details each aspect of the offered service for each use cases. The flow allows all the actors involved to have an overview of the offered service and its ecosystem and gives a detailed map of the Solvy app interface and functionalities. This is a mandatory deliverable to design the App screen flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*GSVGlB1Fidx6k__6uJz4gA.gif" /><figcaption>The app flow has 98 steps on it and 12 sections</figcaption></figure><p>We designed a strong and flexible Sketch library to be able to handle such a map. Every step is inside an iPhone outline to better convey the idea of the app, a section label on top help the reader to understand the area of the app, a number on the top right corner is mandatory if you wanna do a remote review with your client on a file with 100 screens. We also used some interactions between a step and the others just to give the idea of the way we expect the user could interact with that area.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e68IohGi94YnGftOeVw4Sg.png" /><figcaption>The Sketch setup</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b794XJExrSw-ntAYu_qyxQ.png" /><figcaption>The symbol page of our Sketch file</figcaption></figure><h4><strong>Interface</strong></h4><p>The app is the main touchpoint for the Solvy experience. We designed it keeping in mind the pillars: usefulness, good communication, simplicity, convenience.</p><p>We designed the dashboard, a section of the app where the user can see all the data about the money he/she’s using with Solvy. The dashboard has 3 sections, one is the past where all the expenses of the previous months are stored, divided by categories helps the user to figure out where he spent too much. The present is a section with the list of all the expenses of the current month and the future is the last section with the prevision of how much will be the next rate. The idea behind this is to empower the user giving him/her info about what he did in the past, what he/she is doing right now an what to expect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-lBqjIr8BaqMb94IwzAKjg.png" /><figcaption>Past, Present and Future of the user expenses</figcaption></figure><p>When we design something we have a responsibility as designers. We are not only responsible for the good design of the app, we are not only responsible for the service to achieve its goal. We are also responsible of creating something the user will understand and in case of a fintech service we are responsible to not trick the user and to help him/her to use his/her money in a new way that will be helpful in his/her life. That’s what we tried to do with Solvy, designing a fintech service with a social responsibility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*4SVHHUAokidJxy1ABZmzUw.gif" /><figcaption>Bonus — Gab skating backwards in the Red Square, yes the one in the back is the Kremlin ⛸🔝</figcaption></figure><p>I tried to keep this post short, there are hundreds of other things to tell about this project but here I explained the main activities we carried out. If you have any other question about what we did and how, just post a comment, we’ll be happy to answer you or catch up with <a href="https://www.linkedin.com/in/albertoandreetto/">me</a> or <a href="https://www.linkedin.com/in/gabrieledemarindesigner/">Gab</a> on Linkedin.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=549f0046311a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sketchin/from-branding-to-interaction-a-fintech-end-to-end-project-in-sketchin-549f0046311a">From branding to interaction, a fintech end-to-end project in Sketchin</a> was originally published in <a href="https://medium.com/sketchin">Moving forward</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What did i learn switching from a company to a design agency as UX Designer?]]></title>
            <link>https://medium.com/@aandreetto/what-did-i-learn-switching-from-a-company-to-a-design-agency-as-ux-designer-1fdbb0fcf142?source=rss-ff4b9d4d6203------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fdbb0fcf142</guid>
            <category><![CDATA[agencylife]]></category>
            <category><![CDATA[ux-designer]]></category>
            <category><![CDATA[learn]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Alberto Andreetto]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 14:02:59 GMT</pubDate>
            <atom:updated>2017-06-13T14:02:59.125Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XFh-VhIvULE_jAPsz4jwbA.jpeg" /></figure><p>My former job was Interaction Designer for <a href="http://www.stylight.de/">Stylight</a>, an ecommerce aggregator based in Munich, Germany. Stylight is a cool company with almost 200 employee at that time and with a team of 15 designers (UX, IX, illustrators, graphic and so on). Working there means working in an agile environment, where the team is in charge of the product and where everyone in the team has the same possibility to say something about what they’re designing. Starting January 2017 i decided to move to a <a href="http://www.ander.group/">design agency</a>, just because i never worked in an agency before and i was curious to challenge myself with this. I decided to move back to Switzerland and I joined Ander Group, an interesting agency in Lugano with 10 designers, working mainly in the digital design field. I decided to write this because i had so many questions when i started and i hope i can help somebody else doing the same switch.</p><h3>Time matter</h3><p>Working for a company means you are designing for yourself, you can have all the pressure you want but there’s no client waiting for the stuff you are doing. For sure dealing with an internal deadline is different than dealing with an external client. Usually you can easily talk with the team you are designing for and telling them you need 3 days more for the wireframe they were waiting for, you can’t do this with a client.</p><h3>Time = money</h3><p>Time is money, everybody says that but u never really face this till u are in a design agency. If you sold a project for a certain amount of money you know that you have a certain amount of days you can work on it. As designers we know we could work on a project forever, is never finished and can be always better. In an agency you really have to challenge yourself to get the best out of it in a given time. If you pass the deadline (in the case you are super lucky and the client agree) you are losing money.</p><h3>Agile is not so easy in an agency</h3><p>In Stylight i was working really agile and i have to admit this, I fucking love it. I think working agile in a dev team is the best thing you can do, everything goes smooth, everybody have clear goals and more important everybody knows what to expect every two weeks. If you can’t wait 2 weeks the problem is not agile, is something else.</p><p>Right after my start in Anger Group i tried to apply everything i knew about agile in the agency, well, is not exactly the same. Working at multiple project per time for different clients and with different deadlines really messes up everything. If you want to apply agile in an agency you need to be really structured and plan your workflow in a perfect way.</p><h3>Deal with the client</h3><p>In a company you have no client, or at least you have no external client usually. You can have internal client but is something different. Dealing with the client is an important side of the job in an agency. How you deal with it will let your job being smooth and clean or a hell. I stumbled upon a blog once, hell of a client, and everything is true. Except that the client act how you let them act. As designers we need to reach the client and to create a workflow with them that won’t let them change everything 2 days before the deadline. The story about not being in charge of how the client will react to our job is just bullshit. Make the client being part of your design process, make them feel active and be clear about what you will provide them and when and the client will be happy.</p><blockquote>Happy client = happy designer</blockquote><blockquote>Happy designer != happy client</blockquote><h3>1+1 is not 2</h3><p>Well, I already knew this from Stylight but here is even more clear. The real power of an agency is not the singles designers, is the fact that they will work together to achieve one single goal. An agency is more than a bunch of freelancer sharing a desk. If you settle up your agency with designers that doesn’t talk to each other the client won’t see the value in your agency.</p><h3>Up and down</h3><p>In a company your work is always stable. You always have the same amount of stuff to do. Sure u can can have some period of the year with more work (a fair, a show, a release…) but usually you have the same stuff to do from Monday till Friday. In an agency is not like that, you cannot put your client in a queue and let them wait. There will be times with a lot of stuff to do and times with nothing (well, hopefully not nothing) to do. Just plan some side projects in order to have something to work on when you’ll have the down time.</p><h3>Wider vs deeper</h3><p>I spent the last 2 years of my life designing basically one single customer journey. The way u can go deeper in a company you’ll never face it in an agency. You learn a lot in a company about your users, if you are lucky to have a lot of users (I had 15 millions per month) you can get a lot of insights that you will use again later in your career. In an agency you can go wider than deeper. You can switch project every 3/6 months and start again, it’s not better or worse it’s just a different approach. The only advice I can give is to not just let go the project u do. Just not ship a website and forget about it. Take care of it and propose to the client a review of the KPIs and of the goals after 6 months in order to optimize it and you’ll have the perfect mix between working for a company and an agency.</p><p>So far this is what I got from working in an agency, it’s just 6 months so I guess I’ll have new thoughts in a few.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fdbb0fcf142" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>