Use the calendar people actually work by

From a dashboard I designed for wholesale sales reps, who take retailers’ orders for manufacturers, and the agencies they work for.

A long-time member of our monthly council of agency owners and reps once asked me why the dashboard had no way to save a date range of her own alongside the built-in ones. Those were the timeframes the industry already reported in (month, quarter, and year to date, plus rolling 30, 60, and 90 days), and her question sounded like a request to stop typing the same dates. It turned out to point at a whole kind of period I’d left out. The calendar gives you dates, but the people using a product decide which stretches of time actually matter.

A few follow-up questions later, it was clear what the dates she kept typing were: trade shows, where retailers gather to place orders with reps. The industry holds a handful to a dozen major shows a year, each a few days to two weeks long and usually named for its city. Once I knew to look, the data showed people setting up one-off date ranges for shows everyone knew about, over and over. Then, after the first show of 2026, several users came forward on their own and all but begged for timeframes built around the shows, because almost all of their sales happened there.

Ask a parent in September how the year is going and they’ll tell you the new teacher seems good, mornings are chaos, and someone has already lost a left shoe. They’re measuring the year in school years without saying so, and reps measured theirs in shows: how this year’s Dallas show went, and how it compared with last year’s.

A month that contains a show also contains everything sold outside it, so an accurate monthly total can still be the wrong answer to “How did the show go?” I gave the dashboard’s timeframe pickers a mode for shows, drawn from a list each agency kept of the shows it worked, the same for all of its reps. A show in that list was its dates under its name, so its figures covered every order placed while it ran. The name went with those figures into every view, so a table said “Dallas Total Home” instead of “Jan 17–22.”

A saved range is only a set of dates, while a show comes back every year under the same name, so show mode could compare the Dallas show across three years even though its dates moved each year. The comparison still wasn’t conclusive, since sales during a show aren’t necessarily sales caused by it, and a show might run longer one year than the next. So the chart showed each year’s dates beneath its figures and left the explaining to the rep.

Shows also appeared as dots on the picker’s calendar, so someone puzzled by a low total could see when the timeframe they’d picked cut a show in half. During a show, some reps loaded the dashboard 50 to 100 times a day to see how the show was going as orders came in. So we let people make the current show their default, and the chart and tables opened on whichever show was running.

Once the shows were in, people also asked to name and save date ranges of their own, which is exactly what the council member had first asked for. Each rep’s named ranges sat in the same list as the agency’s shows, and reps used them for their sales trips on the road. Her literal request was right, and it wasn’t enough.

When someone asks for a preset, I ask what the dates stand for before I ask how often they type them. People measure time by the periods their work runs on, and a product should offer those periods by name, next to the calendar’s.