User Experience for B2B Platforms

🔬 How To Run UX Research In B2B and Enterprise. Practical techniques of what you can do in strict environments, often without access to users. 🚫 Things you typically can’t do 1. Stakeholder interviews ← unavailable 2. Competitor analysis ← not public 3. Data analysis ← no data collected yet 4. Usability sessions ← no users yet 5. Recruit users for testing ← expensive 6. Interview potential users ← IP concerns 7. Concept testing, prototypes ← NDA 8. Usability testing ← IP concerns 9. Sentiment analysis ← no media presence 10. Surveys ← no users to send to 11. Get support logs ← no security clearance 12. Study help desk tickets ← no clearance 13. Use research tools ← no procurement yet ✅ Things you typically can do 1. Focus on requirements + task analysis 2. Study existing workflows, processes 3. Study job postings to map roles/tasks 4. Scrap frequent pain points, challenges 5. Use Google Trends for related search queries 6. Scrap insights to build a service blueprint 7. Find and study people with similar tasks 8. Shadow people performing similar tasks 9. Interview colleagues closest to business 10. Test with customer success, domain experts 11. Build an internal UX testing lab 12. Build trust and confidence first In B2B, people buying a product are not always the same people who will use it. As B2B designers, we have to design at least 2 different types of experiences: the customer’s UX (of the supplier) and employee’s UX (of end users of the product). In customer’s UX, we typically work within a highly specialized domain, along with legacy-ridden systems and strict compliance and security regulations. You might not speak with the stakeholder, but rather company representatives — who regulate the flow of data they share to manage confidentiality, IP and risk. In employee’s UX, it doesn’t look much brighter. We can rarely speak with users, and if we do, often there is only a handful of them. Due to security clearance limitations, we don’t get access to help desk tickers or support logs — and there are rarely any similar public products we could study. As H Locke rightfully noted, if we shed the light strongly enough from many sources, we might end up getting a glimpse of the truth. Scout everything to see what you can find. Find people who are the closest to your customers and to your users. Map the domain and workflows in service blueprints and . Most importantly: start small and build a strong relationship first. In B2B and Enterprise, most actors are incredibly protective and cautious, often carefully manoeuvring compliance regulations and layers of internal politics. No stones will be moved unless there is a strong mutual trust from both sides. It can be frustrating, but also remarkably impactful. B2B relationships are often long-term relationships for years to come, allowing you to make huge impact for people who can’t choose what they use and desperately need your help to do their work better. [continues in comments ↓] #ux #b2b

It took me a decade to truly understand what it means to design for B2B enterprise. Here are some hard truths. B2B is wonderfully complex. Release cycles are driven by engineering rigor, and the domain knowledge runs deep. Learning it takes time, and there’s incredible institutional knowledge to absorb. You earn trust when you invest in understanding the domain as deeply as your engineering partners do. Vision thrives when leadership champions it. The challenge is demonstrating how design thinking adds value within real technical constraints. Here’s what I’ve learned about how design succeeds in this environment: Push the envelope, always. Designers bring unique ways of seeing, framing, and solving problems. That’s the power of creative problem solving. Great design requires great engineering, and the partnership works best when both disciplines challenge each other constructively. Design naturally gets pressure tested from multiple angles. That’s healthy. As designers who understand technology and product (myself included), we can empathize deeply with engineering constraints. But we also need to maintain one perspective that imagines beyond current limitations. That’s where breakthrough solutions come from. Measure what matters for your customers. B2B customers typically upgrade quarterly or semi-annually, not daily or weekly. Understanding their actual adoption patterns helps us focus on the right success metrics. Designing for B2B requires patience and perspective. Progress can feel slow day to day, but when you do the right things consistently, impact compounds and arrives all at once. If you need instant gratification, enterprise work will frustrate you. But if you appreciate compounding returns, it’s incredibly rewarding. B2B customers often become accustomed to friction in their tools. They accept it as normal until something like Slack shows them a fundamentally better experience. Our job is to not accept that friction, even when customers have adapted to it. We can create those breakthrough moments. Some days feel like you’re keeping the ship running smoothly. Other days you’re pushing toward the future state. Both matter equally. Both are essential to success. What I wish I’d understood earlier: - Be the designer you’re meant to be. - Collaborate with your partners with deep empathy. - Stay relentless about simplifying your customers’ lives. - Don’t accept unnecessary complexity. Trust in long-term impact over quick wins. The domain is deep. The pace is measured. The collaboration is constant. And the work matters tremendously because enterprise users deserve experiences as intuitive and delightful as the consumer products they use every day. Earn respect from your stakeholders and partners. Keep pushing forward. #design

