Onyx Eagle Claw
Translating an evolving vision into a system the client could understand, approve, and use.
The Challenge
Onyx Eagle Claw is a martial arts school identity built around Eagle Claw Kung Fu, Wu Tai Chi, and the relationship between movement, balance, and the yin-yang.
The project began with a detailed brief and a client who had strong ideas about what the identity needed to represent. But some of the most important relationships inside that vision only became clear once they could be seen, discussed, and tested.
My role extended beyond creating the visual identity. I structured the review process, translated evolving feedback into requirements, mapped dependencies between design decisions, documented the reasoning behind each major iteration, built the final asset system, and created the guidance needed for the client to use it independently.
A detailed brief wasn’t the same as a finished specification
The initial direction was unusually specific.
The identity needed to combine a yin-yang, a Chinese Golden Eagle, and a silhouette of the client performing a particular technique from his system. The pose carried real meaning and was non-negotiable. The eagle and practitioner needed to communicate the relationship between animal movement and human practice, while the yin-yang represented the philosophy underlying the system.
There were also practical needs: the identity had to extend beyond one mark into something usable across digital, apparel, signage, and other future applications.
That gave me a strong starting point, but not every relationship was fully understood yet.
Early requirements described the eagle and practitioner as opposing subjects with similar visual weight. Later discussion revealed a more nuanced hierarchy: the eagle was the origin and blueprint of the practice, while the practitioner was its human realization. They were not adversaries. The practitioner mirrored and translated the animal’s movement.
Likewise, Wu Tai Chi initially appeared to function like supporting information. Through later conversation, I learned that it was integral to how the client understood the complete practice and could not simply read as a subordinate descriptor.
A stakeholder can know what matters without yet having the language to specify exactly how those relationships should work.
Context & Constraints
The hardest part of the project was not any individual drawing problem. It was the dependency between them.
The practitioner’s pose was fixed. The traditional S-curve and circular integrity of the yin-yang needed to remain recognizable. The eagle, practitioner, positive and negative space, typography, scale, and points of intersection all affected one another.
Changing one relationship changed several others.
Relationships
The eagle, practitioner, and yin-yang had to communicate a meaningful hierarchy rather than simply coexist.
Geometry
The traditional S-curve and circular field needed to remain legible even where the figures interrupted them.
Fixed figure
The client’s exact technique and pose were non-negotiable, so the surrounding system had to adapt around them.
No element could be adjusted in isolation.
This changed how I approached revision. Instead of treating feedback as a list of independent edits, I tested each change against the system around it.
When the original reference image made the silhouette difficult to resolve cleanly, I asked for a better source photograph of the same technique and orientation. The requirement stayed fixed; the input improved.
Approach
Creating a shared way to review the work
Because the identity carried so much personal and philosophical meaning, simply presenting options and asking, “What do you think?” would have produced weak feedback.
Instead, I treated each presentation as part of the working process.
Round 1 explained what stage the project was in, what the client should evaluate, and what did not need to be resolved yet. I asked him to focus on the overall feeling, required symbolic relationships, and real-world usefulness rather than minor production details.
That framing mattered. After reviewing the presentation, he told me:
“I am glad I did because the purpose of this phase would have been missed on me.”
The presentation had done more than display work. It had helped onboard the client into the review process itself.
From there, each round became progressively narrower. Early reviews invited broader interpretation. Later reviews focused on specific unresolved relationships and, eventually, final approval.
Visualization surfaced requirements that conversation alone had not
Round 1 gave the client something concrete to react to. That reaction exposed information that neither of us had fully articulated at the beginning.
The traditional circular integrity of the yin-yang mattered more than I had understood. The eagle needed a stronger sense of descent and predatory movement. Several visual connections made the composition feel too closed. Color preferences shifted. And as the work became more resolved, the client began identifying subtler concerns about scale, hierarchy, and meaning.
I treated those discoveries as new information about the problem rather than a sequence of isolated change requests.
By Round 2, the feedback had been translated into three explicit goals: restore the yin-yang structure, strengthen the eagle’s movement, and open the composition while preserving the required pose and overall balance.
The distinction became especially important when the client said the eagle felt too large.
That could have meant several different things. Was the eagle too visually dominant? Was its symbolic importance overstated? Or did a man-sized eagle simply feel physically implausible?
Those interpretations would lead to different solutions.
Instead of shrinking it immediately, I went back to the underlying relationship. The answer changed my model of the identity: the eagle was important because it represented the system’s origin, but it was not meant to overpower the practitioner. Its scale problem was primarily physical, not conceptual.
The artifact had made the requirement more precise.
Exploration
Turning subjective feedback into testable decisions
Some feedback began as a feeling: the eagle needed to descend more convincingly, the composition needed to feel more open, or an intersection simply looked wrong.
My job was to identify which variables created that feeling.
For the eagle, I tested rotation, wing position, relative height, direction, silhouette, and interaction with the practitioner rather than relying on a single intuitive redraw.
For the yin-yang, I separated the underlying geometry from the figures layered over it. That allowed me to preserve the traditional S-curve and circular structure even when portions of the form were visually interrupted.
These studies were not produced simply to show process. They helped turn broad reactions into criteria I could evaluate.
The resulting Round 2 identity was more open, more structurally legible, and more clearly directional.
Decision-Making
Validating the model before rebuilding
Round 2 resolved several problems, but it also exposed deeper questions about the hierarchy of the identity.
Rather than continue making surface-level changes, I stopped.
I asked the client to explain the relationship among the eagle, the practitioner, the yin-yang, Wu Tai Chi, and the school itself in greater detail. Then I translated his explanation back into a simplified model:
Yin-yang → foundation and governing principle
Eagle → origin, blueprint, and inspiration
Human → practitioner and realization
That was materially different from the earlier premise of the eagle and practitioner as similarly weighted opposing forces.
I then reduced the remaining work to four explicit requirements:
- Eagle scale — Reduce its physical scale without reducing its conceptual importance.
- Yin-yang / figure relationship — Preserve the positive-negative interaction while resolving the awkward intersection with the practitioner.
- Wu Tai Chi — Increase its prominence so it reads as integral to the practice.
- Color — Move forward with a monochrome primary identity.
Before rebuilding, I asked for one thing: yes or no. Was this now an accurate model of what he meant?
It was.
The final design brief shows how much more precise the shared understanding had become.
Execution / Implementation
From a resolved mark to a usable identity system
Once the core relationships were stable, the focus shifted from exploration to implementation.
The final identity needed to work as a system rather than a single logo.
I developed a family of purpose-built configurations including the Standard Lockup, Emblem, Circular Lockup, horizontal and stacked wordmarks, Social Profile, and Micromark.
Each existed because a different context created a different information or scale requirement.
A detailed mark that works well at large sizes is not automatically the right asset for a tiny digital icon. A wide wordmark solves a different problem from an enclosed circular mark. The goal was not to create variants for completeness; it was to give the client appropriate tools for different situations without requiring him to modify the artwork himself.
The Standard and Reverse marks also became separate, optically corrected assets rather than one file recolored in opposite directions. The identity could remain visually balanced across light and dark contexts without asking the client or a vendor to improvise.
Approval became a release gate
Round 3 was intentionally different from the previous presentations. Exploration was over.
The presentation showed the resolved identity, the larger asset family, color treatments, and applications together so the client could evaluate the system as a whole.
At that point, I explicitly asked for final approval. Approval would trigger final production, quality checks, packaging, and the Brand Reference Guide.
After approval, I shifted into release preparation: checking asset naming, Standard and Reverse distinctions, file formats, digital sizes, official business naming, typography guidance, licensing requirements, and delivery structure.
One late-stage question illustrates why that mattered.
Before packaging the system, I verified whether the formal brand name was ONYX EAGLE CLAW or ONYX EAGLE CLAW WU TAI CHI rather than allowing an assumption from earlier design work to become embedded in the final documentation.
The answer affected naming, hierarchy, and the asset package itself.
Small ambiguities are inexpensive to resolve before release. They become expensive once they are baked into a system.
Designing the handoff for independent use
Delivery was not finished when the files were exported.
The client needed to know what he had, which asset to choose, and how to use it without needing me beside him every time.
The Brand Reference Guide therefore became operational documentation for the identity.
One section explains progressive simplification: when detail or available space decreases, move from the Standard Lockup to the Emblem, Wordmark, Simplified Wordmark, and eventually the Micromark rather than forcing one configuration into every environment.
The Asset Library documents how the delivered files are organized and what the available formats are for. The Quick Reference turns common use cases into direct selection guidance.
The objective was self-sufficiency.
A good handoff should make the client less dependent on the person who created the system, not more.
Supporting adoption after delivery
The support path remained open after handoff.
When the client began thinking about producing branded materials, he came back with a practical observation: having a logo was one thing; knowing how to put it on a shirt well was another.
I helped him evaluate production methods, vendors, garment options, sizing, placement, and which supplied identity configuration was appropriate for different applications. I also offered to review vendor proofs before he approved production.
This was not a new design phase. It was support for the transition from delivered system to real-world use.
Production considerations belonged here, during adoption and implementation, not as an invented constraint driving the original design.
Outcome
The project began with a strong vision, but not every requirement was fully knowable at the beginning.
Through iterative visualization, structured reviews, detailed communication, and repeated validation, that vision became increasingly precise.
The final result was not only a resolved identity. It was a documented system the client could evaluate, approve, navigate, and use across different contexts.
The client described the process this way:
“I sincerely appreciate this experience and how painless you’ve made it for me.”
That mattered because the project contained a great deal of detail. The goal was never to remove that complexity. It was to make it understandable enough for both of us to keep moving through it.
Reflection
Onyx Eagle Claw changed how I think about requirements.
Good discovery matters. There are questions I would ask earlier now, especially when symbolic relationships carry as much weight as visual ones.
But I also learned that discovery cannot eliminate every unknown.
Some information exists before the work begins. Other information becomes available because the stakeholder can finally react to something concrete.
The answer is not endless revision. It is a process that makes emerging information visible, captures it, tests its implications, and deliberately turns it into the next decision.
I also learned more about scope. I delivered substantially more structure and documentation than the project originally required because I saw opportunities to make the finished system more useful. The client benefited from that, but future projects should distinguish more deliberately between required scope, valuable enhancements, and additional work.
Most importantly, the project reinforced something I had been doing for years without always naming it:
My strongest work happens when the problem is still a little messy.
I like finding the relationships underneath the requests, organizing what matters, making the dependencies visible, and building enough shared understanding to move from ambiguity to something workable.
The identity was the output.
The deeper work was getting there together.