پن کیا گیا ٹویٹ
Ashish
2.7K posts

Ashish
@ashux_ui
Product Designer. Taking Projects for Q2 '26.
Let's Design Yours👉 شامل ہوئے Eylül 2024
521 فالونگ576 فالوورز

@0xsakshamtyagi @paper Atleast give the credit man to the original designer
English

I still can't believe this whole landing page came out of just a conversation with Claude.
I used @paper for prompts to design then back to code
I mean this is crazyy 🫡
English
Ashish ری ٹویٹ کیا

4. Rethinking the Kanban
Finally, I spent the most time on the Kanban board.
Before changing anything, I asked myself a simple question:
"What is this board actually helping users do?"
The answer wasn't reading beautifully designed cards.
It was scanning dozens of deals as quickly as possible.
That's when I realized the biggest issue wasn't the amount of information—it was the hierarchy.
The price, property, buyer, tags, and metadata all competed for attention, making every card feel visually flat.
So instead of removing information, I focused on organizing it. Better typography, spacing, layout, and hierarchy created a much clearer reading order, making the cards easier to scan.
One detail I kept coming back to was the Purchase tag.
With the board filtered to All, almost every visible card was still a Purchase. Showing a colorful badge on every card wasn't adding much value—it was simply repeating the default state.
So instead of removing it, I treated it as metadata. It still communicates the same information, but no longer competes with details that matter more.
The goal wasn't to simplify the cards.
It was to make them easier to read.


English
Ashish ری ٹویٹ کیا

3. KPI Cards & Chart
Next, I looked at the dashboard summary, the KPI cards and the analytics chart.
The first thing I noticed was that the KPI cards weren't really doing what KPI cards are supposed to do.
A good KPI should answer three questions almost instantly:
What am I looking at?
What's the current value?
Is it getting better or worse?
The original cards only answered one.
One metric in particular stood out: "Completed This Month."
Completed what?
Deals? Contracts? Signatures?
As one of the four most important numbers on the dashboard, it shouldn't leave room for interpretation.
So I focused on making the cards more informative. Clearer metric names, trend indicators, meaningful icons, and percentage changes all help answer the extra question users naturally have:
"Is this getting better or worse?"
The chart had a similar story.
The visualization itself wasn't the problem—it was everything around it.
Two very similar shades of blue represented different datasets, yet there was no legend to tell them apart. Then there was the "Show Analytics" dropdown... which felt a little funny because the chart is already analytics.
Rather than redesigning the chart, I focused on making it easier to read. A proper legend, more distinctive colors, a shorter title, and cleaner controls make the same information much easier to understand at a glance.


English
Ashish ری ٹویٹ کیا

2. Dashboard Structure
Once the sidebar felt cleaner, I moved on to the dashboard layout.
This was the part where I explored the most.
The original layout isn't wrong at all. It's a familiar SaaS pattern: KPIs at the top, analytics in the middle, and the workspace below.
So instead of asking "How can I redesign it?", I asked:
"What are RealPact users spending most of their time doing?"
From what I could understand, there are two primary jobs: keeping an eye on business performance and actively managing deals in the pipeline.
My first idea was to make the Kanban the primary focus of the page. It looked interesting, but it also changed the reading pattern significantly. Without user research, I couldn't justify asking existing users to relearn the interface.
So I looked for a middle ground.
The final layout keeps the familiar structure but gives the pipeline more room in the viewport. It shifts the emphasis from looking at the business to working on the business, without changing the mental model users have already built.

English
Ashish ری ٹویٹ کیا

1. Sidebar
The first place I started wasn't the dashboard.
It was the sidebar.
The original sidebar mixed actions, navigation, settings, and secondary tools together. Nothing was technically broken, but it required more visual effort than necessary.
At first, I actually considered removing it completely and experimenting with a bottom navigation something similar to what we've started seeing in more modern SaaS products.
It looked interesting, but the more I thought about it, the less it made sense.
So instead of replacing it, I asked a simpler question:
Can it become easier to scan?
The redesign focuses on better grouping, cleaner spacing, and a clearer distinction between primary navigation and secondary utilities.
The interaction stays familiar, but the hierarchy becomes much easier to understand at a glance.


English

Another example of tweets where people simply post my work to attract new clients 🤔
Zayden ✧ SaaS Expert@ZaydenSaaSgtfs
Going something like this
English

Closing the Thread
This wasn't an official redesign of RealPact.
It was a personal exercise to challenge my own product thinking and explore how small design decisions can improve an existing experience.
Throughout the project, I kept coming back to one principle:
Don't redesign what you don't understand. Improve what you do.
Every decision started with a simple question:
Can this be understood faster?
If the answer was yes, I explored it. If it required changing established workflows without understanding the users, I left it alone.
None of these changes are dramatic on their own.
But together, they make the dashboard feel clearer, lighter, and easier to scan while respecting the product and the people who already use it.
DM or book a call if you are founders who wants someone like me for their product.
English












