“Design used to be the seasoning you’d sprinkle on for taste. Now it’s the flour you need at the start of the recipe.’’

— John Maeda, Designer and Technologist
closeing x icon

Contact us

Please tell us a bit about your project idea and we’ll get back to you as soon as possible.
Tell us about your project idea
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
closeing x icon
Privacy Policy

This Privacy policy was published on March 1st, 2020.

GDPR compliance

At UX GIRL we are committed to protect and respect your privacy in compliance with EU - General Data Protection Regulation (GDPR) 2016/679, dated April 27th, 2016. This privacy statement explains when and why we collect personal information, how we use it, the conditions under which we may disclose it to others and how we keep it secure. This Privacy Policy applies to the use of our services, products and our sales, but also marketing and client contract fulfilment activities. It also applies to individuals seeking a job at UX GIRL.

About UX GIRL

UX GIRL is a design studio firm that specialises in research, strategy and design and offers clients software design services. Our company is headquartered in Warsaw, Poland and you can get in touch with us by writing to hello@uxgirl.com.

When we collect personal data about you
  • When you interact with us in person – through correspondence, by phone, by social media, or through our uxgirl.com (“Site”).
  • When we get personal information from other legitimate sources, such as third-party data aggregators, UX GIRL marketing partners, public sources or social networks. We only use this data if you have given your consent to them to share your personal data with others.
  • We may collect personal data if it is considered to be of legitimate interest and if this interest is not overridden by your privacy interests. We make sure an assessment is made, with an established mutual interest between you and UX GIRL.
  • When you are using our products.
Why we collect and use personal data

We collect and use personal data mainly to perform direct sales, direct marketing, and customer service. We also collect data about partners and persons seeking a job or working in our company. We may use your information for the following purposes:

  • Send you marketing communications which you have requested. These may include information about our services, products, events, activities, and promotions of our partners. This communication is subscription based and requires your consent.
  • Send you information about the services and products that you have purchased from us.
  • Perform direct sales activities in cases where legitimate and mutual interest is established.
  • Provide you content and venue details on a webinar or event you signed up for.
  • Reply to a ‘Contact me’ or other web forms you have completed on our Site (e.g., to download an ebook).
  • Follow up on incoming requests (client support, emails, chats, or phone calls).
  • Perform contractual obligations such as invoices, reminders, and similar. The contract may be with UX GIRL directly or with a UX GIRL partner.
  • Notify you of any disruptions to our services.
  • Contact you to conduct surveys about your opinion on our services and products.
  • When we do a business deal or negotiate a business deal, involving sale or transfer of all or a part of our business or assets. These deals can include any merger, financing, acquisition, or bankruptcy transaction or proceeding.
  • Process a job application.
  • To comply with laws.
  • To respond to lawful requests and legal process.
  • To protect the rights and property of UX GIRL, our agents, customers, and others. Includes enforcing our agreements, policies, and terms of use.
  • In an emergency. Includes protecting the safety of our employees, our customers, or any person.
Type of personal data collected

We collect your email, full name and company’s name, but in addition, we can also collect phone numbers. We may also collect feedback, comments and questions received from you in service-related communication and activities, such as meetings, phone calls, chats, documents, and emails.

If you apply for a job at UX GIRL, we collect the data you provide during the application process. UX GIRL does not collect or process any particular categories of personal data, such as unique public identifiers or sensitive personal data.

Information we collect automatically

We automatically log information about you and your computer. For example, when visiting uxgirl.com, we log ‎your computer operating system type,‎ browser type,‎ browser language,‎ pages you viewed,‎ how long you spent on a page,‎ access times,‎ internet protocol (IP) address and information about your actions on our Site.

The use of cookies and web beacons

We may log information using "cookies." Cookies are small data files stored on your hard drive by a website. Cookies help us make our Site and your visit better.

We may log information using digital images called web beacons on our Site or in our emails.

This information is used to make our Site work more efficiently, as well as to provide business and marketing information to the owners of the Site, and to gather such personal data as browser type and operating system, referring page, path through site, domain of ISP, etc. for the purposes of understanding how visitors use our Site. Cookies and similar technologies help us tailor our Site to your personal needs, as well as to detect and prevent security threats and abuse. If used alone, cookies and web beacons do not personally identify you.

How long we keep your data

