<?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[Idib Group - Medium]]></title>
        <description><![CDATA[A User Experience agency located in Italy and USA. Research, storytelling and superior design are our ingredients to let your ideas come to life. - Medium]]></description>
        <link>https://medium.com/idib-group?source=rss----4fc15fd5a3ed---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Idib Group - Medium</title>
            <link>https://medium.com/idib-group?source=rss----4fc15fd5a3ed---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:55:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/idib-group" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Il paradosso dei dati: quando troppa informazione paralizza le decisioni]]></title>
            <link>https://medium.com/idib-group/il-paradosso-dei-dati-quando-troppa-informazione-paralizza-le-decisioni-372311697c42?source=rss----4fc15fd5a3ed---4</link>
            <guid isPermaLink="false">https://medium.com/p/372311697c42</guid>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[ai-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Francesco Stagno d’Alcontres]]></dc:creator>
            <pubDate>Wed, 02 Jul 2025 15:49:13 GMT</pubDate>
            <atom:updated>2025-07-02T15:49:12.976Z</atom:updated>
            <content:encoded><![CDATA[<p>A mio parere, stiamo vivendo il paradosso più affascinante dell’era digitale: abbiamo più dati di quanti ne abbiamo mai avuti nella storia dell’umanità, strumenti di analisi sempre più sofisticati e algoritmi che elaborano informazioni a velocità impensabili.</p><p>Eppure molte organizzazioni si trovano paralizzate proprio da questa abbondanza di informazioni, non per mancanza di dati, ma piuttosto per l’incapacità di trasformare questi dati in decisioni concrete che producano risultati duraturi.</p><p>Qualche tempo addietro ho avuto una call con il digital manager di una grande catena di negozi che mi spiegava una situazione emblematica: i loro clienti online acquistano in media una volta l’anno e perdevano conversioni nella fase di checkout. La soluzione sembrava ovvia: sistemare il processo di pagamento e aumentare le vendite.</p><p>Ma qui emerge il <strong>data paradox</strong>.</p><h3>Quando la certezza matematica diventa paralisi</h3><p>Il problema fondamentale è che i dati ci dicono <em>cosa</em> sta accadendo, con precisione matematica, ma non ci dicono <em>perché</em> sta accadendo e soprattutto non ci dicono cosa dovremmo fare per creare valore a lungo termine. Il formato Excel, per quanto preciso e rassicurante, non comunica significato autonomamente. Nel nostro lavoro di agenzia, incontriamo quotidianamente organizzazioni che si fermano alla valutazione numerica: manager che devono giustificare le decisioni con dati inconfutabili, team che cercano nei numeri quella sicurezza che il business non può garantire. Ma questa ricerca di certezza spesso porta al risultato opposto: la paralisi decisionale.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YBqjT7KILsE3v9nOriI4uQ.png" /></figure><p>Ecco il paradosso: la tendenza a concentrarsi su ciò che è facilmente misurabile (come i tassi di abbandono del checkout), ignorando questioni più profonde e complesse che i dati non rivelano direttamente. Nel caso del franchise, i numeri indicavano un problema di conversione — ma invece di chiedersi “come sistemiamo il checkout?”, la vera domanda strategica era “perché questi clienti comprano solo una volta l’anno?” Questo è il limite dell’analisi puramente quantitativa: rimanendo entro i confini delle variabili note — quelle che possiamo controllare, misurare e ottimizzare — rischiamo di diagnosticare male la vera sfida. Sistemiamo il checkout e miglioriamo leggermente le conversioni, ma non affrontiamo la bassa frequenza d’acquisto, che probabilmente dipende dal comportamento dei clienti, dalla percezione del brand o da bisogni non soddisfatti — tutte cose che i numeri da soli non spiegheranno mai.</p><h3>Dal caos nascono le strategie vincenti</h3><p>Il nostro metodo introduce un livello di “Creative Disorder” nel processo decisionale lineare delle aziende. Nel <em>design thinking</em>, parliamo di fasi divergenti e convergenti: prima espandiamo il campo delle possibilità esplorando soluzioni che possono sembrare irrilevanti, poi convergiamo verso la soluzione più promettente. Dove il business tradizionale dice “ho il problema A, lo risolvo con la soluzione B”, noi diciamo “aspetta, esploriamo prima tutte le possibili interpretazioni di A e tutte le possibili soluzioni creative.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Khk_gY74RXgj4gsSdguD-g.png" /></figure><p>Un esempio concreto di questo processo lo abbiamo sperimentato con un player europeo nell’ambito della formazione online. Avevamo condotto un’analisi quantitativa completa del mercato: il 32% del target citava “prezzi alti” come principale barriera all’iscrizione, avevamo mappato tutti i competitor, le preferenze per età, geografia e motivazioni. Ma erano paralizzati da questi dati. Vedevano quel 32% e pensavano: “Dobbiamo abbassare i prezzi.” Per rigenerare questi dati, abbiamo applicato un processo in tre fasi: <strong>Fase divergente</strong> — abbiamo preso ogni insight quantitativo e ci siamo chiesti “cosa succederebbe se interpretassimo questo dato al contrario?” Quel 32% “prezzi alti” poteva significare non che costassero troppo, ma che le persone percepivano poco valore. <strong>Validazione</strong> — abbiamo trasformato le percentuali in storie umane con paure, ambizioni e frustrazioni specifiche, validandole attraverso interviste mirate con persone del campione originale. <strong>Convergenza strategica</strong> — abbiamo combinato insights apparentemente scollegati: “Prezzi alti” + “interesse alle certificazioni” + “motivazione lavorativa” = opportunità nascosta. E se invece di costare meno, garantissimo risultati concreti? Da questa esplorazione è emersa una strategia “Pay on Success”, dove paghi solo se raggiungi risultati misurabili come certificazioni o avanzamenti di carriera. Abbiamo trasformato “la scuola più costosa” in “il partner che investe nel tuo futuro.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QKNTMuxBQ4QxEJ6_x2pyMw.png" /></figure><h3>L’era dell’AI e il ruolo insostituibile dell’intelligenza umana</h3><p>Il valore di questo approccio non sta nel sostituire l’analisi quantitativa, ma nel completarla attraverso quello che definiamo “rigenerazione dei dati”. Non demoniziamo i numeri, non li ignoriamo, ma li facciamo parlare diversamente, collegandoli a elementi generalmente non misurati: emozioni, contesto sociale e dinamiche comportamentali che emergono solo attraverso l’osservazione diretta e l’interpretazione creativa.</p><p>Non sostituiamo i <em>data scientist</em>, li completiamo trasformando i loro numeri in storie che generano azione concreta.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zWVVtRcXhfonP01NcWLfQw.png" /></figure><h3>La saggezza sta nell’incertezza</h3><p>La comprensione delle cause è sempre un processo ipotetico, per definizione. Non possiamo mai essere sicuri al 100% che la nostra interpretazione sia corretta. Ma questa incertezza non è un bug; è una feature. Perché è proprio questa incertezza che ci spinge a rischiare, sperimentare, innovare.</p><p>I dati possono darti certezza, ma senza rischio non c’è innovazione.</p><p>Qualcuno potrebbe obiettare: “Dato che l’interpretazione umana può essere viziata e soggettiva, non sarebbe più responsabile lasciare che gli algoritmi prendano decisioni direttamente dai dati?” È un argomento convincente, e onestamente ci sono contesti dove forse il decision-making algoritmico è superiore: rilevamento frodi, diagnostica medica, ottimizzazione della supply chain.</p><p>Ma ecco cosa abbiamo imparato: anche l’algoritmo più sofisticato prende decisioni basate su pattern storici. Ottimizza per quello che ha funzionato prima, non necessariamente per quello che potrebbe funzionare meglio. Nel caso del player della formazione online bloccato sul 32% “prezzi alti”, un algoritmo avrebbe raccomandato ottimizzazione dei prezzi per sempre.</p><p>Il vero potere emerge quando combini precisione algoritmica con creatività umana. Lascia che gli algoritmi gestiscano il riconoscimento di pattern e l’elaborazione dati — sono vastamente superiori a noi in questo. Ma usa l’insight umano per questionare se stiamo ottimizzando per i risultati giusti.</p><h3>Il navigatore nell’era degli algoritmi</h3><p>I processi non lineari che introduciamo servono proprio a questo: rompere la linearità rassicurante ma spesso limitata dell’ottimizzazione algoritmica. Se ottimizzi solo il conosciuto, non saprai mai se il conosciuto è la tua migliore proposta. Per capirlo, devi essere disposto a introdurre disordine, manipolare il sistema, mettere in discussione assunti fondamentali.</p><p>Nell’era dell’intelligenza artificiale, il nostro ruolo non è competere con gli algoritmi nella loro capacità di elaborare informazioni. Il nostro ruolo è essere l’interfaccia insostituibile tra il mondo dei dati e il mondo umano, assicurandoci che ogni decisione non sia solo matematicamente corretta ma anche umanamente significativa e strategicamente sostenibile.</p><p>Come ho appreso dall’amico velista Paolo Manzoni: puoi avere tutti gli strumenti del mondo, ma nel momento decisivo finale, è sempre l’elemento umano che fa la differenza tra vincere e perdere.</p><h3>Il potere delle narrazioni</h3><p>Quando creiamo esperienze digitali, non stiamo solo costruendo interfacce — stiamo creando narrazioni che gli utenti vivranno. Ogni click, ogni interazione è parte di una storia che stiamo raccontando su come la tecnologia dovrebbe sentirsi, su come i problemi dovrebbero essere risolti.</p><p>C’è una differenza cruciale tra storytelling e analisi dei dati: le storie sono ipotesi sul comportamento umano, mentre i dati ci dicono cosa è già successo. Le decisioni più potenti emergono quando usi i dati per validare quali storie vale la pena raccontare, e le storie per immaginare quello che i dati non possono ancora misurare.</p><p>I dati ti tengono sulla riva sicura di quello che conosci, ma le storie ti spingono nelle acque imprevedibili dove succede la vera innovazione. Il nostro ruolo è essere navigatori che sanno leggere sia gli strumenti che le onde.</p><h3>La scelta che definisce il futuro</h3><p>La vera domanda non è se i dati siano importanti — lo sono. La domanda è se siamo disposti ad andare oltre la sicurezza dei numeri per esplorare territori inesplorati dove nascono le vere opportunità di innovazione.</p><p>Ma quale approccio è più rassicurante? La certezza di aver preso la decisione più corretta date le evidenze disponibili, o la speranza di aver intrapreso un corso verso orizzonti che intravediamo?</p><p>A mio parere, la speranza dell’orizzonte è infinitamente più potente dell’illusione della certezza. I dati possono darti fiducia sul passato, ma non possono garantire il futuro. Il caso del player della formazione online ce l’ha insegnato: avrebbero potuto ottimizzare i loro prezzi per sempre basandosi su quel 32% di dati, ma non avrebbero mai scoperto che “Pay on Success” era la loro posizione più forte.</p><p>Come ha dimostrato Paolo (il velista), hai bisogno sia degli strumenti che del coraggio di leggere le onde che i tuoi strumenti non riescono a misurare. <strong>L’orizzonte rappresenta possibilità, crescita, innovazione</strong> — tutto quello che rende il business eccitante e umano.</p><p>Perché alla fine, ciò che distingue le aziende che crescono da quelle che sopravvivono non è la qualità dei loro dati, ma il coraggio di usare quei dati come trampolino di lancio verso l’ignoto, invece che come ancora di sicurezza nel conosciuto.</p><p>Il <em>design thinking </em>applicato ai dati non è solo una metodologia — è una filosofia che riconosce che il futuro del business non si trova nelle colonne di Excel, ma nell’immaginazione umana che sa leggere tra le righe di quelle colonne. È scegliere di andare per mare invece che rimanere a terra a giudicare.</p><p><em>Se vuoi approfondire come applichiamo questo approccio ai progetti dei nostri clienti, puoi esplorare il nostro metodo su </em><a href="https://idibgroup.com/"><em>idibgroup.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=372311697c42" width="1" height="1" alt=""><hr><p><a href="https://medium.com/idib-group/il-paradosso-dei-dati-quando-troppa-informazione-paralizza-le-decisioni-372311697c42">Il paradosso dei dati: quando troppa informazione paralizza le decisioni</a> was originally published in <a href="https://medium.com/idib-group">Idib Group</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coda, Miro, Figma e Zoom.]]></title>
            <link>https://medium.com/idib-group/coda-miro-figma-e-zoom-6d0654c1a2b4?source=rss----4fc15fd5a3ed---4</link>
            <guid isPermaLink="false">https://medium.com/p/6d0654c1a2b4</guid>
            <category><![CDATA[design-tools]]></category>
            <category><![CDATA[communication-tools]]></category>
            <category><![CDATA[smart-working]]></category>
            <category><![CDATA[design-agency]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Donatella Ruggeri]]></dc:creator>
            <pubDate>Mon, 16 Mar 2020 17:41:29 GMT</pubDate>
            <atom:updated>2020-03-16T18:58:20.525Z</atom:updated>
            <content:encoded><![CDATA[<h3>Coda, Miro, Figma e Zoom. Gioie e dolori della nostra agenzia con questi strumenti di lavoro (in remoto)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2WiDVMFUZGr8z_VAh7UsbQ.jpeg" /></figure><p>Essere un gruppo flessibile e affiatato ci consente di cambiare in corsa e adattarci a tutte le necessità. Così come tutti ci siamo trovati ad affrontare le sfide del Coronavirus e del remote working.</p><p>Ecco che nel confrontarci sugli strumenti da usare, ci siamo ritrovati a commentare <strong>lati positivi e negativi </strong>di ciascuno di essi, che abbiamo condiviso anche sulla nostra pagina Facebook (se volete seguirci, <a href="https://www.facebook.com/idibgroup/">siamo qui</a>).</p><p><em>Disclaimer: nessuno strumento è perfetto, nessuno strumento è ideale sempre e per tutto. Per questo condividiamo gioie e dolori della nostra agenzia di delle prese con gli strumenti di progettazione partecipata che, in questi giorni, si svolge interamente da remoto.</em></p><h3>Giorno 1: Coda, ecco come lo usiamo in Idib Group</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-E3fcwqhbExj00RUDgtfRQ.jpeg" /><figcaption>Foto di Francesco Stagno d’Alcontres</figcaption></figure><p><strong>Perché ci piace</strong></p><p>Cominciamo col dire che per le nostre esigenze attuali, il <strong>piano gratuito</strong> è sufficiente. E ci sembra già un bel vantaggio.</p><p>Coda.io ci piace perché fornisce un <strong>unico spazio per archiviare testi, tabelle ed altri media</strong> che riguardano un progetto. Può essere organizzato in cartelle e sezioni e si integra molto bene con Google Drive. Da dentro Drive, infatti, di solito apriamo un file Coda nella cartella del progetto, un file che si chiama inizialmente <em>Brief</em>, retaggio di “vecchie” linee guida interne all’agenzia che abbiamo sempre faticato a seguire, dovendo adattarci con velocità e flessibilità ai tempi e alle esigenze della progettazione e dei clienti.</p><p><strong>Come lo usiamo in Idib Group</strong></p><p>Su Coda tutti i membri del team assegnato al progetto (in genere un ricercatore, un visual designer e uno UX designer) contribuiscono alla crescita del file, aprendo cartelle, sezioni (così Coda chiama le pagine) e avendo sempre una buona panoramica del progetto e dei suoi progressi con un semplice colpo d’occhio.</p><p>Su questo file aggreghiamo informazioni che arrivano dalla ricerca con gli utenti, dal design visivo, dalle analisi tecniche, dalla SEO. Praticamente tutto. Dentro Coda infatti è possibile collegare le pagine tra loro e raggiungerle velocemente per approfondire i vari pezzi di design, con chiarezza e semplicità.</p><p>Infine, nelle ultime settimane lo stiamo sperimentando come vero e proprio <strong>deliverable</strong>, documentazione per il cliente, in sostituzione del vecchio deck in PDF.</p><p><strong>I problemi che Coda ha risolto per noi</strong></p><ul><li>Organizzare vari tipi di contenuti (testi, tabelle, immagini e chi più ne ha più ne metta) in un unico posto</li><li>Evitare il moltiplicarsi di documenti su Drive che causavano confusione anche all’interno di micro team (due o tre persone)</li><li>Dover seguire in maniera rigida linee guida sulla creazione e l’uso dei file per raccogliere e documentare il nostro lavoro</li><li>Collegare i pezzi del puzzle della progettazione attraverso link ipertestuali ed estensioni</li></ul><p><strong>Cosa non ci piace di Coda</strong></p><ul><li>Non è disponibile offline</li><li>Ha un piccolo problema di usabilità che induce in errore almeno la metà delle volte quando copi e incolli le tabelle da una parte all’altra</li><li>Non è possibile modificare il layout o la formattazione dei contenuti</li></ul><p><strong>Una alternativa a Coda</strong></p><p>Una alternativa che abbiamo testato in precedenza è <a href="https://www.notion.so/?utm_source=google&amp;utm_campaign=brand_alpha&amp;utm_content=row&amp;utm_term=notion&amp;gclid=Cj0KCQjwx7zzBRCcARIsABPRscO0o7L2ubb5VrRInhW_JRQEAF46YqMeuyvSzTvPkqfUDJxTWvgla0AaAgEiEALw_wcB">Notion</a>, che però ci è sembrato un po’ caro, se consideriamo che il costo si aggiunge a tutti gli strumenti di cui disponevamo già in agenzia.</p><h3>Giorno 2: Miro</h3><p>In origine fu Real Time Board, dopo un rebranding si fa chiamare <a href="https://miro.com/app/">Miro</a>.</p><p>Si tratta di uno spazio digitale condiviso che permette di creare diagrammi di flusso, schemi e canvas (e questi sono solo gli usi che abbiamo trovato noi, ma si può fare praticamente di tutto).</p><p><strong>Perché ci piace</strong></p><p>E’ molto semplice da usare, non ha bisogno di grandi tutorial per essere compreso. Il tool è eccellente per creare deliverable, anche complessi, che vengono semplicemente esportati nel formato migliore.</p><p>Ha i <em>post-it</em>, fatto che consente di riprodurre esattamente la stessa esperienza visiva dei workshop di co-design.</p><p><strong>Come lo usiamo in Idib Group</strong></p><p>I nostri team usano Miro non solo per fare brainstorming, ma anche per visualizzare processi, journeys, flussi, personas, etc. (in foto vedete proprio un dettaglio di una Customer Journey).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5peVW6oWrCmIChfypHYwlg.jpeg" /><figcaption>Foto di Francesco De Mento</figcaption></figure><p><strong>I problemi che Miro ha risolto per noi</strong></p><ul><li>Visualizzare il quadro generale</li><li>Sintetizzare informazioni di ogni tipo senza passare da un’applicazione all’altra</li><li>Fare <a href="https://www.nngroup.com/articles/dot-voting/"><em>dot voting</em></a> con il cliente</li><li>Organizzazione e conduzione di workshop distribuiti</li><li>Riprodurre e conservare in formato digitale canvas che realizziamo fisicamente durante i workshop</li></ul><p><strong>Cosa non ci piace di Miro</strong></p><ul><li>Non è pixel-perfect, non ha quella precisione che un team di design apprezza</li><li>Pur integrando <a href="https://thenounproject.com/">The Noun project</a>, non consente di cambiare i colori delle icone</li><li>Fa molte cose, ma nessuna in modo perfetto. Il vantaggio è che tutte queste cose le puoi fare in un solo “posto”</li></ul><h3>Giorno 3, Figma</h3><p><a href="https://www.figma.com/">Figma</a> è piuttosto noto tra chi si occupa di visual design, per questo saremo brevi: a nostro parere è il miglior strumento per il lavoro collaborativo su interfacce e prodotti digitali semplici. <strong>Ci piace!</strong></p><p><strong>Cosa non ci aiuta di Figma</strong></p><ul><li>Non esiste una vera e propria modalità di lavoro offline</li><li>La gestione dei vettori, rispetto ad altri tool, lascia un po’ a desiderare</li><li>La visualizzazione dei progetti e dei team nella dashboard non è molto chiara e lineare e alle volte l’utente perde di vista i progetti</li></ul><h3>Giorno 4, Zoom</h3><p>Di strumenti per la videoconferenza ce ne sono moltissimi, ma il nostro preferito è <a href="https://zoom.us/">Zoom Meeting</a>.</p><p>Funziona sempre bene, consente di collegarsi anche con una telefonata se si ha una scarsa connessione internet, è integrato con Chrome e Calendar, ha <strong>tutte le funzionalità necessarie e nessuna superflua</strong>.</p><p>Normalmente lo attiviamo nella nostra sala riunioni, ma in questi giorni gli sfondi delle nostre webcam sono le pareti delle nostre abitazioni.</p><p>L’importante è rimanere operativi e sul pezzo, e Zoom è un ottimo modo per farlo!</p><p>Se vi va di condividere i vostri strumenti preferiti o i vostri feedback su questi quattro appena trattati, siamo tutti orecchi.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d0654c1a2b4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/idib-group/coda-miro-figma-e-zoom-6d0654c1a2b4">Coda, Miro, Figma e Zoom.</a> was originally published in <a href="https://medium.com/idib-group">Idib Group</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Design Thinking changed my perspective (and my career too)- interview to Grazia Maria Giordano…]]></title>
            <link>https://medium.com/idib-group/how-design-thinking-changed-my-perspective-and-my-career-too-interview-to-grazia-maria-giordano-2452d6bd0527?source=rss----4fc15fd5a3ed---4</link>
            <guid isPermaLink="false">https://medium.com/p/2452d6bd0527</guid>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[enterpreneurship]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Donatella Ruggeri]]></dc:creator>
            <pubDate>Wed, 15 May 2019 12:29:28 GMT</pubDate>
            <atom:updated>2019-05-16T10:55:41.770Z</atom:updated>
            <content:encoded><![CDATA[<h3>How Design Thinking changed my perspective (and my career too)- interview to Grazia Maria Giordano, independent business consultant</h3><p>I digitally met a cheerful <a href="https://medium.com/u/21c489857f5e">Grazia Maria Giordano</a> a few weeks ago and since then something has been tickling my brain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*1FMUjD4LKtvKa9DqrqWiHA.jpeg" /></figure><p>Grazia Maria is a business consultant, she comes from my same hometown, she has lived and worked in Rome, Milan, Washington DC and Amsterdam and she speaks four languages. Apart from her professional and life achievements — which I believe can be considered as a model for women struggling with starting up a career while taking care of the family, that is sadly still very uncommon — when chatting during a Zoom call she said something that surprised and fascinated me. She said that she had been unconsciously looking for a fun, fast, adaptive and flexible framework for her entire career and that she knew she had found it only when she came across a <strong>book </strong>about Design Thinking (you will read more in this interview).</p><p>This surprised me (a fairly green UX designer and a cognitive psychologist) for two reasons: I kind of felt the same when I started using this method in my daily working life, often asking myself “how did I manage to work without it?”; also, she discovered Design Thinking after years of “traditional business processes”, while creating her own process, and without any hesitation, she started using it.</p><p>So this gave me the hint to wanting to know more and I asked if I could interview her. She kindly agreed and this is what we discussed. <strong>I hope her story can inspire those managers and entrepreneurs that feel like they need to change their methods in order to meet people’s real needs</strong> and improve the working environment and the customer experience.</p><p><em>NB: “Design Thinking” will be “DT” from now on</em></p><h4>Grazia Maria, how would you introduce yourself to a stranger?</h4><p>The most difficult question someone can ask me is “where are you from?”. This question throws me really in confusion! I’m originally a Sicilian from Messina, have lived in Rome, Milan, Washington DC and Amsterdam. My husband is from Genoa so we spend a significant amount of time there and I’ve always traveled a lot. Each place I’ve lived in, each place I’ve visited has left a tiny mark in my heart, in my soul, and in my mind so nowadays I feel that I’m from all these places. It’s difficult for me to provide a straight answer to such a simple question. I have three daughters, and I speak 4 languages. I love reading. I could read (and sometimes I do) anything.</p><p>I work as an independent consultant. <strong>My ambition is to help organizations to grow their business improving the way they interact with their customers, their employees, and their partners</strong>.</p><blockquote>Over the years I’ve developed my own approach, “People Friendly Processes”, which is at the base of the projects I manage. “People Friendly Processes” aims at bringing the person to the center of the processes to create the best environment where people can thrive.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ImzWHW3cLuNub2LWrtLaA.jpeg" /></figure><p>My ”People Friendly Processes” approach can be used in different contexts such as <strong>Product and service innovation</strong>, <strong>Customer Experience design</strong> and improvement, <strong>Employee Experience design</strong> and improvement, <strong>Business Travel</strong>, <strong>Project Management</strong>, <strong>Change Management</strong>, etc.</p><blockquote>I love mixing tools from different fields of the management theory, depending on the project I’m managing.</blockquote><p>So I use more traditional instruments such as Lean, Organizational Design, Change Management, and Procurement best practices, but I’m leveraging more and more on newer tools such as Design Thinking and Storytelling.</p><p>My background is quite traditional: before starting my consulting business I worked in the corporate world (Procter &amp; Gamble, Vodafone), where I covered several positions within Financial Control and Procurement.</p><h4>Let’s start from the end: with whom and for which purpose do you use DT today?</h4><p>Today I use DT for several purposes.</p><p>First of all, I use it to design and develop the best <strong>Business Travel Programmes</strong> for organizations that need to create or improve the way they manage their Business Travel. I believe that in this particular situation DT is a <strong>very powerful tool to put together in a harmonious way the different interests of the several stakeholders with those of the Business Traveller</strong>. The Business Traveler is the end-user of the Travel Programme itself but <strong>usually is not involved in the creation of the Programme</strong>.</p><blockquote>It happens then that what it’s decided by someone else is not meeting the needs of the Traveller and this is when the problems raise. With DT all these issues are easily overcome.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XD4x6VtQxl1w1OFv4irVtw.jpeg" /></figure><p>Second, I use DT to <strong>help organizations improve their Customer Experience</strong>. Thanks to the input coming from Personas and Customer Journey Maps, organizations can quickly create new products or new features <strong>based on what their Customer really needs</strong>.</p><p>Last but not least, I’ve started using DT to <strong>promote a sounder and faster decision making and more effective project management</strong>. This very simple, yet powerful approach with sticky notes, voting and so on is the perfect way to address challenges of any sort, overcoming the difficulties of traditional approaches such as long tedious PowerPoint presentations, endless conference calls with several people where it’s very difficult sometimes to even understand what’s being discussed.</p><h4>What is the reaction you get when you introduce DT with your clients?</h4><p>The knowledge of DT is still quite low in organizations outside the Innovation/CX/UX field. People don’t really know what we’re talking about. And when you start explaining the methodology, they’re a bit put off as they think it’s something “fun” just for creative people, or they see it as the next “shiny thing”, which will cause a lot of hassle with no result.</p><p>That’s why <strong>I tend not to speak about DT in the beginning</strong>. I start speaking about their problems, and how the method I use can solve them. This put people in a listening mode and makes things a bit easier. <em>[this is how powerful DT is, I guess; you adopt it starting from changing perspective within your own work, ndr]</em></p><h4>It’s not always been like that… how did you work before adopting DT? What were the main problems, what the difficulties?</h4><p>My background is quite traditional: before starting as a consultant, I’ve worked for several multinational companies in financial planning and procurement roles. In my roles, I’ve always had great international exposure as a member of several important global projects. And <strong>the way of approaching a project of any kind was always the same</strong>.</p><blockquote>You get some input from your boss or a global function “dictates” what you have to do next. Then the negotiations start: negotiations with the global function as you’re trying to mediate their request with your reality (global functions are unfortunately well known for completely lacking any understanding of local realities!), negotiations internally with other departments/functions as the activity has some kind of impacts also for them. And all this is done via endless conference calls with a huge amount of people online. The projects would last months and, in the end, the result was not always what you hoped for.</blockquote><h4>Why did you decide to change your approach in the middle of your career? What was an enlightening moment or situation?</h4><p>I happened to learn of DT by chance. My business partner at that time advised me to read <a href="https://amzn.to/2WNdO3g">Change by Design from Tim Brown</a> and it was love at first sight! That book it’s a kind of “Bible” for DT. While I went through the pages, <strong>I became more and more aware that my personal way of addressing problems was very similar to the DT method</strong>. It was the cherry on top of the cake.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wG7df11Vpfnaeqi2m1ANuQ.jpeg" /></figure><blockquote>I had acquired a method, which could allow me to solve basically any problems in collaborative, engaging and, why not, fun way.</blockquote><h4>Tell us about an event or project that could have a different result, had it been developed using DT</h4><p>Well, I’ve run several projects over the years. But the one I’m sharing today goes back to my time as <strong>Purchasing Manager for Marketing and Communication in Vodafone Italy</strong>.</p><p>I remember we were trying to change the way we approached the production and printing of the material the client could find in the stores (flyers, brochures, etc). My teammate and I started talking to various printers, to the print management company which did the job on our behalf. We also tried to involve the Advertising agency which would design the materials. And, of course, we also involved the Communication department. And at each meeting, we were really disappointed by the kind of <strong>conservative attitude</strong> of the people we met and this, of course, <strong>didn’t bring a lot of new ideas on the table</strong>. At each meeting, our frustration grew and at a point <strong>we had to abandon the project because we were really at a dead end</strong>.</p><blockquote>I’m deeply convinced that with DT this project would have had a very different outcome!</blockquote><h4>Young entrepreneurs are advised to work on execution to implement an idea… Is DT “start-up stuff” or can it be beneficial to more traditional organizations? What are the attention points in this case, what are the differences?</h4><p>I strongly believe that DT is a method that <strong>can be used in every organization</strong>, it doesn’t matter the size or the industry. And I also think that it’s very powerful <strong>not only to innovate, to create new products or services but also to improve the way each organization designs their own internal processes and the way they make decisions</strong>.</p><blockquote>Every process has its own “user”, which might be a customer, a person in another department/function or a supplier. And once you design the process having in mind the needs of that user, you’ll have a better, more efficient and effective process.</blockquote><p>In larger organizations, one of the most critical aspects is siloed activity. Department A doesn’t know what Department B does. DT helps to break down silos and fostering collaboration, but it has to be a company-wide action. So implementing DT in bigger organizations calls for extensive participation and diffusion from all functions and departments.</p><h4>What is the DT tool you like best and why?</h4><p>I particularly love the <strong>empathy interviewing</strong>, which leads to the creation of “Personas”. I particularly like how you can create a rapport with your counterpart, and bring them to talk more freely about their challenges, their motivations. Once you learn to listen to them, you’ll get access to a world full of discoveries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WQXdfy2Yr7hLPLuURdGicA.jpeg" /></figure><h4>Which tool have you not yet used, but one you look forward to giving it a go?</h4><p>I’ve used more or less all the tools, I now aim at increasing the use of DT based methods in the management of more traditional projects. <strong>I strongly believe it will bring tremendous benefits.</strong></p><h4>You come from a long experience outside Italy. How is the Italian situation, compared to the rest of Europe or the US?</h4><p>The awareness about DT is growing in Europe. There are very interesting examples of organizations which have succeeded in developing DT such as the <a href="https://medium.com/u/7c16b1472933">Design Thinkers Academy London</a> or <a href="https://medium.com/u/7baf15e4c260">AJ&amp;Smart</a> in Berlin. In Italy, we’re still a bit behind, as we’re lagging behind in DT related disciplines such as Customer Experience (CX), User Experience (UX), and Employee Experience (EX). I feel in our country, <strong>DT is still too much enclosed behind the doors of innovation departments</strong>.</p><blockquote>We need to bring DT in the daily life of the organization, so as it can produce a significant change.</blockquote><h4>What is the reason why some companies are more resistant to experience new methods and processes?</h4><p>Companies are most of the times victims of a sort of inertia: it’s difficult to penetrate and make them change behaviors. <strong>It’s easier to keep doing things the same way as usual</strong>. The different departments or functions work in isolation: they have department objectives which clash with those of others. <strong>People don’t talk to other people</strong>. And people are blamed when they make mistakes. And all this is definitely very detrimental to innovation!</p><blockquote>Good ideas stop at the door of the person’s own office! Promoting innovation requires a change in the mindset, in the whole company and not only in those functions facing the customer or which are in care of innovation itself. But it’s not easy to achieve and it requires a coordinated effort within the organization. Innovation has to become a way of thinking and approaching a challenge and not a function.</blockquote><h4>What is a good approach to spread the DT culture and build DT mindset?</h4><p>Based on the above, I believe <strong>the best way to promote DT culture and mindset is through experience</strong>. It’s very hard to explain how a DT process works, but once you experience it, it’s done: people are usually won!</p><p>After a workshop, I’ve heard people saying <strong>they couldn’t imagine they would accomplish so much in such a short time</strong>. People who didn’t want to interview clients came back from interviews saying it was <strong>one of the best moments in their career</strong>.</p><blockquote>So the best way is to try it!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7V7x7BRfi0asDnVJtL0Afw.jpeg" /></figure><p>And you don’t need to go with a big project, you can apply it also to small things. There are so many techniques which can be applied. The other factor I’d consider is to <strong>apply it to a real challenge/problem you want to solve: this will make immediately apparent the benefits</strong> of the method and how it can produce results in a very short period of time.</p><h4>If you want to share your experience with Design Thinking both me and Grazia Maria will be happy to hear from you.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2452d6bd0527" width="1" height="1" alt=""><hr><p><a href="https://medium.com/idib-group/how-design-thinking-changed-my-perspective-and-my-career-too-interview-to-grazia-maria-giordano-2452d6bd0527">How Design Thinking changed my perspective (and my career too)- interview to Grazia Maria Giordano…</a> was originally published in <a href="https://medium.com/idib-group">Idib Group</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you need a cognitive psychologist in your design team]]></title>
            <link>https://medium.com/idib-group/why-you-need-a-cognitive-psychologist-in-your-design-team-2b4af3e0a48f?source=rss----4fc15fd5a3ed---4</link>
            <guid isPermaLink="false">https://medium.com/p/2b4af3e0a48f</guid>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[cognitive-psychology]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[neuroscience]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Donatella Ruggeri]]></dc:creator>
            <pubDate>Tue, 16 Apr 2019 14:13:22 GMT</pubDate>
            <atom:updated>2019-05-15T20:12:20.594Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rW7nnQLi2xldAxfTaybkeg.jpeg" /></figure><p>When creating teams for a new design project, agencies tend to include people who master primarily technical skills. Therefore, you will usually find a UI designer, a UX designer, a researcher, a copywriter, maybe a developer; if you’re lucky a project manager, and if you really need one, a data analyst. In my experience, this is the common configuration you see when working with design agencies. There can also be a hybrid, not-well specified figure which presents himself as “facilitator” or “moderator” in the co-design sessions.</p><p>As a professional psychologist with a background in cognitive, affective and social neuroscience I want to share a few reasons why <strong>you should consider adding a cognitive psychologist to your design team</strong>, highlighting the benefits your project will obtain. In fact, I’ve been working as UX designer at iDIB Group (a firm focused on Human Centered Design) for more than two years now and — not without a bit of surprise- I’ve been told I’ve brought some freshness and unique contribution to the working team.</p><blockquote><strong>DISCLAIMER</strong>: This is my personal view and feeling about the value of a professional psychologist involved in a design team. Of course different psychologists in the world will have different approaches, skills, attitudes, needs, and goals, so the following aspects could be biased by my experience and might not ever apply to your team. I also trained, live and work mainly in Italy, so some things might be culturally based and related.</blockquote><p>While most of the people with a technical background (IT, graphic design, and so on) might need to work a bit in the development and empowerment of their soft skills, I feel quite confident saying that a psychologist has already worked those skills out. I’m talking about soft skills such as empathy and respect when communicating, listening, negotiating, self-confidence, persuasion, questioning, reframing, and many others.</p><p>So let’s begin by saying the obvious: a psychologist is -first of all- a psychologist. This will allow him to contribute some basic and positive virtues to the work environment. When involved in a design process, he will wear and use his <strong>scientific lenses</strong> to first assess, and then deliver value to the project. But, again, let’s start with the basics.</p><h4>Basic aspects where a psychologist helps you and your team</h4><p>A psychologist has been studying how to build a <strong>positive, empowering and authentic relationship</strong> for most of his career, so it will be easy for him to <strong>get the best from every meeting</strong> or discussion that may arise with clients and within the team. He’s also a master in <strong>preventing and managing stress and emerging conflicts.</strong> As he is trained to be quite sensitive to the mood in the room, he can <strong>perceive and observe changes in behavior or attitude</strong> and act accordingly.</p><p>He has a <strong>profound knowledge about human cognition and behavior </strong>and<strong> </strong>he’s an expert in the complicated art of <strong>facilitating change</strong>. He’s a natural at <strong>seeing opportunities</strong> where other people see obstacles. He’s a scientist, so he will collect data, but maybe more importantly, force you to <strong>collect data supporting your decisions</strong>. Along with these skills, the cognitive psychologist on your design team will also most likely be the one encouraging the team to get up to date with new trends and discoveries, boosting morale and cutting edge solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h8iUuTLXKRZELuQrd1ZtVQ.jpeg" /></figure><p>Apart from these general benefits (which I believe we should never underestimate in a working environment), I see specific advantages psychologists bring to the process of designing within the framework of the Human-Centered Design. Speaking of which, I suggest you read <a href="https://www.amazon.com/Field-Guide-Human-Centered-Design/dp/0991406311">The Field Guide to Human-Centered Design</a>. Additionally, more in-depth reading will lead you to one of the most renown designers in the field of user experience, Donald Norman. To my point that psychologist add to design teams, Norman is both a psychologist and engineer who wrote, <a href="https://www.amazon.it/gp/product/0465050654/ref=as_li_qf_asin_il_tl?ie=UTF8&amp;tag=neu0b-21&amp;creative=21718&amp;linkCode=as2&amp;creativeASIN=0465050654&amp;linkId=ba508a1acd38c2b735547eb6d4f0c7c7">Design of Everyday Things</a>; the preeminent and definitive work on the benefits of cognitive psychology in design. So, here is my personal list of contributions psychologists bring to a design team.</p><h4>10 reasons why you might want a psychologist as part of your design team</h4><ol><li>A psychologist is a great <strong>observer</strong>. This is certainly useful when conducting interviews, user research or usability tests, plus you can use his analytic eye in everyday work activities.</li><li>He’s used to going <strong>under the surface of things</strong>, looking for and noticing aspects that most people take for granted.</li><li>He’s familiar with <strong>cognitive biases</strong> and their consequences. He can easily isolate and question whether a statement is a fact or an assumption.</li><li>A psychologist is often lead by a <strong>healthy curiosity for human beings</strong>’ thoughts, feelings, and <strong>group dynamics</strong>.</li><li>As a scientist, he has a deep knowledge of <strong>research methods and tools</strong>, both qualitative and quantitative. This is why he’s often passionate about field research and collecting people’s feedback and impressions.</li><li>Following the scientific method, he knows the <strong>perils of validating a thesis</strong>: if this is what you’re trying to do, somehow, eventually, you will succeed. Instead, he will try to reject, confute the hypothesis.</li><li>As a scientist, again, he’s very familiar with finding, reading and summarizing <strong>scientific papers and results</strong>. Indeed, if there is any chance that the topic you’ve been working on or studying has already been researched and published, he will find the publication and identify those results important to your current project.</li><li>He can <strong>administer actual personality tests</strong> and use exclusive tools only health professionals have access to (according to norms and policies of the country where he practices).</li><li>A psychologist cares about people <em>before personas </em>but when building and using <strong>personas as a tool</strong>, he can input <strong>introspection</strong>, as well as powerful, coherent and plausible traits to boost the design thinking process.</li><li>He has a clear understanding of people’s <strong>behavioral patterns</strong> and knows techniques that allow the <strong>shaping of habits and actions</strong>. He can implement strategies to help users going from A to B in a natural way.</li></ol><h4>10 + 1 (my favourite)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qCjfJ9WZ22YxbxOE2l-XCA.jpeg" /></figure><p>A cognitive psychologist is an expert —obviously- in the field of human cognition. He <strong>knows and recognizes the normal and abnormal cognitive functioning</strong> regarding perception, attention processes, memory domains, executive functions, language and communication rules and techniques, learning abilities, emotions, creativity, intelligence (and all the others cognitive components).</p><p>When <strong>designing pleasant and usable products he keeps in high regards those biological aspects that define human nature</strong>. He will not ideate or apply solutions that conflict with how the human mind works.</p><p>With so much to offer, it may be tempting to utilize all the new team members skills. Here are some bonus tips regarding what not to ask, or imply when collaborating with a psychologist. In fact, even if he’s a professional psychologist, <strong>his role in agencies or businesses is very different</strong>.</p><h4>What you may not ask a psychologist with a design role</h4><p>First: <strong>You cannot ask for personal clinical and psychological support</strong>. The setting is very different, he’s there with another purpose — which is definitively <em>not therapy</em>. If you need any help and you feel confident about sharing with him your discomfort, he may help you identify another professional psychologist to contact.</p><p>Second: A psychologist is powerful, but not in a special way; <strong>you cannot expect him to read your mind</strong> or understand specific things you’re not willing to share explicitly.</p><h4>Keep in touch</h4><p>If you are curious about my work as a psychologist and designer I’m more than happy to chat with you. As I previously disclaimed I mainly live and work in Italy, so if you want to contribute to this topic with your cultural and personal perspective, or if you are willing to share your experience with such a professional in your team, I’m even happier.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b4af3e0a48f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/idib-group/why-you-need-a-cognitive-psychologist-in-your-design-team-2b4af3e0a48f">Why you need a cognitive psychologist in your design team</a> was originally published in <a href="https://medium.com/idib-group">Idib Group</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Augmented Usability Tests]]></title>
            <link>https://medium.com/idib-group/augmented-usability-tests-b860e3721719?source=rss----4fc15fd5a3ed---4</link>
            <guid isPermaLink="false">https://medium.com/p/b860e3721719</guid>
            <category><![CDATA[augmented-reality]]></category>
            <category><![CDATA[ar]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[usability-testing]]></category>
            <dc:creator><![CDATA[Manu Reggi]]></dc:creator>
            <pubDate>Wed, 28 Nov 2018 16:56:41 GMT</pubDate>
            <atom:updated>2018-11-28T21:50:39.346Z</atom:updated>
            <content:encoded><![CDATA[<h4>What to look for in a usability test for an AR app</h4><h4>TL;DR</h4><p>We’ve conducted some usability tests on <em>Augmented Reality</em> apps and gathered some interesting tendencies in users behaviors here to share them with those developing an AR experience themselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*p9CbDKO31jH4XVJyVNT7IQ@2x.jpeg" /></figure><p>It is often said that 97% of websites offer a bad UX and the situation is not rosier when it comes to apps, especially if they involve <em>Augmented Reality (AR)</em>.</p><p>Lately, we had the chance to run some <em>usability tests</em> on AR apps and we have noticed some tendencies in user behaviors that might help you when developing your AR app.</p><h3>Reality</h3><p>What matters the most in AR is the perception that the user has of what he sees. As long as the illusion of reality stands, the user will enjoy the experience.</p><h4>Transparency</h4><p>One of the main aspects for this illusion to stand is the transparency of the technology involved.</p><p>AR adds, in fact, an extra level of complexity to the interaction with the real world: users have to see it through a mean they don’t normally use to experience it — such as their phone. This additional barrier has to be carefully dealt with when designing this kind of apps as it could make the difference between a useful and a limiting tool.</p><p>It is therefore very important that the world they see around them and the one they see through their phone feel the same. No filters, no effects, no difference.</p><h4>The laws of physics</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x5X8g8eAhyZtHlxqhCY-4A.jpeg" /><figcaption><a href="https://flic.kr/p/GJ4UkD">Photo by Sagie</a>, available under a <a href="https://creativecommons.org/licenses/by-sa/2.0/">Creative Commons Attribution-ShareAlike 2.0 Generic license</a>.</figcaption></figure><p>As for transparency, another aspect that can affect the perception of reality is physics. Physics governs the world around us and all of us know its functioning, much more than we think. When something does not abide the laws of physics, we feel it as unnatural.</p><p>The same thing applies with AR. If we move an object off a table and this object levitates, the illusion is broken: all we are left with is augmentation, but no reality.</p><h3>Scanning the area</h3><p>Reality is a very important aspect, but not the only one. The perception of space, and all processes affected by it, require us to pay particular attention when designing our app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TCvNn_iMxk0VO0eaCjpRAA.png" /><figcaption>Facebook puts a little control on panoramic pictures to help the user orienting himself.</figcaption></figure><h4>Space perception</h4><p>Diversely to the app, which feels the space as a finite set of planes or surfaces, users think of it as infinite: they can move, turn around, even leave the room they are in.</p><p>If you place something around them, they might not be facing it, hence they could ideally walk around for hours before even noticing it at all. Hence, it is very important that you provide your users with some kind of compass to allow them to orient themselves.</p><h4>How much should I scan?</h4><p>Another consequence of perceiving space as infinite is the inability to feel virtual boundaries. It is very important that you provide you users with clear and immediate feedback to help them perceive how much area has been scanned, both while scanning and when trying to move past these boundaries.</p><h4>What should I scan?</h4><p>What we have observed, in this case, is that users tend to point the camera straight in front of them, and not at their feet, even when asked to scan the floor.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F302685341%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F302685341&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F741524720_640.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="640" height="352" frameborder="0" scrolling="no"><a href="https://medium.com/media/9915acaf4ed7989817ca1edbe8bf6273/href">https://medium.com/media/9915acaf4ed7989817ca1edbe8bf6273/href</a></iframe><p>As with all human behaviours, the aim of a good design is not that of changing them, but of exploiting them to offer a frictionless experience. In this particular case, it would be better to design a scanning process that can achieve good results when the user points the camera forward, rather than forcing the user to follow a strict — unnatural — protocol.</p><h3>Controls</h3><p>In your app you might or might not allow your users to place objects in the space around them. If you do, you should make sure of two things: move/rotate controls should always be visible and not hidden by the object itself or anything else, and they should feel natural.</p><h4>Don’t be (too) original</h4><p>All domains have conventions, such as the logo in the top left corner on websites. AR does too, more than you could think. And most of these conventions are inherited from other fields, such as strategy video games.</p><p>For example, think of games as Age of Empires, Civilization or, for those of you who are younger and don’t remember these games, Clash of Clans. It is highly probable that your users are familiar with these games and the controls involved in them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9uPEQ6Zk0cGYrTtAN18CbQ.png" /><figcaption>An example of controls for moving objects used in Clash of Clans.</figcaption></figure><p>So, instead of inventing new controls, which could take time and not necessarily deliver good results, translate these conventions to the AR domain and benefit from them.</p><h3>Tutorial, or not tutorial: that is the question</h3><p>Ah, that is indeed a good question. In general, if your users need a tutorial to understand how your app works, then maybe your app is not that usable after all. But this does not apply to every case, of course. Some apps are not usable, but others are just complex and complexity requires a certain level of guidance to be grasped.</p><p>What we noticed, though, is that users tend to disregard detailed tutorials in favour of learn-by-doing even when it comes to new things such as AR. Our suggestion, then, is the following: if your app is very complex because the context it represents is complex (hence, such complexity cannot be avoided) do include a tutorial; otherwise, spending more time making it usable instead of adding a tutorial is by far the best choice.</p><h3>Test it, test it, test it</h3><p>And, as a last tip, always test your product, not only after you have developed it. You wouldn’t sail an uncharted sea without constantly checking your compass and testing is the best compass you have to check whether your project is still on the right track.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rfUouQvGx4QiQsFQMVnKPw.jpeg" /></figure><p>As to when you should stat testing, I’ll quote Steve Krug when he says</p><blockquote>“start earlier than you think makes sense”.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b860e3721719" width="1" height="1" alt=""><hr><p><a href="https://medium.com/idib-group/augmented-usability-tests-b860e3721719">Augmented Usability Tests</a> was originally published in <a href="https://medium.com/idib-group">Idib Group</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vi racconto il World Usability Day Rome 2018]]></title>
            <link>https://medium.com/idib-group/vi-racconto-il-world-usability-day-rome-2018-1f8d889315f8?source=rss----4fc15fd5a3ed---4</link>
            <guid isPermaLink="false">https://medium.com/p/1f8d889315f8</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Donatella Ruggeri]]></dc:creator>
            <pubDate>Sat, 10 Nov 2018 09:51:23 GMT</pubDate>
            <atom:updated>2018-11-10T10:22:52.572Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RL43on8kCjOjYBFiyzHvIA.jpeg" /><figcaption>Il giorno della conferenza (8 Novembre 2018) al Parco Leonardo.</figcaption></figure><p>Scrivo mentre sono ancora qui, al Parco Leonardo, per paura che le cose ascoltate e viste in questi due giorni sfuggano via dalla mia mente.</p><p>Il <a href="https://www.wudrome.it/">World Usability Day Rome 2018</a> è stato il primo WUD al quale io abbia mai partecipato e stando ai commenti che ho sentito forse uno dei più belli tra quelli che si sono svolti contemporaneamente in Italia e nel mondo, e per questo mi ritengo molto fortunata.</p><p>Due giorni dedicati al design come lo conosciamo e lo amiamo, ma anche come non lo abbiamo mai visto o immaginato.</p><p>Il tema era già stimolante di per se, <em>Design for good or evil</em>, con diverse accezioni che ciascuno degli speaker ha dato e ha portato sul palco. Anche io sono salita sul palco come speaker con un <em>pecha kucha</em>, uno speech di 6 minuti e 40 secondi in cui non ho avuto il controllo delle slide, che cambiavano automaticamente ogni 20 secondi. Faticoso ma divertente!</p><p>Dunque <strong>Design for good</strong>, per bene, o una volta per tutte, o a fin di bene e <strong>Design for evil</strong>, per ingannare l’utente, manipolare la società o per favorire la criminalità.</p><p>Il design è responsabilità, profonda conoscenza dell’ambiente e comprensione delle conseguenze che derivano dalle decisioni che prendiamo. Oserei asserire anche da quelle che non prendiamo e che finiamo col subire, perché anche <strong>non fare alcuna scelta è una posizione</strong> che provoca un outcome.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ewWmXR1RF0X7Ia-gpzQWPg.jpeg" /><figcaption><a href="https://medium.com/u/d5a50199a666">Carlo Frinolli</a>, CEO e Founder di <a href="https://medium.com/u/aaa57cef4a71">nois3</a>.</figcaption></figure><p>La conferenza del primo giorno, introdotta da <a href="https://medium.com/u/d5a50199a666">Carlo Frinolli</a> che è il CEO e founder di <a href="https://www.nois3.it/">Nois3</a>, agenzia organizzatrice dell’evento, ha visto alternarsi speaker internazionali come <a href="https://medium.com/u/4221b3505b52">Cennydd Bowles</a>, che ha parlato dell’<strong>etica della progettazione</strong> e ci ha ricordato che la tecnologia è tutt’altro che neutrale, o <a href="https://medium.com/u/fad7ccb71ce5">Katy Arnold</a>, che ha raccontato come la <strong>fiducia</strong> sia alla base di una <strong>relazione sana e trasparente</strong> tra un governo e i suoi cittadini e ha portato il caso di e-Estonia, la società quasi completamente digitale che ha realizzato, appunto, l’Estonia.</p><p>Di fiducia ha parlato anche <a href="https://www.wudrome.it/speaker/simone-borsci/">Simone Borsci</a>, in particolare guardando ai tre momenti della customer journey: pre-sale, experience e post-sale e portando i dati della sua recente ricerca sul tema. E quando la fiducia viene tradita, in buona o cattiva fede, possiamo invece parlare di <strong>dark patterns</strong>, come ha spiegato <a href="https://www.wudrome.it/speaker/guido-martini/">Guido Martini</a> (<a href="https://medium.com/u/abf3fd7e4bdd">Guimar</a>), con una serie di esempi diabolici di interfacce utente.<br><a href="https://medium.com/u/ae91aba82042">Alessandra Petromilli</a> ha invece trattato un tema emergente, quello delle <strong>Voice User Interfaces</strong>, portando un caso d’uso concreto che ha progettato per Alexa, l’assistente virtuale di Amazon.</p><p>Il pomeriggio ha toccato anche temi forti e a tratti inaspettati. È forse stato la dimostrazione di come si possa progettare bene, a fin di bene, come ha visualizzato <a href="https://medium.com/u/528061c3d4ab">Federica Fragapane</a> attraverso <a href="http://www.storiesbehindaline.com/"><em>The Stories Behind a Line</em></a>, un progetto nato per dare voce alle storie di sei persone arrivate in Italia per richiedere asilo, o l’iniziativa creativa di @<a href="https://www.wudrome.it/speaker/pietro-gregorini/">Pietro Gregorini</a> e il suo gruppo che con <a href="https://www.soloincartolina.it/"><em>Solo in cartolina</em></a> ha coinvolto centinaia di designers a supporto del salvataggio delle vite in mare, dimostrando che <strong>il design può essere reazione, azione, presa di posizione</strong> su temi sociali. Di società e socialità ha parlato anche <a href="https://medium.com/u/12123699389f">Vincenzo Di Maria</a>, presentandoci oltre allo <em>user </em>anche il <em>misuser </em>(che utilizza uno strumento per scopi altri rispetto a quelli previsti) e l’<em>abuser</em> (che utilizza lo strumento per sovvertire le regole della società). Quando progettiamo dobbiamo infatti pensare non solo all’uso che le persone possono fare del prodotto che stiamo mettendo nelle loro mani, ma anche a come questo potrebbe essere impiegato per raggiungere altri outcome, perfino criminosi.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CtdtqD-VwAcDvHvRnwBQgw.jpeg" /></figure><p>Altri speaker d’eccezione, come <a href="https://www.wudrome.it/speaker/dee-scarano/">Dee Scarano</a> (Creating better products, faster with Design Sprints), <a href="https://www.wudrome.it/speaker/stefano-maggiore/">Stefano Maggiore</a> e Omar Campana (Nascondere la complessità per semplificare la vita), <a href="https://www.wudrome.it/speaker/lorenzo-fabbri/">Lorenzo Fabbri</a> (Le parole sono importanti), <a href="https://www.wudrome.it/speaker/daniela-petrillo/">Daniela Petrillo</a> (Progettare una salute accessibile: l’eterna lotta tra la regola e il caos) e <a href="https://medium.com/u/285e91e85f9f">Matteo Cadeddu</a> (Change.org: Human Centered Change) hanno contribuito ad accrescere la consapevolezza sui nostri progetti, portando casi e applicazioni originali e d’ispirazione e ad accompagnarci alla giornata più hands on, quella dei <strong>workshop</strong>, alcuni dei quali hanno registrato il sold out.</p><p>Personalmente ho partecipato al workshop di <a href="https://medium.com/u/161192c913be">Adam StJohn Lawrence</a>, co-autore di <em>This is Service Design Doing</em>, attore e grande facilitatore, con cui abbiamo guardato alla <strong>componente implicita del design</strong>, la quale non è sempre immediatamente percepibile o apparentemente rilevante anche se gioca un ruolo non indifferente per gli utilizzatori dei nostri servizi o all’interno delle aziende.<br>Attraverso una serie di attività poco convenzionali, in tre ore ho sperimentato frustrazione per ciò che non era immediatamente accessibile attraverso il linguaggio, sorpresa per i significati anche molto diversi che ciascun partecipante ha attribuito a una singola scena e la solita meravigliosa sensazione che si prova quando si rimane aperti alla possibilità di cambiare idea o di vedere le cose in un altro modo. Adam ha aperto il workshop proprio dicendo che alcune cose le avremmo portate con noi in modo implicito e così è stato, non è facile da spiegare con le parole.</p><p>Ho provato comunque a usare le parole per raccontare questa edizione del WUD Rome, sperando di aver dato anche solo un’idea dell’aria che si respirava e delle relazioni che si sono create o consolidate, che certamente hanno modificato alcune nostre connessioni cerebrali, come accade quando facciamo una nuova esperienza o apprendiamo qualcosa di nuovo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4AY63H0-MZRq_0ei2p7M7g.jpeg" /></figure><p>PS: nel <a href="https://www.wudrome.it/talk/moral-centered-design-are-we-ready-to-design-for-our-true-selves/">mio speech</a> ho guardato al design dal punto di vista<strong> neuropsicologico</strong>. Ho parlato della necessità di comprendere come funziona il nostro cervello per prendere decisioni e strade che rispecchino come siamo fatti neurobiologicamente e non come crediamo di essere. Ho raccontato della recente vittoria del buon senso, o del <em>design for good</em>, nell’introduzione degli allarmi obbligatori per i seggiolini delle auto in cui è fisiologicamente possibile dimenticare i bambini. La condizione che provoca tale dimenticanza, nota come <em>amnesia dissociativa</em>, è dovuta proprio a come funziona il nostro cervello e la nostra memoria, che in certi casi fa prevalere l’aspetto motorio, procedurale (andare al lavoro) su quella cognitiva (ricordare di portare il piccolo al nido). Se non accettiamo come siamo fatti e se non costruiamo gli oggetti che usiamo sulla scienza umana, biologica, rischiamo di diventare designer diabolici.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f8d889315f8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/idib-group/vi-racconto-il-world-usability-day-rome-2018-1f8d889315f8">Vi racconto il World Usability Day Rome 2018</a> was originally published in <a href="https://medium.com/idib-group">Idib Group</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>