If your Figma text styles are named “H1 / H2 / H3”… we need to talk. DON'T! It works for a while. Then your product grows, pages get more complex, marketing joins the party, accessibility requirements show up, and suddenly: • Your “H1” feels too loud in some places and too quiet in others • Designers override styles because “it didn’t look right” • Devs guess which heading tag goes where • Accessibility gets messy • Consistency slowly slips away The core issue? 👉 You’re mixing semantics with styling. In code, headings tell a story in hierarchy: H1 = most important H2 = next H3 = nested meaning …and so on. But visually, the largest, boldest text in your UI isn’t always your semantic H1. • Sometimes the biggest text is a hero headline. • Sometimes it's a section title. • Sometimes a dashboard title isn’t visually huge, but is the true H1 for the page. So tying visuals to HTML tags locks your system into the wrong rules. What to do instead: 👉 Name type styles based on their role and scale, not HTML tags. Something like: ********************** Display XL Display L Display M Headings Heading XL Heading L Heading M Heading S Body Default Body Emphasized Body Default Plus optional variants like Caption, Label, Overline. ********************** 👉 Now designers choose based on visual intention. 👉 Developers map the correct semantic tag based on context. In short: HTML tags = meaning and structure Figma styles = visual hierarchy and usability Keep them separate and your system scales cleanly. ✉️ → Free newsletter: moonlearning.io/newsletter 📚 → All my tutorials: moonlearning.io

Brands used to broadcast. Now they respond. ✅ Think of a B2B SaaS platform where every interaction flexes to the person in front of it. A procurement officer logs in and the dashboard emphasizes compliance, audit trails, and control. A developer logs in and the experience surfaces APIs, sandbox access, and speed. A CFO sees ROI models, forecasts, and financial clarity. Same product. Same brand. Different resonance. This is the rise of responsive brand experience. Not a gimmick, but a strategy: making every layer of identity—UI, UX, content, and even tone of voice—adaptive, intelligent, contextual.❤️ The contrast is striking. Legacy enterprises still design for the average user. They ship one interface, one story, one pathway. Digital-first players design for each user, building systems that adjust like living organisms—changing not only logos, but dashboards, help content, and even microcopy to meet the user where they are. There’s philosophy behind it. Customers don’t just want “software that works.” They want “software that gets them.” Adaptive design—whether in visual identity, navigation, or communication—signals empathy. It says: we see you, we know what matters to you, and we’ll clear the clutter so you can move faster. But the danger is real. Adapt too much and you lose coherence. A CFO may welcome tailored insights but won’t trust a brand whose tone, design, or values feel inconsistent. Responsiveness must orbit around a strong, immutable core: trust, reliability, transparency. What shifts is the expression; what stays firm is the essence. So, the real question for technology brands is not can you adapt? It’s why and how much?💯 The opportunity is profound. Responsiveness is not decoration. Not novelty. It’s a signal of intelligence. The same principle behind great products—turning complexity into clarity—should govern the brand experience itself. When UI, UX, and content stop shouting and start listening, the brand doesn’t just “look” intelligent. It feels intelligent. That’s when technology stops being a tool and starts being a partner. #futureofmarketing #thoughtleadership #thethoughtleaderway