We store personal data for as long as we find it necessary to fulfil the purpose for which the personal data was collected, while also considering our need to answer your queries or resolve possible problems. This helps us to comply with legal requirements under applicable laws, to attend to any legal claims/complaints, and for safeguarding purposes.

This means that we may retain your personal data for a reasonable period after your last interaction with us. When the personal data that we have collected is no longer required, we will delete it securely. We may process data for statistical purposes, but in such cases, data will be anonymised.

Your rights to your personal data

You have the following rights concerning your personal data:

  • The right to request a copy of your personal data that UX GIRL holds about you.
  • The right to request that UX GIRL correct your personal data if inaccurate or out of date.
  • The right to request that your personal data is deleted when it is no longer necessary for UX GIRL to retain such data.
  • The right to withdraw any consent to personal data processing at any time. For example, your consent to receive digital marketing messages. If you want to withdraw your consent for digital marketing messages, please make use of the link to manage your subscriptions included in our communication.
  • The right to request that UX GIRL provides you with your personal data.
  • The right to request a restriction on further data processing, in case there is a dispute about the accuracy or processing of your personal data.
  • The right to object to the processing of personal data, in case data processing has been based on legitimate interest and/or direct marketing.

Any query about your privacy rights should be sent to hello@uxgirl.com.

Hotjar’s privacy policy

