CASE STUDY: iClicker Education
New connected digital experience for students and instructors fuels rapid market dominance.
CASE STUDY: Wolters Kluwer CoursePoint+
Refreshed UX aligns product with mental models of nursing instructors.
My working relationship with Openfield is one of the best I’ve had. I value and trust the partnership we’ve built together. We see them as another member of our team who has been instrumental in building great customer experiences with our products.
Selected clients and product teams that we collaborate with:
Insights from Openfield
Article
How to use loss aversion bias to evoke more meaningful user feedback on your product
As a product owner, you know that your users’ feedback is the most valuable asset in your arsenal. After all, your EdTech product can only succeed to the extent that it actually meets your users’ needs. And the more deeply you understand your users — their desires, mental models, requirements, and preferences — the more perfectly you can tailor your product to suit their taste. So it’s imperative that you draw out frank, unbiased, and uncensored feedback in every round of user testing.
Article
How EdTech product executives can make sense of mounting UX research data as products scale
If your EdTech company is committed to your product’s UX, then you already know UX research isn’t a one-and-done activity. It’s an ongoing, holistic part of your product life cycle. Which means that your UX team may generate dozens of research reports over the course of a single year. Each individual report tells a story and provides actionable insights. But as your research scales, so does your data. Before you know it, you can amass an avalanche of information — with no simple way to make sense of the bigger picture story it tells.
Article
To create an accessible EdTech product, banish exclusive design patterns
Say the words “exclusive design,” and the average person probably starts picturing high-end fashion brands and electronic devices. After all, in the world of marketing, “exclusive” is a good thing. But in the context of digital products, exclusive design isn’t a positive feature. It’s a preventable failure. When it comes to EdTech products, an exclusive design pattern is one that doesn’t meet the needs of all of its users. In other words, it’s a design pattern that only works well for certain groups of people, such as visual users or those with a mouse in addition to a keyboard.
Article
How to avoid EdTech data visualizations that are all beauty and no brains
At their best, data visualizations enable EdTech companies to tell interesting and meaningful stories using the data collected within individual products. Visualizations are both attractive and powerful. They have the ability to highlight trends, support decisions, and improve outcomes across the board. But not all data visualizations are created equal. If you don’t approach them with focus and care, they can actually work against you. A data visualization can be gorgeous — a piece of art worthy of hanging on the wall — without being truly useful.
Article
Need to right-size your UX and engineering investment? Understand these risks.
As an EdTech leader, you know firsthand how challenging it can be to strike the right balance between production costs, time to market, and quality. You must ship great products that generate revenue for your bottom line, build customer confidence in your brand, and ensure that your user and business needs are adequately addressed. That’s a pretty tall order, especially considering that you’re probably also under pressure to tighten your proverbial belt, given the current economic times. As a result, you may be grappling with the inevitable need to trim production costs in the form of UX research, design, and engineering.
Article
How to prioritize user needs as your product team tackles feature requests & business demands
As a product owner, you’ve been trained to put your users’ needs first. But you also know from experience that you don’t have the luxury of developing EdTech products in a vacuum. While your users should ideally drive everything you do, you must also contend with a host of competing pressures, from budgetary constraints to compressed timelines. The truth is that your feature requests and production timelines are often driven by business needs. But your users are the reason you created your product in the first place.