Reducing Time-to-Trust in Competitive Fortnite
Product Designer
No-Code Builder
3 Weeks Concept to Product
Context
While observing a competitive FNCS player, I noticed that he regularly spent 1 to 2 hours every few days searching for teammates. Even after connecting, several scrims were required to determine whether the skill level and playstyle were compatible.
The issue was the time required to establish trust.
Defining the Problem
Players need alignment across mechanical skill, in-game decision-making, communication habits, and region proximity to ensure low ping. A mismatch in any of these areas often becomes apparent only after several practice sessions.
Existing tools introduce compounding friction.
Discord channels are noisy and ephemeral. Messages are quickly buried. Filtering for serious competitors is limited. Performance metrics such as Power Ranking (PR) and earnings are frequently self-reported and difficult to verify. Initiating contact requires repeated cold outreach, and validation still depends on trial games.
Approach
My research began with a focused interview with a competitive player, followed by an analysis of Reddit discussions and direct observation of discovery workflows within Discord communities.
A consistent pattern emerged. Players ultimately evaluated potential teammates through gameplay rather than through written descriptions or statistics. Metrics such as earnings and PR provided context, but clips revealed a player’s consistency, game awareness, and performance under pressure.
Design Decisions
The focus shifted to accelerating trust. Gameplay clips were prioritized as the primary signal, allowing users to evaluate skill instantly. Autoplay eliminated the need to navigate deeper into profiles, making assessment fast and intuitive.
The matching flow replaced open messaging with mutual interest. Instead of sending direct messages, users could express interest through a simple swipe. Conversation was only enabled once both players showed interest, reducing unnecessary outreach and making introductions more intentional.
The discovery view was intentionally simple. Region and key performance metrics were visible, but secondary to gameplay clips. The goal was to allow users to evaluate someone confidently within seconds, keeping the interface focused while still providing essential context.
Solution
MatchFN introduced a structured matching system. Profiles focused on gameplay clips and competitive preferences. A video-first feed enabled quick evaluation, and conversation was unlocked only after mutual interest was confirmed.
This shortened gap between initial discovery and first scrim by increasing confidence earlier in the process.
Outcome
Early feedback confirmed that the frustration was real. Players agreed that finding a good duo was inefficient, and they understood the value of the concept. However, most were not motivated to change their current behavior.
Despite its flaws, Discord felt “good enough.” Players occasionally found strong teammates through random matches, which reinforced the idea that the existing system eventually works. Because of that, there was little urgency to move to a new platform.
The primary learning opportunity was about problem intensity. Even when a workflow is inefficient, people will stick with it if the pain is tolerable. In this case, the problem existed, but it was not strong enough to drive meaningful behavior change.
Reflection
This project changed how I think about product design. In matching systems, building trust is more important than adding more information. The signals you show matter more than how many you show. I also learned that people rarely leave familiar systems, even if they are inefficient.
Good design alone is not enough if the problem is not urgent.
If I continued to build MatchFN, I would focus on tournament earners who's time has real financial stakes. Testing the product with that group would help determine whether the problem is strong enough to support a dedicated platform.