Why this KPI works better than most “Sales Overview” cards I see? Not because it uses icons. Not because it has percentages. But because it turns a summary metric into a quick comparison story. There are 7 intentional design decisions here. Let me break them down. 1. The primary metric owns the visual hierarchy: $2,000 is large, centered, and impossible to miss. Before users process anything else, they understand the headline: total sales. Everything else supports that number- nothing competes with it. 2. Icons provide instant semantic cues. Cart = Orders. Location pin = Visits Users don’t need to read labels first- they recognize categories visually. This reduces cognitive load, especially for frequent viewers. 3. Color is doing classification, not decoration: Blue for Orders. Purple for Visits. Consistent across icon, text, and bar segment. No gradients. No unnecessary highlights. Color is used once and then reinforced everywhere. 4. The progress bar visualizes imbalance: It’s showing distribution. The longer Visits segment immediately communicates: “We’re getting traffic, but fewer of those visits convert.” The insight is visual before it’s analytical. 5. Percentages + counts = dual level understanding" 32.47% vs 67.53% gives proportion. 250 vs 520 gives scale. Many dashboards show only percentages- which hides magnitude. Here, users see both impact and volume. 6. The comparison is explicit, not implied: Orders vs Visits aren’t placed in separate visuals. They live side by side with a clear “vs” separator. No guessing what’s being compared. The design literally says: “Compare these two.” That tiny “vs” is doing heavy cognitive lifting. 7. Time context sits quietly in the slicer: Month selection at the top keeps the KPI focused on one period. Users understand this is a snapshot- not a trend analysis. Context is available without cluttering the main story. Love this breakdown? Follow #TheVisualBreakdown. Hit the bell so you don’t miss the next one.

The deeper the workflow, the harder it is for users to articulate what they need. In B2B, users are often experts in their job, not in your product. They’ll tell you what’s broken, but not always how to fix it. They might ask for a button, when what they really need is a better workflow. Great PMs listen beyond the ask. They watch users work. They study the pain behind the request. And they design solutions that solve the root cause, not just the symptom. In enterprise products, the best insights don’t come from feature requests. They come from understanding context. #B2B #SaaS #ProductManagement #UserResearch #CustomerEmpathy #EnterpriseUX

If AI adoption is uneven in your company, that’s not a tooling problem. It’s a UX leadership problem. Not because the interfaces are bad. But because we keep designing features, while the real challenge is adoption across roles, teams, and workflows. A recent OpenAI enterprise report, based on aggregated usage data and a survey of 9,000 workers across nearly 100 companies, makes this shift unmistakably clear: AI inside organizations is no longer experimental. It’s becoming infrastructure. But here’s the uncomfortable part. The biggest performance gap isn’t between companies. It’s between frontier users and the median—inside the same organization. That gap shows up as uneven speed, uneven quality, and uneven decision-making. And UX leaders should care, because this isn’t a model-access issue anymore. It’s an operating model issue. The teams pulling ahead aren’t just “prompting better.” According to the OpenAI report, they’re doing less visible, more structural work: ▶️ Standardizing reusable internal GPTs instead of one-off experiments ▶️ Turning on secure connectors so assistants actually understand organizational context ▶️ Treating enablement as a design problem, not a training afterthought ▶️ Measuring workflow impact over time, not just feature satisfaction This reframes the role of UX leadership. Experience quality is no longer defined only by UI polish. It increasingly depends on governance, enablement, and shared institutional knowledge. And the next wave makes this unavoidable. The same report points toward a shift from requesting outputs to delegating multi-step workflows. At that point, accountability, visibility, and coordination become core experience questions. Who decided what? What did the system actually do? Where does review, escalation, and “definition of done” live? If we don’t design for those answers, uneven adoption will quietly harden into uneven capability. And that’s how organizations end up with AI-powered teams—and AI-blind ones—sitting side by side. If you’re exploring the Empathic Web, AI, and design leadership, follow me for more. #UX #DEsign #UXDesign #UXLeadership #EnterpriseAI #DesignLeadership #OpenAI #AdoptionUX #FutureOfWork #ProductDesign Virtual Identity

Ever wonder why users abandon your product despite all those features you've worked so hard to build? #ux The culprit might be hiding in plain sight. I once worked with a startup that couldn’t figure out why their user retention was plummeting. They had a solid product, great features, and a strong value proposition. But after conducting a UX audit, we uncovered five critical mistakes that were silently driving users away. 🤔User psychology..... - minimize cognitive load by providing clear, easily accessible paths to different sections. Users don’t have to remember complex navigation structures (cognitive load) - localized content and personalized sections make users feel the app is tailored to their needs, increasing engagement (Motivation) - Visual Hierarchy and High contrast between text and background, along with consistent color usage, helps users quickly distinguish different sections and interactive elements (Attention and Perception) - A clean, visually appealing design creates a positive emotional response, making users more likely to spend time on the app and return frequently (Emotion) 1) Overwhelming users with options instead of guiding their journey 2) Hiding critical features behind unintuitive navigation 3) Prioritizing aesthetics over usability (that gorgeous but unreadable font isn't helping anyone) 4) Ignoring mobile users (still happening in 2025!) 5) Failing to validate designs with actual user testing The most expensive mistake? Assuming your users think like you do. 🎙️As Theodore Levitt famously said, "People don't want to buy a quarter-inch drill. They want a quarter-inch hole." Which of these mistakes have you seen the most? Let’s discuss! #ux Follow Sivaraman loganathan . Reshare to others

