ABOUT
Companies that join forces through mergers and acquisitions face unique website challenges. Mergers often leave a company with dozens of websites with unclear ownership and mixed messages for customers. I help companies manage a cohesive multi-site content transition by using a framework to make content architecture decisions across hundreds to sometimes thousands of pages so they all tell one story on time.
Effective website information architecture pays off in better findability, clearer decisions about content, and stronger brand and sales results.
A well-structured site uses navigation labels and groupings that match how users think, so they can locate what they need without guessing. This leads to higher user satisfaction and better content discoverability.
The Little Language Models process is an established framework for research, auditing, and developing new content structures aligned with key goals. This prevents the chaos that builds up when websites accumulate content without a plan.
When companies combine or rebrand, a shared content structure keeps their websites consistent and prevents confusion. This framework supports cross-selling and creates sales synergy between once-separate entities.
By finding and fixing the content structure pain points that hold back engagement and conversions, a site can guide visitors more efficiently through key tasks and journeys.
Case studies
Process
These are some of the information architecture activities involved in keeping your digital ecosystem organized and optimized.
Read this guide for a thorough explanation of the activities, why they’re needed, the formats they’re delivered in, and how each piece fits together.
Step 0.1
After you express interest via the form, LinkedIn, or email, I schedule a 30-minute intro call with you to explore mutual fit and address any immediate questions.
Alternatively, you can book a meeting on Calendly directly. You’ll be able to share details about the initiative and add team members to the call.
If your company is located in Vienna, I’d love to meet in person – at The Hub or in your offices.
Step 0.5
You’ll receive a proposal that outlines the current state, project objectives, ways to work together (such as audits, redesigns, or ongoing retainers), timeline, and budget. Once that’s signed and ready, here are the six steps involved in an information architecture redesign, roughly in the order the work happens.
Step 1
Interview users and stakeholders, and review heatmaps, screen recordings, visit data, and search behavior to find the biggest user frustrations and confirm the key tasks.
Step 2
Group content into categories that match users’ mental models, rewrite navigation labels so they’re clear, and streamline the paths people take to reach information.
Step 3
Create a sitemap and, where useful, a product ecosystem map that shows how products, platforms, and stakeholders relate. This gives the redesign a clear structure before any pages are built.
Step 4
Design user journeys for three to four key pages as low-fidelity content wireframes. This keeps the focus on information hierarchy and clarity rather than visual styling.
Step 5
Organize the recommended changes by impact and effort so the team knows what to tackle first.
Step 6
Build a content testing plan to validate the new groupings and labels, refine the designs based on results, and compile everything into a report with clear decisions and recommendations.

Tested across 30+ websites, this framework looks at the full system: how engineering, marketing, design, and content owners fit together, how pages connect to automations and personalized experiences, and how each user pathway leads to the actions that drive conversions.
I’ve organized information for diverse companies, from academia to tech giants. My tested approach adapts to different audiences, content types, and constraints, allowing customization for any site instead of a one-size-fits-all template.
A sitemap shows where pages sit. Instead, I design content architecture that accounts for the teams who build and maintain content, the technology that connects it, and the paths people take to reach their goals, so that the structure supports the outcomes your business cares about.
Every URL has a history. I bring the same care to those conversations as I do to the data. I listen to the concerns behind each request to keep content, then pair them with clear rules and analytics, so your team can move forward with confidence.

Hi! I’m Delfina Hoxha, the founder of Little Language Models and an information architect who helps merging companies bring their websites together. I’ve architected and implemented information structures for universities, non-profits, and global tech brands.
I led the Harvard Law Review website content redesign, earning a Webby Award nomination, and wrote the content that helped the top Food & Drink app in Albania set a new daily active users record.
My background in psychology taught me how people make sense of information, why they get lost, and what helps them find what they need. I bring that understanding to every project, along with years of experience as a writer, designer, and marketer.
Testimonials
Little Language Models has proudly supported products used by thousands to millions of users for clients like Sony, Journi, and DataRobot.



Weekly guides on how to structure content so people actually find what they need, covering taxonomies, navigation, and the systems that make discovery effortless.