BlockSync
BlockSync was a resurrected production-geology product within the Seequent Evo ecosystem. As Lead Product Designer, I led the UX direction for a new generation of production-mining workflows: grounding the opportunity in the domain, aligning the team around a usable model of the work, and turning that direction into a buildable product concept.
Re-establish the case for BlockSync
Section titled “Re-establish the case for BlockSync”The first step was not to polish the old concept. I revisited the production-geology context, the market, and the competitive landscape to understand what had changed and where the product could create a clear advantage. This gave the team a shared basis for deciding what to preserve, what to challenge, and what to leave behind.
Market research connected the product idea to the wider opportunity and the work still needed to make it viable.
Industry research grounded the opportunity in the realities of production mining.
Competitive review helped separate familiar conventions from genuine opportunities.
Understand production-geology users
Section titled “Understand production-geology users”Evo gave the product a platform context, but it did not answer how production-geology teams worked. I led the research and synthesis across roles, responsibilities, handoffs, and existing tools. The central problem was not simply moving spreadsheets online: teams needed to know which model was current, what had changed, and who could safely work on it.
User-group mapping made the ecosystem of primary users, supporting roles, and decision-makers explicit.
The geologist lifecycle showed where responsibilities, information needs, and handoffs changed over time.
Research synthesis turned domain knowledge into product questions the team could act on.
Set a direction the team could build from
Section titled “Set a direction the team could build from”I translated the research into product principles, user definitions, and a service journey. This was the leadership work: making the trade-offs explicit, giving the team a shared language, and establishing what the first useful version needed to make clear.
The team-purpose work connected research questions to principles, hypotheses, and a shared way of working.
The journey connected individual tasks to the wider production workflow.
The resulting direction treated BlockSync as a system of record for model work, rather than a cloud folder for files. Ownership, status, review, and handoffs became first-class design concerns.
Workflow mapping showed where the product needed to protect trust and coordination.
Turn the direction into buildable flows
Section titled “Turn the direction into buildable flows”I used information architecture, UI flows, wireframes, and prototypes to test how the direction could work in practice. The goal was to make model state, ownership, and change legible without adding another layer of administrative work for production teams.
Prototype slices made the current release direction concrete while keeping future capability visible.
Validate the workflow before release
Section titled “Validate the workflow before release”Task-based prototype testing gave the team evidence about where the proposed flow worked and where it created friction. One tested task recorded an 81.8% average success rate, with a 22.5% missclick rate and clear drop-off points to investigate. That made the next design decisions specific: simplify the path, clarify system feedback, and remove avoidable ambiguity before build.
Testing turned a broad workflow concern into measurable decisions about the path and the screens within it.
Shape a phased release
Section titled “Shape a phased release”The product was not treated as one large delivery promise. I helped frame a Now / Next / Future direction so the team could protect the core model-management workflow while making room for reporting, reconciliation, integrations, and richer 3D collaboration later.
Phased planning kept the first release focused without losing sight of the larger product opportunity.
Outcome and leadership contribution
Section titled “Outcome and leadership contribution”The work re-established BlockSync as a credible product direction for production mining: clearer model state, traceable change, and structured collaboration around shared block models.
My contribution was to lead the direction from market and domain framing through research synthesis, principles, workflow definition, prototype testing, and release thinking. The platform foundation reduced the need to rediscover shared context; the mining research supplied the domain understanding Evo could not provide. That combination gave the team a more grounded starting point for deciding what to build next.