We use Hotjar in order to better understand our users’ needs and to optimize this service and experience. Hotjar is a technology service that helps us better understand our users experience (e.g. how much time they spend on which pages, which links they choose to click, what users do and don’t like, etc.) and this enables us to build and maintain our service with user feedback. Hotjar uses cookies and other technologies to collect data on our users’ behavior and their devices (in particular device's IP address (captured and stored only in anonymized form), device screen size, device type (unique device identifiers), browser information, geographic location (country only), preferred language used to display our website). Hotjar stores this information in a pseudonymized user profile. Neither Hotjar nor we will ever use this information to identify individual users or to match it with further data on an individual user. For further details, please see Hotjar’s privacy policy by clicking on this link.

You can opt-out to the creation of a user profile, Hotjar’s storing of data about your usage of our site and Hotjar’s use of tracking cookies on other websites by following this opt-out link.

Sharethis’s privacy policy

We use Sharethis to enable our users to share our content on social media. Sharethis lets us collects information about the number of shares of our posts. For further details, please see Sharethis’s privacy policy by clicking on this link.

You can opt-out of Sharethis collecting data about you by following this opt-out link.

Changes to this Privacy Policy

UX GIRL reserves the right to amend this privacy policy at any time. The latest version will always be found on our Site. We encourage you to check this page occasionally to ensure that you are happy with any changes.

If we make changes that significantly alter our privacy practices, we will notify you by email or post a notice on our Site before the change takes effect.

Design debt quietly erodes UX over time. Should you fully redesign or iterate your product? Learn how to assess the impact, weigh the risks, and choose the right path for long-term success.

Press Office

Design Debt: When to Redesign vs. When to Iterate

reading time  - clock - icon
WSTAW
Author picture

Over time, digital products accumulate design debt—incremental changes, quick fixes, and legacy decisions that gradually degrade the user experience. This often results in a fragmented, inconsistent interface that frustrates users and complicates workflows. Organizations face a critical dilemma: should they invest in a full redesign or make iterative improvements to refine the existing system?

A complete overhaul can be costly, risky, and disruptive. It requires significant resources, may alienate existing users, and can introduce new usability challenges. On the other hand, continuous iteration allows for gradual refinement but risks perpetuating flawed design foundations. The key to making the right decision lies in assessing the extent of design debt, understanding its impact, and weighing the costs and benefits of each approach.

Understanding Design Debt: The Silent UX Killer

Design debt accumulates in several ways:

  • Quick fixes and workarounds often address immediate needs but create long-term usability issues
  • Legacy design decisions may no longer align with user needs or technological advancements
  • Inconsistent UI patterns emerge when multiple teams contribute without a cohesive design system
  • Lack of user feedback loops results in decision-making based on assumptions rather than data

Ignoring design debt can lead to a frustrating user experience, increased support costs, and lost revenue. Indicators of high design debt include frequent user complaints, declining conversion rates, and significant usability issues that require extensive workarounds.

The Case for Iterative Improvements

When the core UX remains functional but users experience friction in specific areas, iteration is often the best approach. This method allows teams to make targeted enhancements without disrupting familiar workflows. Iteration works well under several conditions:

  • Users struggle with specific pain points that usability testing can pinpoint and address
  • Minor UI inconsistencies create confusion but do not fundamentally hinder functionality
  • Data-driven insights suggest small optimizations can improve engagement and conversions
  • The current system remains scalable and does not impose excessive technical constraints

Successful iteration requires a structured approach—identifying pain points, testing solutions, and continuously refining the design based on real-world feedback.

The Case for a Full Redesign

Sometimes, design debt reaches a point where incremental improvements can no longer salvage the user experience. When usability flaws are deeply embedded in the system, a redesign becomes the only viable option. This is particularly necessary when the product relies on outdated technology that restricts innovation, when maintaining the existing system incurs higher costs than rebuilding, or when competitors offer a far superior UX that threatens market relevance.

However, redesigns come with substantial risks. A poorly executed overhaul can alienate loyal users, disrupt workflows, and lead to significant financial setbacks.

One infamous example is Digg’s 2010 redesign. Digg, once a popular social news aggregator, launched a drastic redesign (Digg v4) that removed key features users loved, such as the ability to view upcoming stories before they became popular. The new version was seen as prioritizing publishers over its core community, leading to a massive user exodus. Within weeks, competitors like Reddit saw an influx of former Digg users, and Digg’s traffic plummeted. This serves as a cautionary tale of how failing to align a redesign with user needs can have catastrophic consequences.

In contrast, Airbnb’s methodical redesign, informed by extensive user research, showcases how a well-planned revamp can drive engagement and growth. In 2014, Airbnb redesigned its search and booking experience to better accommodate user preferences and enhance visual storytelling. The redesign incorporated high-quality photography, improved filters, and a more intuitive booking flow. By leveraging A/B testing and gathering extensive feedback before the full rollout, Airbnb ensured a smooth transition, resulting in increased user satisfaction and higher conversion rates. Their data-driven approach demonstrates how a well-executed redesign can elevate a product without alienating its user base.

Making the Right Call: A Decision Framework

Deciding between iteration and redesign requires a structured evaluation process. Companies should begin with an in-depth usability audit, assessing the severity of design debt through usability scores, conversion rates, churn data, and direct user feedback. Identifying whether the primary issues are surface-level or deeply rooted in the system will clarify whether an iterative approach suffices or a full redesign is necessary.

If usability issues are isolated and correctable through focused adjustments, iteration is likely the better route. Teams should establish clear KPIs and user experience benchmarks to measure the success of iterative changes. Small-scale A/B testing can validate improvements before full implementation, reducing risks and allowing for incremental refinements.

For cases where fundamental usability issues persist, a redesign may be necessary. However, it should be approached methodically—by conducting thorough user research, prototyping potential solutions, and testing new designs before a full-scale launch. A phased rollout can mitigate risk, ensuring that users adapt smoothly and reducing potential backlash from drastic changes.

Beyond usability concerns, business strategy and technical feasibility should guide decision-making. If the current system lacks the flexibility to support long-term innovation, redesigning may be the only viable choice. However, if technical constraints are manageable and the UX can be improved without significant disruption, iteration offers a lower-risk alternative.

Conclusion: Strategic UX Decision-Making

Ultimately, the decision to iterate or redesign depends on the severity of design debt and its impact on users. While iteration allows for gradual enhancements, a full redesign is sometimes the only way to break free from foundational issues. Businesses must take a data-driven approach, leveraging usability testing and user feedback to guide their choices. Regularly auditing design debt ensures that user experience remains a priority and prevents the need for drastic interventions. By making strategic UX decisions, organizations can sustain product growth while maintaining an intuitive, user-friendly interface.

people
reading time  - clock - icon
5 min

Gherkin for UX? How Designers and Agile Teams Can Finally Speak the Same Language

In the high-speed world of Agile, where user expectations evolve faster than sprint cycles, clear communication is not just a nice-to-have — it’s critical. Yet even in well-functioning teams, UX designers and developers often struggle to stay perfectly aligned. The result? Beautifully crafted prototypes that don’t quite behave as intended once implemented, or ambiguous flows that leave testers guessing.

Enter Gherkin — a simple, structured language that can help bridge the gap between design, development, and product.

What is Gherkin (and why should UX designers care)?

Gherkin is a structured, plain-language format used to write behavior-driven development (BDD) scenarios, typically used by QA and dev teams to write automated tests. But its value goes far beyond testing.

Its real strength lies in its simplicity — it describes user behavior in a "Given–When–Then" format, making it the perfect candidate for aligning cross-functional teams around how a feature should behave.

Example:

This isn’t code — it’s user intent, written in plain English. And that makes it a powerful communication tool for designers.

How UX Designers Can Use Gherkin to Document Intent

Designers don’t need to become developers to leverage Gherkin. Instead, they can use it to clearly define interaction logic — supplementing wireframes, prototypes, and user flows with behavior-driven context.

By embedding Gherkin-style scenarios into design documentation or user stories, designers ensure that the team understands not just what the interface looks like, but how it should behave.

Here’s a UX-specific example:

This format reduces ambiguity and ensures that design intentions translate into correct implementations.

What’s in it for your team (and your bottom line)?

Introducing Gherkin into the UX process may feel like an extra step, but it pays off. Studies show that reducing ambiguity in handoffs and requirements can lead to major efficiency gains.

  • Fewer misunderstandings: A McKinsey report found that companies improving requirement clarity saw up to a 40% increase in team productivity (Source: McKinsey & Company).

  • Faster onboarding: Gherkin scenarios give new team members immediate context for how the product should behave.

  • Better alignment with business goals: Stakeholders can validate behavioral flows early — even before development starts.

  • Improved testability: QA teams can use Gherkin to write automated or manual tests directly aligned with design.

Gherkin becomes a shared language between design, product, dev, and QA — cutting down feedback loops and minimizing rework.

How to Start Using Gherkin in Your Design Process

You don’t need to overhaul your workflow overnight. Start small:

  1. Pick one key user flow — such as login, checkout, or onboarding.

  2. Write 1–3 scenarios in Given–When–Then format.

  3. Share them during refinement or planning with developers and testers.

  4. Attach the scenarios to your design files or link them in your backlog.

This lightweight addition can dramatically improve alignment — even in teams that already communicate well.

Design Is Behavior — Not Just Visuals

UX is about more than how things look — it's about how they work. While wireframes and prototypes show structure and visuals, they often leave room for interpretation when it comes to logic, rules, and edge cases.

Gherkin helps designers express interaction logic in a way that’s unambiguous and testable. And in an Agile team, that means fewer assumptions, faster delivery, and better user outcomes.

At UX GIRL, we encourage product teams to experiment with Gherkin as a way to reduce misalignment and build stronger bridges between design and development. You don’t need to be technical — you just need to care about clarity.

What’s Next?

Ready to give your design handoffs a boost? Start with a single Gherkin scenario for your next feature. Use it to open a conversation between design, dev, and QA. You might be surprised how quickly your team aligns when you’re finally speaking the same language.

Need help integrating UX practices like Gherkin into your Agile process? Reach out to UX GIRL — we help teams turn design decisions into product clarity.

people
reading time  - clock - icon
5 min

Designing Apps with OpenAI Apps SDK: UX Guidelines

Conversational AI has changed the rules of user experience. With OpenAI Apps SDK, teams can now create embedded applications that live directly inside ChatGPT — offering users seamless, intelligent, and contextual support.

But building these apps isn't just about writing smart code. It's about designing meaningful, intuitive interactions. That’s why OpenAI published official design guidelines — and why UX GIRL is here to help you translate them into real results.

What Are ChatGPT Apps and the Apps SDK?

ChatGPT apps are mini-tools that users can access directly in the ChatGPT interface. They allow users to perform tasks, analyze data, create documents, fetch information from external sources, and more — all within the flow of conversation.

The Apps SDK lets developers define these app interactions using JavaScript while maintaining full compatibility with the ChatGPT interface. But to deliver real value, apps need to feel intuitive — and that’s where UX comes in.

The Core Design Principles from OpenAI

OpenAI’s UX guidelines are built on six core principles. Here’s what they mean in practice, with insights from the UX GIRL team:

Clarity is key

Your app’s interface must clearly communicate what it does, how it works, and what users can expect. Avoid vague labels or overloaded screens. Guide users with simple language and clean layout.

Respect the user’s intent

Let users take the lead. Your app should support user goals, not hijack the conversation. Avoid aggressive prompts or forced flows.

Make progress visible

Users need feedback. Loading indicators, success confirmations, and microinteractions help users trust the process — especially in a conversational UI.

Minimize user effort

Reduce friction wherever possible. Use smart defaults, context-aware suggestions, and auto-filled values to streamline user input.

Be consistent

ChatGPT has a defined look and tone — follow it. Use system UI components and maintain consistency in voice, spacing, and layout.

Fail gracefully

Errors are inevitable. Design them to be informative and friendly. Offer users clear explanations and next steps without making them feel lost.

How Product Teams Can Apply These Guidelines

Following these principles doesn’t require a full UX overhaul — but it does require strategic thinking. Here are two practical ways your team can implement them:

1. UX-aligned development workflow:

  • Define realistic user conversations and app responses early.
  • Prototype conversations using mock UIs or prompt flows.
  • Test early and often — even with basic, Wizard-of-Oz style setups.
  • Build in real-time feedback elements (confirmation messages, visual states).

2. UX checklist for Product Owners:

  • Does the user always know what they can do next?
  • Are all actions and outcomes clearly explained?
  • Is app progress or system state visible?
  • Is tone and layout consistent with ChatGPT?
  • Do error messages guide users constructively?

The Unique UX Challenges of Designing Inside a Chat Interface

Unlike traditional apps, ChatGPT apps don't rely on menus, tabs, or visual hierarchies. Users interact through text — with fluid, nonlinear intent. This makes context one of the biggest UX challenges.

Small design gaps (e.g., unclear responses or missing context) can lead to confusion. That’s why good conversational design includes scenario testing, intelligent defaults, and visible state changes — even without a traditional UI.

Final Takeaways

Designing inside ChatGPT isn’t just about building functionality — it’s about earning user trust through clarity, empathy, and consistency.

At UX GIRL, we recommend:

  • Start with a small MVP to test a focused user goal.
  • Use OpenAI’s design principles as a design audit tool.
  • Involve UX early — especially for dialogue design and testing.
  • Don’t rely on AI to do everything. Guide the user intentionally.

Building with Apps SDK? Let UX GIRL help you design AI-powered experiences that convert, engage, and delight.

magda
reading time  - clock - icon
5 min

Magdalena Ostoja-Chyżyńska: Strong Women in IT 2025

We are proud and excited to announce that Magdalena Ostoja-Chyżyńska, CEO of UX GIRL, has been recognized among the outstanding leaders featured in the prestigious Strong Women in IT 2025 – Global Edition report. This global publication highlights inspiring stories of women from around the world who play a key role in driving digital transformation, innovation, and the growth of new technologies.

The report showcases women who not only achieve professional success but also inspire others with their determination, resilience, and ability to break barriers. Magdalena was selected thanks to her consistent work, broad expertise, and vision that she has been implementing in the IT industry for many years. Her story is presented in the report based on a personal questionnaire, giving readers a glimpse not only into her professional journey but also into the values she lives by every day.

As the CEO of UX GIRL, Magdalena has been building a company that places users at the very center of the design process, creating digital solutions that truly support business growth. Her leadership combines strategic expertise with a deep understanding of people’s needs – both the end users of technology and the team members she works with. Thanks to this approach, UX GIRL delivers not only innovative projects but also fosters an organizational culture built on empathy, collaboration, and responsibility.

Magdalena’s recognition is not just a celebration of her achievements but also an important voice in the global conversation about the role of women in technology. The IT sector still faces challenges around equality and representation, and initiatives such as Strong Women in IT are essential. They demonstrate that diversity, collaboration, and courage in decision-making drive meaningful change and open up new opportunities.

For years, Magdalena Ostoja-Chyżyńska has been proving that leadership in technology can successfully combine business expertise, an innovative mindset, and the ability to build teams based on trust and shared accountability. Her journey is a powerful example that women in IT not only achieve success but also have a lasting impact on the entire industry.

This recognition is both an acknowledgment of Magdalena’s accomplishments and an inspiration for all women who aspire to a career in technology.

We warmly congratulate our CEO – Magdalena Ostoja-Chyżyńska – for being named among the global leaders who are shaping the future of IT.

Read the full report here

Begin your design adventure now!
Contact us