<?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>https://www.holderux.com/home</loc>
    <changefreq>daily</changefreq>
    <priority>1.0</priority>
    <lastmod>2026-06-04</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/428da82c-3c5f-4244-b22b-6ab6906c04aa/EA-Flow-splash-rev-cond02.png</image:loc>
    </image:image>
  </url>
  <url>
    <loc>https://www.holderux.com/work</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2026-06-02</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/1adbe811-563e-4cb7-928a-1b1d35e5a201/thumb-claims.png</image:loc>
      <image:title>Use Cases</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/4370d263-6fbb-4ac4-aae9-d54c4d9e5ebf/thumb-fixfund.png</image:loc>
      <image:title>Use Cases</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/8770f9dd-02d4-4c80-a552-7f935f0c0424/thumb-proscomm.png</image:loc>
      <image:title>Use Cases</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/bfaa2c2d-b7e7-4528-932e-90d69cd1e7d2/thumb-calc.png</image:loc>
      <image:title>Use Cases</image:title>
    </image:image>
  </url>
  <url>
    <loc>https://www.holderux.com/experience</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2026-06-02</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/e6427612-9f9e-4fc4-846b-aa8274beb519/menetta01.png</image:loc>
    </image:image>
  </url>
  <url>
    <loc>https://www.holderux.com/work/mobilewires</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2023-06-02</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/1e3537d7-45b0-4fea-ac03-d2ce6ba56d9f/FFO03a.png</image:loc>
      <image:title>Mobile Wires</image:title>
      <image:caption>Start with blocking each distinct area or module and add general labels for titles, copy, functions, etc.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/3db30f47-bc70-44b6-8ba1-8871922a4295/FFO03b.png</image:loc>
      <image:title>Mobile Wires</image:title>
      <image:caption>Progress by adding general function details and define collapsible modules. Add further definition of content.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/779c4feb-1143-41e5-b0e8-1647bbd05257/FFO03c.png</image:loc>
      <image:title>Mobile Wires</image:title>
      <image:caption>Remove blocking for hi-res wires. These are used most often when designer-created comps are skipped in favor of an automated, style-guide enabled creation system.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.holderux.com/work/flowanalysis</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2023-06-08</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/b4cb2425-a12c-4a5d-ab3d-5a2d80dd6d5c/1PComm-intro_mask.png</image:loc>
      <image:title>Flow Analysis of Communications Strategy</image:title>
      <image:caption>I was tasked with analyzing the communication strategy used in 3 separate insurance quote flows. These strategies were based solely on emails provided during the flow by the user, and focused on convincing the user to return and finish the flow.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/e505e748-b60b-49a0-8fe7-10555b39d082/2Emailtypes-mask.png</image:loc>
      <image:title>Flow Analysis of Communications Strategy</image:title>
      <image:caption>The different email templates with their intent and trigger events were identified and distinguished from each other, as well as competitor counterparts.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/f12a5305-0568-4da6-a211-bade396cf2dc/3FlowTypesA2.png</image:loc>
      <image:title>Flow Analysis of Communications Strategy</image:title>
      <image:caption>each flow was presented with each email type/trigger noted as well as other pertinent info, such as when specific personal data is requested in the flow.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/7e130988-758d-4f62-9528-a2036208bdd8/4FlowTypesB.png</image:loc>
      <image:title>Flow Analysis of Communications Strategy</image:title>
      <image:caption>Using a layered flow diagram approach, all three flows were presented together to allow for a visual compare/contrast of key flow information.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/d8eee5ee-99e1-45fd-84b7-59f3e99e6fff/5contacttriggers.png</image:loc>
      <image:title>Flow Analysis of Communications Strategy</image:title>
      <image:caption>an alternate chart illustrates the variance in number of screens between the 3 different flows and the positional relevance of their corresponding data points.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/42c580b4-04f5-46f4-995a-a46a8f2c0cd3/PCCA.png</image:loc>
      <image:title>Flow Analysis of Communications Strategy</image:title>
      <image:caption>A visual display of corresponding screens in the competitor analysis portion of the review (Figma/Figjam)</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/9d6b393d-0925-45ad-acc6-39a89acaa6f7/NXPCAfest01.png</image:loc>
      <image:title>Flow Analysis of Communications Strategy</image:title>
      <image:caption>The full display of various visual elements in the flow analysis portion of the review. (Figma/Figjam)</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.holderux.com/work/taxonomy</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2023-06-12</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/8569598f-0e31-4fb1-9663-60ff32f127bb/Claimscurrent.png</image:loc>
      <image:title>Taxonomy Review</image:title>
      <image:caption>The review began with an overall taxonomic illustration of the site flow with the claims landing landing page at the top level. The wireframe breaks out the landing page content into functional sub sections for further review.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/3569032d-e2ad-4c91-953c-bdc6fc00d2c4/CaseflowsMod1.png</image:loc>
      <image:title>Taxonomy Review</image:title>
      <image:caption>A flow breakdown for each page in the site was included. This example shows the claims landing page, where most of the usability issues were identified. Different colored lines represent linkage flow for the individual use cases.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/1659eaf4-bdd0-49fe-85a0-eea79c74279c/usecasebreakouts.png</image:loc>
      <image:title>Taxonomy Review</image:title>
      <image:caption>Three use cases for the home page showing link destinations for each.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/59add596-af74-495b-9935-49302a0d3fdb/summaryrecomm.png</image:loc>
      <image:title>Taxonomy Review</image:title>
      <image:caption>The Summary review notes the key overall findings and illustrates recommended solutions relating to all three use cases. Having users self-identify by use case upon arriving on the landing page is made simple by introducing a dynamic module in the top position on the page.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.holderux.com/work/webapp-1</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2023-06-13</lastmod>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/a91bfb89-08af-416a-ad16-ed710f871132/XDPCA-1.png</image:loc>
      <image:title>Web App Review</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/f38c1606-fd18-4245-8c0e-991e046af612/XDPCA-2.png</image:loc>
      <image:title>Web App Review</image:title>
    </image:image>
    <image:image>
      <image:loc>https://images.squarespace-cdn.com/content/v1/646f7ee8e29386550aacc61a/e85343db-58f3-4b26-ac0d-71fbab067106/XDPCA3-10.png</image:loc>
      <image:title>Web App Review</image:title>
    </image:image>
  </url>
  <url>
    <loc>https://www.holderux.com/dpmacs</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2026-06-16</lastmod>
  </url>
  <url>
    <loc>https://www.holderux.com/aipatternlib</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2026-06-16</lastmod>
  </url>
  <url>
    <loc>https://www.holderux.com/navtax</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2026-06-26</lastmod>
  </url>
</urlset>

