<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:image="http://www.google.com/schemas/sitemap-image/1.1" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:video="http://www.google.com/schemas/sitemap-video/1.1">
  <url>
    <loc>http://www.salliewormer.com/light-gallery</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2017-06-29</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471566288858-BB6TXIF0DZYNNWW1W11W/Screen+Shot+2016-08-18+at+8.24.18+PM.png</image:loc>
      <image:title>Light Gallery - contextual observations</image:title>
      <image:caption>I was curious if people tended to gravitate toward or away from natural light.  I spent several sessions watching behavior in public spaces where there were both windows/outside spaces and places only lit by electric lighting.  I followed up these observations with focus groups to collect specific stories about choices.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471566288858-BB6TXIF0DZYNNWW1W11W/Screen+Shot+2016-08-18+at+8.24.18+PM.png</image:loc>
      <image:title>Light Gallery - contextual observations</image:title>
      <image:caption>I was curious if people tended to gravitate toward or away from natural light.  I spent several sessions watching behavior in public spaces where there were both windows/outside spaces and places only lit by electric lighting.  I followed up these observations with focus groups to collect specific stories about choices.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471573299209-CK80VKRDLM1JNK2C9UJJ/blueberrybuckle.jpg</image:loc>
      <image:title>Light Gallery - focus groups</image:title>
      <image:caption>Further study and observation into the very broad topic of “light” seemed to be taking the project in a different direction, so I needed more information about the quality of light and conscious (or unconscious but self-observed) behaviors around light.  I conducted a series of focus groups (not shown for privacy) with hospitality.  I learned much about the confusion and irritation caused by artificial light.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471562668501-CVFRPHGL0QP90GBEHWT4/3dConcept.jpg</image:loc>
      <image:title>Light Gallery</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471562832797-J34L8BD5RX5G8F3ZLJD4/IMG_1619.jpg</image:loc>
      <image:title>Light Gallery - sketches - light window</image:title>
      <image:caption>If the light wasn't coming from a light bulb, where could it come from?  What would it look like?  If it weren't 'lit', how might that appear?  What other things did I need to think about?</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471564519391-QTB92DBW41A73NBQGECQ/windowmodel.png</image:loc>
      <image:title>Light Gallery - low-fidelity prototype - light window</image:title>
      <image:caption>It's hard to imagine the color of light when you're not a lighting professional.  However, it was significant in the focus groups that the different 'look' of various new light bulbs (LED, CFL, incandescent) was really problematic and frustrating.  This prototype was a 1/8 scale 'window' to demonstrate the difference between normal daylight/solar collection use and night-time or low light programmable lighting source.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471565011784-99O3F61TCA1WNQTCE9O3/3DLUT.jpeg</image:loc>
      <image:title>Light Gallery - sketch - holographic LUT</image:title>
      <image:caption>I truly can't wrap my brain around a 2D light look-up table, which was needed to give users control over the color temperature of the new lighting fixture.  By breaking it down into the appropriate three dimensions, the only thing left is how to display it.  Solution?  3D hologram.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471566017039-51UDEN8GPEBASUT9X99I/HolographicPrototype.png</image:loc>
      <image:title>Light Gallery - prototype - holographic interface</image:title>
      <image:caption>What might an Apple iWatch look like in three projected dimensions?  Would the main interface still be icons?  Does the color temperature representation make any sense at all?  How would text appear, as flat screens or multiple overlays?  Can the eyes' normal depth of focus be utilized?  I had users test these questions and more.  The shape seemed naturally understood but the iconography was a challenge.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/various-gallery</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2022-02-12</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471625553552-NISK6X0HCOWXFS1B4G9Y/BookstoreInfoflow.png</image:loc>
      <image:title>Various Gallery - Course Materials Inventory - Contextual Analysis</image:title>
      <image:caption>As the Director of Digital Learning Services, I was asked to look into our university book ordering process. There were reports of frustration from all sectors - students, faculty, IT and the bookstore. In isolation, no singular process was faulty but holistically they bottle-necked where they converged and created problems for everyone.  Each perspective seemed unwilling to budge, but this map showed that it was a problem for systems thinking to solve. This helped create the impetus for change - no one wanted the students to suffer. Carlow University | Pittsburgh, PA | 2012</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471625553552-NISK6X0HCOWXFS1B4G9Y/BookstoreInfoflow.png</image:loc>
      <image:title>Various Gallery - Course Materials Inventory - Contextual Analysis</image:title>
      <image:caption>As the Director of Digital Learning Services, I was asked to look into our university book ordering process. There were reports of frustration from all sectors - students, faculty, IT and the bookstore. In isolation, no singular process was faulty but holistically they bottle-necked where they converged and created problems for everyone.  Each perspective seemed unwilling to budge, but this map showed that it was a problem for systems thinking to solve. This helped create the impetus for change - no one wanted the students to suffer. Carlow University | Pittsburgh, PA | 2012</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1644692146534-15C7SL5PX2MNXB2J6YZA/YMAP-elevatorpitch-graphicnovel.png</image:loc>
      <image:title>Various Gallery - Youth Media - Instructional Design</image:title>
      <image:caption>The Youth Media Advocacy Project (YMAP) pairs university communication majors with high school classes in under-served districts which often lack consistent classroom technology.  The elevator speech lesson was originally conceived as a video, but I opted to design and create a graphic novel to mediate in-class technology instability. Using actual images of previous students (with permission) was well received by the current students. The project was part of a year long curriculum stabilization project that I oversaw. YMAP @ Carlow University | Pittsburgh, PA | 2016</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471652142858-N0P3PQ6PSSNRJZC0YTRM/IRB-workflow.png</image:loc>
      <image:title>Various Gallery - Optimizing Intranet - Workflow Design</image:title>
      <image:caption>One of my responsibilities at Carlow was optimizing our SharePoint intranet.  Typically what this meant was creating and outfitting team sites to fit each team's needs and team members’ tech savviness.  Occasionally I got to dig into InfoPath and SharePoint Designer when form-related workflows were needed;  this was the case of the Institutional Review Board (IRB) proposal submission and review process.  I redesigned the proposal form to make it more usable, then built a multi-phase multi-condition workflow.  Throughout I solicited user feedback through iterative testing to make sure things were working 'as expected.' IRB @ Carlow University | Pittsburgh, PA | 2015</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471653777270-X1S7Z9PVLF0AS9E43KWY/WebConf.png</image:loc>
      <image:title>Various Gallery - Multi-User Systems - Decision Making</image:title>
      <image:caption>Rarely do organizations get to design their ideal solutions from scratch, and too often purchased solutions are chosen for reasons that don’t include actual user needs.  Over my career, I've been quite vocal about ensuring user voices are meaningfully included in decision making.  To me, that includes co-establishing the key features to evaluate through observation, conversation and/or discussing primary tasks with users.  The relative criticality of each feature is also necessary to understand, as buying or building solutions typically means compromise.  This example shows the criteria elicited from faculty for a new video conferencing solution, and their aggregated and weighted perceptions how each product (in columns) stacked up.  Carlow University | Pittsburgh, PA | 2012</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471717476796-86YOSW13X38LB8AYEGQB/task-analysis-scrubbed.png</image:loc>
      <image:title>Various Gallery - Customer Support Site - Heuristic Review and Usability</image:title>
      <image:caption>As part of an intranet support site for a large CRM vendor, we first conducted a heuristic analysis to inform our user testing tasks.  A primary hypothesis to test was that the navigation was the most problematic feature of the site.  This sample shows how much each participant chose to use either search or navigation (or change strategies), how many tasks they then reached, and how successful they ultimately were.  In addition to being the team lead, I took a major role in designing the user testing tasks and moderator's guide.  Client:  Pegasystems | Cambridge, MA | 2016</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471634303742-3H6XZFHJEX2Q9BX4LH8S/Persona-CombinedVectors.png</image:loc>
      <image:title>Various Gallery - Community Building - Diary Study</image:title>
      <image:caption>Participants in a diary study about online technical community usage clustered at different points on the study's behavioral vectors.  By splitting the clusters into two personas - a seasoned veteran and a hungry young developer - the results suddenly made much more sense.  Solo hands-on research project for Field Methods course. Client:  Pegasystems | Cambridge, MA | 2016</image:caption>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/koyagallery</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2016-08-19</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471470798781-BPMRGZC9V3VYH465RK07/KOYA-wrist-mode-sm.png</image:loc>
      <image:title>KOYA Gallery</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471468977161-S1PF7LLY049QRLPIYP3W/Persona_Kris_Olga_Sallie.png</image:loc>
      <image:title>KOYA Gallery - Persona</image:title>
      <image:caption>After interviewing several people, we developed this primary persona.  It looks as awesome as it does thanks to our team graphic designer, Kris.  In addition to conducting some of the interviews, I wrote the primary quote, contributed to the rest of the text, and sourced most of the photos.  </image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471468705301-YZ757HN4D0W81RKMO4TB/Koya-sketch-mtg.png</image:loc>
      <image:title>KOYA Gallery - Sketch - Meetings</image:title>
      <image:caption>I'm not an artist, but sometimes rough sketches help me think.  As meetings are the bane of almost everyone's existence, the question I was exploring was how socially and physically awkward would it be to use KOYA during a meeting?</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471468706886-WGEP53P9VE937E65KDYV/Koya-sketch-immersive.png</image:loc>
      <image:title>KOYA Gallery - Sketch - Immersion</image:title>
      <image:caption>At the beginning, we toyed with creating an immersive environment.  Based on interviews, this was less of a priority, (thankfully as it is likely not technically feasible yet!), so we left this feature for a 'future iteration.'</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471561822083-1A3VYGU647B8JR32KYO9/koyastoryboard.png</image:loc>
      <image:title>KOYA Gallery - Context Scenario</image:title>
      <image:caption>I created this early story of our persona's journey in storyboard form (using a demo of StoryboardThat).  Clearly we were still in the magical thinking phase, here.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471468706247-069S9YWAD4PO0EXIUWUG/Koya-sketch-bio.png</image:loc>
      <image:title>KOYA Gallery - Sketch - Biorhythms</image:title>
      <image:caption>This sketch came about after researching viable accupressure and pulse points.  What would the user need to do to detect and mediate her/his biofeedback?  Where could KOYA be positioned and what does that implicate for the form factor?</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471468704581-HE4S2KP7W0IYGMH7VMNS/Koya-keychain-sketches.png</image:loc>
      <image:title>KOYA Gallery - Sketch - Road Use</image:title>
      <image:caption>As our interviewees noted driving was a stressor, we brainstormed a 'keychain' as a possible form factor.  I wasn't able to imagine any safe way this could be used....</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471466686352-8VMTKPLC5W5RVRHZTOAA/koya-sizing.jpeg</image:loc>
      <image:title>KOYA Gallery - Really Rough - Size and Shape</image:title>
      <image:caption>Once we determined the wrist was a viable option, we needed to determine a size and shape range.  That way, we would know roughly how much room we had for controls.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471465983412-H4PXZAD7A1X63S9CYTC7/KOYA-alerts.png</image:loc>
      <image:title>KOYA Gallery</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471467998934-ZO6N1T02CSEOENKHSOGZ/koyaoptions.jpg</image:loc>
      <image:title>KOYA Gallery - Sketches - Shape and Features</image:title>
      <image:caption>Once we had a rough size in mind, I switched to PowerPoint to mock up some sketches and ideas for conversation.  We tried using Trello at this point, but the virtual bulletin board was a little rough going when trying to point out specifics.  These gave us a better starting point.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471561821798-T4BSNRRGU2UMGR7BIY41/KOYA-infoflow.png</image:loc>
      <image:title>KOYA Gallery - Information Flow</image:title>
      <image:caption>My main contribution to the app was to think about how our screens might be connected and flow from one to the other.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471466741205-S2Q27BYGYPSPYPN47F0O/KoyaPaperPrototype.JPG</image:loc>
      <image:title>KOYA Gallery - LowFi Paper Prototype</image:title>
      <image:caption>Is it really feasible to use as many 'buttons' as we're thinking?  Is there enough space to differentiate?</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471466315199-04PAE3AVR2HENKQ4SMJX/KOYA-wrist-mode-sm.png</image:loc>
      <image:title>KOYA Gallery - Medium Fidelity Wearable</image:title>
      <image:caption>I used Fimo clay and jewelry fixings to mock up a physical prototype.  The raised buttons and lights do not work, but were useful for initial user testing and to begin to explore the following questions: Are the shapes and sizes of the buttons feasible?  Are they understandable by touch only?</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471466394914-FFDV3CX68H9GHY8DEDJU/KOYA-necklace-mode-sm.png</image:loc>
      <image:title>KOYA Gallery - 'Necklace Mode'</image:title>
      <image:caption>This is the same shape as the wrist version, but switched to a chain.  After watching our actress during the protocast filming, I became less convinced that this could actually capture decent breathing and/or heart rates.  With normal human movement (walking, sitting, standing, leaning) the device certainly disengages from the target area.  There are some devices on the market that claim to do this, though.... interesting....</image:caption>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/tagged-gallery</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2022-02-12</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1497398755876-5OUWJJL8GC0OGS90VM7R/Slide3.jpg</image:loc>
      <image:title>Tagged Gallery - PaaS Beyond Disruption - Customer Experience Design</image:title>
      <image:caption>Combining qualitative and competitive research with usage data analysis, we designed and presented a scalable kid-glove-care service design to help the client regain their competitive advantage.  Remote team course project for User Experience and Leadership Management. Client:  Confidential PaaS provider | San Francisco, CA | 2016</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1497398755876-5OUWJJL8GC0OGS90VM7R/Slide3.jpg</image:loc>
      <image:title>Tagged Gallery - PaaS Beyond Disruption - Customer Experience Design</image:title>
      <image:caption>Combining qualitative and competitive research with usage data analysis, we designed and presented a scalable kid-glove-care service design to help the client regain their competitive advantage.  Remote team course project for User Experience and Leadership Management. Client:  Confidential PaaS provider | San Francisco, CA | 2016</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1497407038488-48QO3OKKAV6BA7UIIGAH/diarystudy-vectors.png</image:loc>
      <image:title>Tagged Gallery - Community Building - Diary Study</image:title>
      <image:caption>Participants in a diary study about online technical community usage clustered at different points on behavioral vectors.  By splitting the clusters into two personas - a seasoned veteran and a hungry young developer - the results suddenly made much more sense.  Solo research project for Field Methods course. Client:  Pegasystems | Cambridge, MA | 2016</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1497399408782-U4PDTE9CXQ6CVNRWNC2X/IRB-workflow.png</image:loc>
      <image:title>Tagged Gallery - Optimizing Intranet - Workflow Design</image:title>
      <image:caption>By shifting the focus to users' abilities and goals over content, I increased intranet usage six-fold.  As an example, after analyzing the Institutional Review Board's (IRB) process, I automated their proposal submission/review using a multi-phase multi-condition workflow.  This included redesigning the proposal form and soliciting usability feedback with iterative testing. IRB @ Carlow University | Pittsburgh, PA | 2015  </image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498695531548-QH1E9V3GUJNALDWHMI6X/YMAP-elevatorpitch-graphicnovel.png</image:loc>
      <image:title>Tagged Gallery - Youth Media - Instructional Design</image:title>
      <image:caption>The Youth Media Advocacy Project (YMAP) pairs university communication majors with high school classes in under-served districts which often lack consistent classroom technology.  The elevator speech lesson was originally conceived as a video, but I opted to design and create a graphic novel using actual images of the students. It was well received by the students, and was part of a year long curriculum stabilization project that I oversaw. YMAP @ Carlow University | Pittsburgh, PA | 2016</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1497400669612-V123RUEA5YJ9MNFIBC2B/BookstoreInfoflow.png</image:loc>
      <image:title>Tagged Gallery - Book Ordering - Contextual Analysis</image:title>
      <image:caption>There was frustration about ordering course books from all sectors at our institution. By observing behavior and asking questions, I was able to document the collective processes and show that it was a problem for systems thinking to solve. Carlow University | Pittsburgh, PA | 2012</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498696315952-L9DOSIYTJFGACDDE03NW/extract-designreviewF1console.png</image:loc>
      <image:title>Tagged Gallery - Formula 1 - Physical Design Review</image:title>
      <image:caption>Performance racing requires fast decision making and continual situation awareness under extreme physical conditions - a heavy cognitive load for sure.  As even our regular cars seem to be getting overly complicated, this design review looked at a racing steering console under the framework of working memory. Foundations in Human Factors solo course project. Client: none</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498697387167-MRHXQ3JRQB61AF12DO1S/JellyNoteBeforeAfter.png</image:loc>
      <image:title>Tagged Gallery - Unusable Music - Site Redesign</image:title>
      <image:caption>As a musician I'm often looking for 'chords in all the wrong places.'  This site needed serious help.  After a heuristic evaluation, I sketched a redesign to move the main menu so it doesn't look like it's part of the logo, co-locate and align related functions, eliminate redundant information, change the transposition control from a slider to a drop down (singers can't use 'relative' changes), make hidden-but-essential tools visible, keep sizes uniform, think about changing color palette (not shown) to reduce salience on unimportant things, and the list goes on.  Client: none | 2016  </image:caption>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/wmsd-mixed-methods</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2026-03-12</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1772047244353-GFLAXWBMXCGUL1MID57E/Timeline.jpg</image:loc>
      <image:title>WMSD Mixed Methods</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1772047244353-GFLAXWBMXCGUL1MID57E/Timeline.jpg</image:loc>
      <image:title>WMSD Mixed Methods - Timeline of multi-methods</image:title>
      <image:caption>Green - Research-led activities were planned and conducted by me, such as the technical SME interviews which informed surveys and additional customer interviews. White - Research-consulted activities, such as the focus group or analytics questions to answer, were informed or designed by research but led by others. Grey - Research-requested independent activities, such as the C360 analysis, were nudged into action without oversight. Because we were able to marshal the troops, we were able to accomplish the data collection in an abbreviated time frame.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1772047242625-1XQQSVDLZCVYWT47VOFP/Overall+Research+Questions.png</image:loc>
      <image:title>WMSD Mixed Methods - Primary research agenda questions</image:title>
      <image:caption>Each of these questions required different (or multiple) methods. The overall agenda was designed so that findings from individual studies informed the design of subsequent inquiries.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1772047243729-YWLB8ZL1PZF5SZ1EGOLA/Phase+of+Research.png</image:loc>
      <image:title>WMSD Mixed Methods</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1772047241894-XV928Q9KDDPZ0FBSW502/Comparitive+Surveys.png</image:loc>
      <image:title>WMSD Mixed Methods - Sample from analysis deck of prospect vs buyer surveys</image:title>
      <image:caption>While our analysts are very happy working with the raw numbers, the designers and PMs needed something more visual to anchor on. We threw together a side by side reference deck, and annotated statistically significant (and interesting) differences. We also split results by business size and role/department of respondent within their organization to better uncover potential ICP attributes for our marketing team.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1772047241590-41EQO5POLA6CAI3IRWLU/Interview+Analysis.png</image:loc>
      <image:title>WMSD Mixed Methods - Thematic clustering of SME, prospect and buyer interviews</image:title>
      <image:caption>The analysis is structured by study question, then clustered by emerging themes. Color coding exact quotes by participant and then grouping by theme creates a quick visual heat map, without falling into the loudest-voice trap (all quotes/themes generated by the same person).</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1772047239278-E20JCXRXCJRL74OILH4R/Readout+extract+-+framework.png</image:loc>
      <image:title>WMSD Mixed Methods - Sample from final readout - vicious vs virtuous cycles</image:title>
      <image:caption>This was animated in the deck. The virtuous cycle appeared first with an easy green loop, then all of the drop-off points came in at an accelerating pace with each risk-to-the-buyer clearly labeled. It was important for the team to not generalize “risk” here, as each barrier might need a different solution, or solving one easy problem might not change the overall equation. The team workshop dissected and prioritized what would be on the roadmap.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1772047239316-MFM3QU9T2PB8ID4QJU40/Readout+extract-qual.png</image:loc>
      <image:title>WMSD Mixed Methods - Sample from final readout - how quotes were used</image:title>
      <image:caption>Getting precise and explicit was critical for the readout’s audience, without getting too heavy. Consider this analogy: “Java is to Javascript like ham is to hamster.” Why did this matter? Over-summarization and a lack of technical clarity in prior research had impeded the team, so a combination of plain language and explicit quotes from the technical participants allowed both designers and engineers to share meaning for this vertical, without losing sight of the big picture for the marketing team.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1772047240502-0XLYFGBSHJZZZDLHIKBX/Personas+and+Use+Cases.png</image:loc>
      <image:title>WMSD Mixed Methods - Sample deliverable - personas and use cases</image:title>
      <image:caption>Specifically for the marketing team, primary and secondary personas were created with existing successful use cases. Prior marketing over-simplified the category to “web development”, which attracted only uninformed and less valuable buyers.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1772047240637-W72E2JB9RRT256I68V1M/Workshop.png</image:loc>
      <image:title>WMSD Mixed Methods - How did the team absorb all this information?  Workshop the data!</image:title>
      <image:caption>For the core team responsible for setting strategy and the roadmap, we held a multi-day workshop to dive more deeply into findings from all tracks (vs. the summary readout). The Miro was active for the entire workshop and participants were encouraged to add notes, ideas and unanswered questions during and after each session.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1772053602734-51V79ZCN9O7GOPHV1KER/Team.png</image:loc>
      <image:title>WMSD Mixed Methods - DACI team by role</image:title>
      <image:caption>This was one of the largest and compressed research agendas I’ve led, and its success was due to all of the participants who were engaged, curious, collaborative, responsive and excited about what we were learning. This study snowballed in interest and impact along the way, so a huge shout out needs to go to the lead PM Nat who not only was an invaluable partner and sounding board, but helped wrangle and engage everyone outside the core team.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/qual-samples</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2026-03-12</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/fa5cf572-e32a-419e-8301-d64d014ca78a/MiroExample-precoding-servicemodelsurvey.png</image:loc>
      <image:title>Qual Samples - Sample - pre-coding on multiple dimensions, survey results</image:title>
      <image:caption>Miro is a great tool to identify themes from qualitative responses in surveys and thick data. Here we were examining a sample set of the survey open-ended responses and looking at multiple dimensions identified in the interview portion of this mixed methods study (problem type, journey point, etc.) Ultimately, we uncovered four primary “buckets” that drove need, criticality and behavior when the responses were tagged and quantified.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/fa5cf572-e32a-419e-8301-d64d014ca78a/MiroExample-precoding-servicemodelsurvey.png</image:loc>
      <image:title>Qual Samples - Sample - pre-coding on multiple dimensions, survey results</image:title>
      <image:caption>Miro is a great tool to identify themes from qualitative responses in surveys and thick data. Here we were examining a sample set of the survey open-ended responses and looking at multiple dimensions identified in the interview portion of this mixed methods study (problem type, journey point, etc.) Ultimately, we uncovered four primary “buckets” that drove need, criticality and behavior when the responses were tagged and quantified.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1772047241590-41EQO5POLA6CAI3IRWLU/Interview+Analysis.png</image:loc>
      <image:title>Qual Samples - Miro for discovery interviews</image:title>
      <image:caption>Another coding and analysis example, using colors to identify interviewees (vs. themes) and affinity mapping. By using Miro this way, the team can quickly find areas of interest to get moving before the final deliverable is ready. In smaller n studies (aka less than the color limit in Miro), color coding participants helps avoid what I call the “loud mouth” bias many UXRs are susceptible to, where one passionate and eloquent participant drives all the quotes and themes. This way, it’s quick and easy to see what emerges across multiple participants vs. a single voice.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1497399408782-U4PDTE9CXQ6CVNRWNC2X/IRB-workflow.png</image:loc>
      <image:title>Qual Samples - Sample (older) - InfoPath workflow technical documentation</image:title>
      <image:caption>Carlow’s IRB was manually processed with various paper forms (!) and multiple approval steps, creating bottlenecks at the secretary’s desk who ‘owned’ it. Often this resulted in duplicate work as various forms and approvals got inevitably lost ‘in the mail’ or on someone’s desk or were sent to the wrong person. Automating this process required working with faculty to codify the user types, the research types, and the conditional approval points which were dependent on the user-type and type of research to be done. The first part of the project required mapping out all conditions, rebuilding the request forms into a shared structured data set, and then coding the process in SharePoint via InfoPath. The documentation (shown here) was as much sanity checking for myself during building and QA as it was for future admins who might need to adjust anything, should the IRB alter its process.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/home</loc>
    <changefreq>daily</changefreq>
    <priority>1.0</priority>
    <lastmod>2013-01-30</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471719904207-PFUX34662Y5GIVFEBDSQ/fallwater-crop2.png</image:loc>
      <image:title>Home</image:title>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/rethinking-light</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2017-06-29</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471720660503-9PQ9YABFKPOPGF9YHM0E/3dPrototype-2.jpg</image:loc>
      <image:title>Rethinking Light</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498768444909-B5J1C29UNL5QFSOH38OL/image-asset.png</image:loc>
      <image:title>Rethinking Light</image:title>
      <image:caption>The challenge of creating a 3D light look-up table as a low-fi prototype.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/various</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2022-02-12</lastmod>
  </url>
  <url>
    <loc>http://www.salliewormer.com/contact</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2026-02-24</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471720905141-7QV5PME4JKD4Q9X3DC0R/Dogwood.jpg</image:loc>
      <image:title>Contact</image:title>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/perspective</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2026-03-25</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471720835172-DLKQUPIV2GID8PYKLFNN/seb.jpg</image:loc>
      <image:title>Perspective</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471446479158-T6TVUAC3PXIYXJ7PNANU/image-asset.jpeg</image:loc>
      <image:title>Perspective</image:title>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/mindfulness</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2017-06-29</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471720710660-6XC0W26MR9XWOX63TJA1/KOYA-wrist-mode-sm.png</image:loc>
      <image:title>Mindfulness Wearable</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1483822845044-NHGO3383PQYAYBSYDP8P/Persona_Kris_Olga_Sallie.png</image:loc>
      <image:title>Mindfulness Wearable</image:title>
      <image:caption>Primary persona of Autumn, a working professional with multiple roles and responsibilities.  Images include her "happy place", which became inspiration for visual design elements.  The content was collaboratively developed, although the final layout and design was another team member's contribution.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1483823131579-8BN5YZLNXX0BSFCK7CCO/image-asset.png</image:loc>
      <image:title>Mindfulness Wearable</image:title>
      <image:caption>Early context scenario includes meetings, family interruptions at inopportune times, and immersive-type remediation.  During the design process and based on further interviews, research and testing, we streamlined and clarified our initial ideas.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1483833801547-ULRBS9I32F4YJF6R1H6Z/KOYA-formfactor-sketches.jpg</image:loc>
      <image:title>Mindfulness Wearable</image:title>
      <image:caption>Sketches helped us investigate some key questions.  How socially and physically awkward would it be to use KOYA during a meeting? What would the user need to do to detect and mediate her/his biofeedback?  Where could KOYA be positioned and what does that implicate for the form factor?  Is it possible to safely use while driving?</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1483834030790-6YQGYREVNXKZTDQC5ZHS/KOYA-sketches-shape.jpg</image:loc>
      <image:title>Mindfulness Wearable</image:title>
      <image:caption>We also explored various shapes.  At this point, we had made the design decision to make the device look something like jewelry using themes from our branding, to minimize its technical nature without hiding it completely and making it difficult or awkward to use.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1483837922138-URMGST9SY0QRKKBJLDGX/KOYA-infoflow.png</image:loc>
      <image:title>Mindfulness Wearable</image:title>
      <image:caption>High-level information architecture showing flow between screens, device and other smartphone applications.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1483837250136-1WRY8EFNL0717LQHKFK2/KOYA-lofi.jpg</image:loc>
      <image:title>Mindfulness Wearable</image:title>
      <image:caption>Low fidelity prototypes helped test size and placement hypotheses without costly commitment.  For example, is there enough space to differentiate one shape from another?</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1484075469357-LRHJWB9DUHOIRSAZVODU/KOYA-finalwearableprototype.png</image:loc>
      <image:title>Mindfulness Wearable</image:title>
      <image:caption>Final physical prototype shown in three variations.  Clickthrough to watch the protocast on Vimeo.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1484075546872-E5IJYMEYHNBQTJT8M69B/KOYA-finalapp-prototype.png</image:loc>
      <image:title>Mindfulness Wearable</image:title>
      <image:caption>The final app icon, logo, home screen and a sample screen showing the tracking of patterns over a week's time period.  Clickthrough to view all Axure files.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/mobile-portal</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2017-06-29</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1490820997353-5922U5GFO2TBH3SF9BFL/final-contextscenario.png</image:loc>
      <image:title>Mobile Portal</image:title>
      <image:caption>Final context scenario showing access in various campus locations throughout the initial use.  As being an 'ambassador' can still feel murky and vague, we wanted to ensure growing confidence and ease.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1490820094352-JTC1ITAATKFWK01FGWUN/image-asset.png</image:loc>
      <image:title>Mobile Portal</image:title>
      <image:caption>These early sketches show some key ambassador frustrations - overwhelming amounts of information, a user community unfriendly to learning students, logistical challenges - and how a helpful IUI might mediate those into a more positive experience.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1490561735941-6Z3FRGO79XRPH9R1IJHM/image-asset.jpeg</image:loc>
      <image:title>Mobile Portal</image:title>
      <image:caption>Our system persona explored the perfect ambassadorial assistant to an engineering student.  When we boiled the tasks down to just the most essential and re-examined the scale for this project, we realized we did not need to go that far.  We did keep helpful, right-time-and-right-place attributes in the interface's posture, however.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1490560906976-WO2JBXO13IF6CFSBD164/image-asset.png</image:loc>
      <image:title>Mobile Portal</image:title>
      <image:caption>This version of the task analysis was too complicated, but it did help us see the intersections of all three personas with the tasks.  The big bubbles are different situation/need contexts, linking back to key points in the overall event flow.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1490820338894-SPZESV670LEOTPAJIPNJ/map-wireframes.jpg</image:loc>
      <image:title>Mobile Portal</image:title>
      <image:caption>As we simplified our tasks and workflow, we simplified our wire frames through various desktop and web versions.  It was an easy step from the last card-type Balsamiq version to mobile.  The left image on the bottom also a view a student attendee might see and provides access to sharable parts of the ambassador's event kit.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1490820756501-3UWRHLCHOKF42JU3AW46/simple-IA.jpg</image:loc>
      <image:title>Mobile Portal</image:title>
      <image:caption>Almost final architecture, showing how the three main containers relate to each other.  Ambassadors and students come in at the "My" level, with personalized information based on role, major, event attendance, or custom groupings.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1490822385185-JFQCUO0Q7LUSUIGMN03Y/image-asset.png</image:loc>
      <image:title>Mobile Portal</image:title>
      <image:caption>In the final prototype, we made one adjustment to our architecture and split out scheduled events from the event kit library.  This is a sample of our final working screens, from the to-list at the left, through a task, into the scheduled events list, with detail of the kit, and ending in the community..</image:caption>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/archive</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2022-02-12</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1497404105247-OB26YTM4MG9483BE1NIA/image-asset.png</image:loc>
      <image:title>Older Work</image:title>
      <image:caption>Excerpt of final bot-human relationship building architecture.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1497365143689-BBAUSZEPWIT7NDXZ6O4J/3dPrototype-2.jpg</image:loc>
      <image:title>Older Work</image:title>
      <image:caption>3D Holographic LUT controller concept.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1497404000584-X70HH7UYK45PKW25607Y/image-asset.png</image:loc>
      <image:title>Older Work</image:title>
      <image:caption>Mindfulness physical prototype, as shown in protocast.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1497365392644-PPIG1NEBWIHD5X93LX3Y/image-asset.png</image:loc>
      <image:title>Older Work</image:title>
      <image:caption>An early task-by-user analysis. Looking for the "in" to the concept.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/ai-relationships</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2017-06-29</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1471720710660-6XC0W26MR9XWOX63TJA1/KOYA-wrist-mode-sm.png</image:loc>
      <image:title>AI Relationships</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1497317155003-35LLZNGIZVZ51JHXY0UR/image-asset.png</image:loc>
      <image:title>AI Relationships</image:title>
      <image:caption>Meet Riley.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498685770758-XRSYXNEU23KETL0VSFVG/Goals-Diagram.png</image:loc>
      <image:title>AI Relationships</image:title>
      <image:caption>Slide from our final presentation demonstrating the increasing complexity of a relationship over time.  See the complete presentation here.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498247440790-A6TGHOB4X4C8KLR2HPN0/image-asset.png</image:loc>
      <image:title>AI Relationships</image:title>
      <image:caption>Early collection of key elements into an affinity map from our research.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498766798649-U2A7G9OB3UVW1EAY6QI7/relationship-type-sketches.png</image:loc>
      <image:title>AI Relationships</image:title>
      <image:caption>Some of my sketches exploring relationships with a bot using (clockwise from top left) various degrees of connection, Fiske's model, and a very early personality attunement idea.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498244704584-HEZGS2Z6IXDJDTAENIMS/Persona_briefs.png</image:loc>
      <image:title>AI Relationships</image:title>
      <image:caption>Three possible personality types, eventually narrowed to two.  We realized the steady personality would get along in any situation, and not provide much meaningful insight.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498322785746-Y5M1JGPJI6R64DPWQXUC/stage-model.jpg</image:loc>
      <image:title>AI Relationships</image:title>
      <image:caption>Early 'sketch' of relational stages, showing shared goals and activities, with relationship-enhancing and relationship-destroying behaviors.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498323921403-A3XHO0CJ5IZKB5OW7P8H/rel-overtime.jpg</image:loc>
      <image:title>AI Relationships</image:title>
      <image:caption>How might a relationship with a bot evolve over time?  And what questions (data/actions generated) might occur?  How could the human's emotions change, and could the bot 'show' emotion with just text?</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498685333913-CIXB5SVXV662AU6SYEAI/snippets-analytic.png</image:loc>
      <image:title>AI Relationships</image:title>
      <image:caption>Sample of conversational 'snippets' of an analytic-type bot.  Iin general, an analytic bot style provides data, details, structure, and next steps with less emotion, while a creative bot style shows emotion with lots of emojis, inspires users to reach big goals, and helps the user move through ideas quickly.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498682548061-F9EHFW5I4Z0V7LS7N50V/image-asset.png</image:loc>
      <image:title>AI Relationships</image:title>
      <image:caption>Wizard of Oz testing for a scenario farther into "Olga's" and Riley's relationship.  Here Riley is taking initiative by reminding the user of an upcoming milestone, and offering to provide resources associated with that milestone.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498682424279-L8FGSKJYDVYK43AXCHNM/image-asset.png</image:loc>
      <image:title>AI Relationships</image:title>
      <image:caption>Wizard of Oz scenario showing initial introduction.  "Olga's" conversation was unscripted, while the operator for Riley had to rely on the snippets we had prepared in advance.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498683720585-MTUCPGEHFNDCK4XZ5KPD/image-asset.png</image:loc>
      <image:title>AI Relationships</image:title>
      <image:caption>Final prototype 'interface' in an initial relationship scenario, showing possible interaction with different analysis engines, knowledge bases and outside resources.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498683896621-3UPJ5ZF9BS81DBXKA3WY/image-asset.png</image:loc>
      <image:title>AI Relationships</image:title>
      <image:caption>Prototype in a later interaction scenario, activating different potential elements.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/1498684046898-FWCQ97Y8PINMNVHKDAKO/riley-Bayesian-architecture.png</image:loc>
      <image:title>AI Relationships</image:title>
      <image:caption>Final architecture and processing flow for a relationship-building intelligent agent.  1) User input parsed. 2) Context, Language and Sentiment Knowledge Bases (KB) compare with known data.  3) Temporary (combined) variables are populated in User Inference Engine or sent for clarification. 4) User Inference Engine evaluates if new or previously used and if successful.  5) Personality KB initiates action on instruction from User KB. 6) Bot Style KB uses history from User KB and Personality variable to determine correct response.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>http://www.salliewormer.com/latestwork</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2026-03-11</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/553471e9-cd89-49d9-8230-9fe5b41ad58d/WMSD+Timeline.jpg</image:loc>
      <image:title>Portfolio</image:title>
      <image:caption>Outline of learning agenda.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/4750dd55-9634-4c22-b7ed-ad476aca168e/Learning+Agenda+%28Design+share%29.png</image:loc>
      <image:title>Portfolio - Make it stand out</image:title>
      <image:caption>Summary (slide) of visitor site strategy, prior to implementation.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/89dfacfb-f554-40f4-9a7a-da80acc986bb/Talent+Segmentation+Infographic.jpg</image:loc>
      <image:title>Portfolio - Make it stand out</image:title>
      <image:caption>Infographic from attitudinal segmentation study.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/8cbabe51-731a-4822-9656-4151eb20fe3f/Talent_JtbD_Overview.jpg</image:loc>
      <image:title>Portfolio - Make it stand out</image:title>
      <image:caption>Talent jobs-to-be-done framework in readout.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/4c6e66d1-655e-486c-b0fe-13de1590763f/Sample_ServiceEcosystem.png</image:loc>
      <image:title>Portfolio - Make it stand out</image:title>
      <image:caption>Map of overlapping support solutions and access points.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/6dcc0ba5-d079-48e2-83b8-64eef355b817/Grower+E2E+Scenario%3ATask+Evaluative.png</image:loc>
      <image:title>Portfolio - Make it stand out</image:title>
      <image:caption>E2E analysis with task success rubric. User group 1.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/57b479b5d2b8577c962210cb/ef5d9f70-16f2-4e52-90ee-a8a262795b21/UXMetrics-prelim.png</image:loc>
      <image:title>Portfolio</image:title>
      <image:caption>‘Map’ of existing and proposed UX metrics.</image:caption>
    </image:image>
  </url>
</urlset>