Leading UX maturity transitions isn't for the faint of heart. Your organization's UX maturity plays a big part in your career trajectory. When you're working in a low-maturity company: - You spend countless hours evangelizing why research matters - You're siloed from other departments - Process-building takes precedence over actual research But here's the flip side—low maturity orgs also offer a unique opportunity. You can shape the UX culture from scratch! 🪜Meet them where they are In low-maturity orgs, start with quick wins that deliver obvious value. Focus on usability fixes that create immediate impact. Don't begin with foundational research that takes months to pay off. Remember: You need to earn trust before you can make bigger asks. Think simple 5-user usability tests that identify critical conversion blockers. The ROI will be so clear that executives will ask for more research. 🪜Build champions across departments UX maturity isn't just about your team—it's about the org's mindset. Identify potential allies in product, engineering, and marketing. Invite them to observe user sessions. Keep it low effort. Bribe them with snacks. Go where they are. Make it fun! 🪜Create a visible maturity roadmap Be explicit about where you are and where you're going. Show what each stage of maturity looks like and the business benefits of progressing. This helps manage expectations and gives everyone a shared vision. Don't expect to jump from stage 1 to stage 5 overnight. It's a marathon, not a sprint. 🪜Invest in documentation & processes Make it really easy for anyone to answer, "What do we know about X users?" Start by putting everything in one place. Could be Drive. Or Confluence. Or a cool repository tool like Looppanel. Just make sure that insights are easy to find and reuse. Here’s a guide to setting up a repository from scratch: https://bit.ly/4bs9c9V Have you led UX maturity transitions? What were the learnings?

Predict, Personalize & Perform : From Leads to Loyalty Let’s be honest—customer lifecycle marketing (CLM) in B2B used to be a fancy word for “email nurture” and “CRM segmentation. But today, with AI, machine learning, and predictive data models, CLM is becoming something much more powerful: ➡️ A living, learning ecosystem that adapts to each buyer journey in real time. Here’s how we’re seeing AI and ML revolutionize CLM in B2B: 🔍 1. Predictive Journey Mapping Machine learning algorithms are helping identify where an account or contact actually is in the funnel—not just where your CRM says they are. ✅ No more generic MQL > SQL flows ✅ Dynamic scoring based on behavior, content engagement, and intent signals ✅ Real-time stage shifts based on predictive fit and readiness — 📈 2. Hyper-Personalized Nurturing (at Scale) AI models now create content clusters matched to personas, industries, and even buying committee behavior. 🎯 Email sequences, LinkedIn ads, and landing pages are personalized based on: Buyer role Past touchpoints Predicted product interest ICP match + firmographic data It’s not just segmentation—it’s micro-personalization powered by behavioral AI. — 🔁 3. Intelligent Retargeting & Re-Engagement Using ML-powered intent data and anomaly detection, you can now: Spot churn risks before they happen Trigger re-engagement sequences based on drop-off patterns Retarget accounts that show subtle buying signals across web, search, and social Retention is no longer reactive. It's predictive. — 📊 4. Revenue Forecasting + Attribution Modeling Thanks to data science, we can model: Which touchpoints actually move pipeline Which leads are likely to convert within a time window How to attribute revenue across full-funnel programs—not just the last touch This gives marketing the credibility and confidence we’ve needed for years. — 💡 The CLM Stack of a Modern B2B Org Should Include: ✔️ Customer Data Platform (CDP) ✔️ AI-powered segmentation + scoring ✔️ Predictive content engines (LLMs + RAG) ✔️ Lifecycle orchestration tools (e.g. Ortto, HubSpot, Marketo w/ ML layers) ✔️ Analytics + BI layer for optimization 🧠 Final Thought: In 2025, CLM isn’t just “marketing automation” with better templates. It’s about building an AI-powered engine that understands, anticipates, and activates each step of the buyer journey. You don’t need more content. You need smarter orchestration. 💬 Curious to hear from other B2B leaders: How are you bringing AI into your lifecycle marketing stack?