<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:media="http://search.yahoo.com/mrss/"
	
	>

<channel>
	<title>Eunmo Kang</title>
	<link>https://eunmokang.com</link>
	<description>Eunmo Kang</description>
	<pubDate>Fri, 09 Oct 2026 03:47:33 +0000</pubDate>
	<generator>https://eunmokang.com</generator>
	<language>en</language>
	
		
	<item>
		<title>Datadog Scorecards Improvement</title>
				
		<link>https://eunmokang.com/Datadog-Scorecards-Improvement</link>

		<pubDate>Fri, 09 Oct 2026 03:47:13 +0000</pubDate>

		<dc:creator>Eunmo Kang</dc:creator>

		<guid isPermaLink="true">https://eunmokang.com/Datadog-Scorecards-Improvement</guid>

		<description>
	Datadog Scorecards Improvement
	
	YEAR2026PROJECT TEAM1 designer1 product manager2 engineers

	RESPONSIBILITYUser Surveys &#38;amp; Interviews Competitive Research End-to-End User Flows Information Architecture Wireframing &#38;amp; Prototyping Engineering Handoff QA


	
	The Scorecards feature in Datadog’s Internal Developer Portal (IDP) lets platform teams define engineering standards and evaluate whether services, repositories, and other entities meet them.
For example, a rule might check whether a service has an owner or an on-call team. It could also check for monitoring, documentation, or appropriate deployment settings. 
Each rule shows an overall score alongside individual entity results, such as pass or fail, so teams can see what needs improvement.


	&#60;img width="4144" height="2264" width_o="4144" height_o="2264" data-src="https://freight.cargo.site/t/original/i/d83956e8310c8893637a74179fea8ea8c064d76c0f14fd431df3c7ba30320da0/Scorecards-intro.png" data-mid="253101922" border="0"  src="https://freight.cargo.site/w/1000/i/d83956e8310c8893637a74179fea8ea8c064d76c0f14fd431df3c7ba30320da0/Scorecards-intro.png" /&#62;



	

	Problem

Users could see whether something passed or failed, but it was hard to understand why.

Built-in rules were easy to enable, but their exact evaluation logic was not visible. Custom rules were flexible, but required users to manage evaluation logic outside Scorecards through Workflows or APIs.

One customer told us that most of the actual work happened elsewhere. To them, Scorecards was mainly a dashboard for reporting results.
	



	
	“Most of the work is outside of Scorecards. Scorecards serves as a reporting dashboard.”
Staff Frontend Engineer at Guild Education


	


	

	&#60;img width="2000" height="1602" width_o="2000" height_o="1602" data-src="https://freight.cargo.site/t/original/i/52f7687b4712b0d4feefb1c381f029efc617e122d30448f7e16d981f75908b96/ootb-rule.png" data-mid="253070869" border="0"  src="https://freight.cargo.site/w/1000/i/52f7687b4712b0d4feefb1c381f029efc617e122d30448f7e16d981f75908b96/ootb-rule.png" /&#62;︎︎︎ Built-in rules were easy to enable, but their exact evaluation logic was not visible.
	&#60;img width="2000" height="1602" width_o="2000" height_o="1602" data-src="https://freight.cargo.site/t/original/i/5771fd11691e2e5c81b7312b8018fe0ba48815af8f617ecef0205a44f805045f/custom-rule.png" data-mid="253070891" border="0"  src="https://freight.cargo.site/w/1000/i/5771fd11691e2e5c81b7312b8018fe0ba48815af8f617ecef0205a44f805045f/custom-rule.png" /&#62;︎︎︎ Custom rules were flexible, but required users to manage evaluation logic outside Scorecards through Workflows or APIs.
	



	


	Research
I started by looking at how users created and maintained rules. I sent a survey to 86 users, received 12 responses, and followed up with six interviews to better understand their workflows and challenges. Participants included architects, SREs, platform engineers, and software engineers.
&#60;img width="2360" height="760" width_o="2360" height_o="760" data-src="https://freight.cargo.site/t/original/i/aa1d97c385bc0cad3e0780a6923aba059c85bd9eeb9a66ab7f68a5a515b8c19c/research.png" data-mid="253070870" border="0"  src="https://freight.cargo.site/w/1000/i/aa1d97c385bc0cad3e0780a6923aba059c85bd9eeb9a66ab7f68a5a515b8c19c/research.png" /&#62;I looked across the entire workflow, including how users worked with Scorecards, wrote rules, managed external systems, and investigated failures. I also explored what they would need to write and manage rules directly in code.


Alongside the user research, I reviewed how related products approached policies, templates, evaluation logic, troubleshooting, and change history.
Four themes consistently emerged. 
Rule logic was often difficult to understand because it was hidden or managed elsewhere. 
External systems also required significant effort to set up and maintain, including mapping results to the right entities, handling API and data changes, and identifying entities missing from evaluation. 
When creating a rule, users also struggled to understand how rules, levels, scope, and evaluation methods worked together. 
Finally, they wanted a way to test new rules on real entities before applying them.

Together, these findings pointed to a connected workflow for understanding, creating, testing, and maintaining standards. A query editor would be one part of that experience. It couldn’t solve the whole problem on its own.


	

	
	
	Unclear rule logic made it difficult for users to trust results, troubleshoot unexpected outcomes, and confidently roll out policies.
	
	


	
	Opportunities
I turned the research into three design principles. Make Datadog’s rules easy to understand by connecting each result to the rule’s source, logic, evaluated data, and execution. Let users create rules directly with data already in Datadog, reducing the need for separate pipelines. And provide guidance so users can write and test their evaluation logic with confidence.

These principles also helped define the MVP. Even as we reduced the scope, we wanted to keep the core workflow connected: understand a rule, write it, and see how it works.


	

	
	&#60;img width="2162" height="762" width_o="2162" height_o="762" data-src="https://freight.cargo.site/t/original/i/988fa18789bf297a007e4f3b808e203d8b7c5c93f3d1f9355e81ab439c45104f/opportunities.png" data-mid="253070871" border="0"  src="https://freight.cargo.site/w/1000/i/988fa18789bf297a007e4f3b808e203d8b7c5c93f3d1f9355e81ab439c45104f/opportunities.png" /&#62;
	


	
	VisioningRULE MANAGEMENT PAGE
The existing rule management page showed which rules were available, but it was difficult to understand where the logic came from or how each rule was evaluated.

&#60;img width="2800" height="1664" width_o="2800" height_o="1664" data-src="https://freight.cargo.site/t/original/i/c966d4b7e0a4bb35969733b3b115ca0913082bbca41d3172f13ea03e9bce0d10/scorecards-manage-current.png" data-mid="253070878" border="0"  src="https://freight.cargo.site/w/1000/i/c966d4b7e0a4bb35969733b3b115ca0913082bbca41d3172f13ea03e9bce0d10/scorecards-manage-current.png" /&#62;

︎︎︎ Old rule management page
I kept the familiar layout and added the rule source and evaluation method directly to the table, making these differences easier to identify at a glance.


	


	
	&#60;img width="2120" height="1200" width_o="2120" height_o="1200" data-src="https://freight.cargo.site/t/original/i/ba7e93989bd49ddb3ab05d13b9e0d3c08e70141b7693a65ecf20256c4f6b88a0/scorecard-manage-new.png" data-mid="253070873" border="0"  src="https://freight.cargo.site/w/1000/i/ba7e93989bd49ddb3ab05d13b9e0d3c08e70141b7693a65ecf20256c4f6b88a0/scorecard-manage-new.png" /&#62;
	

	
	︎︎︎ Updated rule management page
	

	
	
RULE DETAIL PAGE
The rule detail page was an opportunity to make evaluation logic more transparent. The existing experience showed basic information and results, but the logic itself was missing and the information felt disconnected.

&#60;img width="2800" height="1754" width_o="2800" height_o="1754" data-src="https://freight.cargo.site/t/original/i/41920e1585462a041c9495a6c6a965da4537c162c6b80fd8088f78241358ba4b/scorecards-detail-current.png" data-mid="253070877" border="0"  src="https://freight.cargo.site/w/1000/i/41920e1585462a041c9495a6c6a965da4537c162c6b80fd8088f78241358ba4b/scorecards-detail-current.png" /&#62;
︎︎︎ Old rule detail side panel
I first explored expanding the existing side panel and allowing users to edit rule logic directly within it. This would keep users in context, but there wasn’t enough space to review complex logic, investigate issues, and support new functionality. As more information was added, the panel quickly became crowded.

	


	&#60;img width="2804" height="872" width_o="2804" height_o="872" data-src="https://freight.cargo.site/t/original/i/b311df8810699550e93754e4b10aa299490e5e5f9a4d581d27947ac83c5566c5/scorecards-detail-wireframe.png" data-mid="253070874" border="0"  src="https://freight.cargo.site/w/1000/i/b311df8810699550e93754e4b10aa299490e5e5f9a4d581d27947ac83c5566c5/scorecards-detail-wireframe.png" /&#62;


	
	︎︎︎ Early exploration of expanding the side panel
	


I moved the rule details to a dedicated page instead, organizing the experience into clear overview, outcomes, and evaluation sections. This brought the rule source, execution details, and evaluation logic together in one connected experience.

	


	
	
︎︎︎ Rule detail design iterations

&#60;img width="2862" height="3052" width_o="2862" height_o="3052" data-src="https://freight.cargo.site/t/original/i/4e527e90b3953093cfd943136be0f3b4e34d28a895849cd02d9df0c913090066/scorecards-detail-updated.png" data-mid="253070889" border="0"  src="https://freight.cargo.site/w/1000/i/4e527e90b3953093cfd943136be0f3b4e34d28a895849cd02d9df0c913090066/scorecards-detail-updated.png" /&#62;︎︎︎ New rule detail page

	

	
	
RULE CONFIGURATION PAGE
Users had to create a rule with its basic information first and configure its evaluation logic afterward.&#38;nbsp;
That meant they were creating a rule before they could fully understand how it would work.
&#60;img width="2800" height="2022" width_o="2800" height_o="2022" data-src="https://freight.cargo.site/t/original/i/d7f28c0ba3e2b6ba4b97c80c7584177a6df08ff4fb454da1b7fdf0306cdd386c/scorecard-creation-current.png" data-mid="253070876" border="0"  src="https://freight.cargo.site/w/1000/i/d7f28c0ba3e2b6ba4b97c80c7584177a6df08ff4fb454da1b7fdf0306cdd386c/scorecard-creation-current.png" /&#62;︎︎︎ Old rule configuration pageI explored several approaches before reaching the final design.

I started by adding a new step where users could define and test the evaluation logic. I worked closely with the PM and engineers to decide which options to offer, which languages to support, and how to design the interface.

Once we chose Datadog SQL (DDSQL) to define the evaluation logic, I explored a query builder for users unfamiliar with DDSQL. To deliver the improvement sooner, we decided to start with a code editor with a built-in AI assistant.
	




	
	&#60;img width="2880" height="2070" width_o="2880" height_o="2070" data-src="https://freight.cargo.site/t/original/i/a54fdf6b701c46552289dc03d4736cfa3975e98f11ff4e5b847cd39c36f427dc/scorecards-creation-iterations-2.png" data-mid="253070894" border="0"  src="https://freight.cargo.site/w/1000/i/a54fdf6b701c46552289dc03d4736cfa3975e98f11ff4e5b847cd39c36f427dc/scorecards-creation-iterations-2.png" /&#62;
	

	
	I also explored how the preview could support rule creation. It started as a way to show which entities were in scope, then evolved to provide guidance and display query results. This allowed users to understand what to write and see how their logic evaluated each entity before applying the rule.

	


&#60;img width="2880" height="1913" width_o="2880" height_o="1913" data-src="https://freight.cargo.site/t/original/i/bce73d41dd019b531ec4fa23faa557d7104512a9183b3b777c065c837b898d54/preview-iterations.png.png" data-mid="253070880" border="0"  src="https://freight.cargo.site/w/1000/i/bce73d41dd019b531ec4fa23faa557d7104512a9183b3b777c065c837b898d54/preview-iterations.png.png" /&#62;

	
	In the final design, users could choose an evaluation method and configure it within the creation flow. For DDSQL, they could write and test queries, use Datadog’s AI features to help generate SQL, and preview results before completing setup.
	


	
	&#60;img width="2860" height="2918" width_o="2860" height_o="2918" data-src="https://freight.cargo.site/t/original/i/a795287d2874392ded45b08b79a894b7eefaad33d62bce0875abac46baeaa4d4/scorecards-creation-updated.png" data-mid="253070890" border="0"  src="https://freight.cargo.site/w/1000/i/a795287d2874392ded45b08b79a894b7eefaad33d62bce0875abac46baeaa4d4/scorecards-creation-updated.png" /&#62;︎︎︎ Updated rule configuration page


	



	
	The creation flow adapts based on the evaluation method users choose. They can write and test DDSQL directly in Datadog, configure evaluations through Workflows, or use the Scorecards API to submit results from external systems.
Each option provides the relevant setup experience while keeping evaluation methods within a consistent rule creation flow.


	

	&#60;img width="1447" height="1144" width_o="1447" height_o="1144" data-src="https://freight.cargo.site/t/original/i/2672c3fbd007dc1be311b3e45c1aa7b886a08982595cd92490039d051d674105/ddsql.png" data-mid="253070884" border="0"  src="https://freight.cargo.site/w/1000/i/2672c3fbd007dc1be311b3e45c1aa7b886a08982595cd92490039d051d674105/ddsql.png" /&#62;
	&#60;img width="1447" height="808" width_o="1447" height_o="808" data-src="https://freight.cargo.site/t/original/i/ef583d6f61978ad712ba8a50356cd8c7f4a63223105104bb10c66e306c961635/workflow.png" data-mid="253070885" border="0"  src="https://freight.cargo.site/w/1000/i/ef583d6f61978ad712ba8a50356cd8c7f4a63223105104bb10c66e306c961635/workflow.png" /&#62;
	&#60;img width="1447" height="642" width_o="1447" height_o="642" data-src="https://freight.cargo.site/t/original/i/7c928367dd51b80e8c04ecba422aa9a6ad0a49d843a1c5e7a9460aaf6d445b8e/api.png" data-mid="253070886" border="0"  src="https://freight.cargo.site/w/1000/i/7c928367dd51b80e8c04ecba422aa9a6ad0a49d843a1c5e7a9460aaf6d445b8e/api.png" /&#62;



	
	ExecutionThe final design brings evaluation setup into the rule creation flow. Users can choose an evaluation method and complete the relevant configuration in one place. For DDSQL-based rules, they can write and test queries and preview results on real entities before applying the rule.

The updated detail page brings together the rule’s source, evaluation method, results, and available logic and execution details. The management page makes each rule’s source and evaluation method easier to compare at a glance.

Together, these changes are designed to make rules easier to understand and reduce the need to build and maintain evaluation logic in external systems.
	



	
	
	



	
	
Customer responsesI shared this direction with customers and received positive feedback. They valued having the evaluation logic visible on the same page, which gave them a clearer understanding of how a rule worked. They also liked having example scripts they could run right away, which they felt would make it easier to start writing their own logic.
Overall, the feedback reinforced that making rules more transparent and easier to create addressed real customer needs. One customer described the direction as a “game changer” for how they could use Scorecards.


	



	
	&#60;img width="2844" height="1306" width_o="2844" height_o="1306" data-src="https://freight.cargo.site/t/original/i/ac41bd096a54d0fda61064cdaab99b685df48cfb1d734fc7dfe7d5640adaddbf/customer-reponses.png" data-mid="253070881" border="0"  src="https://freight.cargo.site/w/1000/i/ac41bd096a54d0fda61064cdaab99b685df48cfb1d734fc7dfe7d5640adaddbf/customer-reponses.png" /&#62;
	

	
	What I learnedLooking back, this project reinforced a few lessons about understanding technical users and adapting to constraints along the way. Two stood out in particular.


	


	


	Deep understanding builds confidence  in design decisionsHearing users describe their workflows  firsthand gave me the clarity and confidence to make better design decisions.

	A clear plan still needs  room to adaptTechnical challenges and time constraints  required us to continuously adjust our approach while staying focused on the goal.
	




	← Previous project
	
	
	All work
	
	
	
	Next project →
Related work</description>
		
	</item>
		
		
	<item>
		<title>Datadog Campaigns</title>
				
		<link>https://eunmokang.com/Datadog-Campaigns</link>

		<pubDate>Fri, 09 Oct 2026 03:47:15 +0000</pubDate>

		<dc:creator>Eunmo Kang</dc:creator>

		<guid isPermaLink="true">https://eunmokang.com/Datadog-Campaigns</guid>

		<description>
	Datadog Campaigns

	
	
	
YEAR2025PROJECT TEAM1 designer1 product manager2 engineers

	RESPONSIBILITYCompetitive Research End-to-End User Flows Information Architecture Wireframing &#38;amp; Prototyping Engineering Handoff QA


	
	The Scorecards feature in Datadog’s Internal Developer Portal (IDP) helps platform teams define engineering standards and evaluate whether services, repositories, and other entities meet them.
But platform, security, and reliability teams also run time-bound initiatives that require coordination across multiple teams, such as upgrading Kubernetes, fixing dependency issues, reducing cloud costs, or addressing security findings.
Scorecards could show whether teams met ongoing standards, but it wasn’t designed to manage these initiatives. Teams needed a way to define who was responsible, which services and teams were involved, when the work was due, and how much progress had been made.



	&#60;img width="4192" height="2016" width_o="4192" height_o="2016" data-src="https://freight.cargo.site/t/original/i/5c608dd690dfafa9ef99e38412d7001b632fd8633c49d799d2bc56816b96862a/campaigns-intro.png" data-mid="253101929" border="0"  src="https://freight.cargo.site/w/1000/i/5c608dd690dfafa9ef99e38412d7001b632fd8633c49d799d2bc56816b96862a/campaigns-intro.png" /&#62;



	
	Pain points


Through customer calls and feedback from internal users, I identified recurring challenges teams faced when coordinating time-bound initiatives across multiple teams. Ownership, progress updates, and follow-up actions were often scattered across tools like Jira, Slack, and team docs. 
This made it difficult to see who was responsible, how much progress had been made, and what needed to happen next. Teams lacked a single place to understand the status of an initiative and take action on the work that remained.
	



	

	No clear ownershipIt’s unclear who owns each task, making delegation and accountability difficult


	No visibility into progress
Updates are scattered across tools, making it hard to see what’s done and what’s left
	Risk of rework and delaysLack of coordination leads to duplicated efforts or missed deadlines
	



	


	
Opportunities
Our goal was to help teams create and run time-bound initiatives with clear ownership, visibility into progress, and a clear path to completing the work on time.


&#60;img width="2202" height="802" width_o="2202" height_o="802" data-src="https://freight.cargo.site/t/original/i/b4eae6d61ff333c92cc106193013afeb1f9b5df6677455218ac816de5a19e5e0/Opportunites.png" data-mid="253070896" border="0"  src="https://freight.cargo.site/w/1000/i/b4eae6d61ff333c92cc106193013afeb1f9b5df6677455218ac816de5a19e5e0/Opportunites.png" /&#62;
Rather than starting from scratch, we built on the Scorecard rules users already had. By adding scope, participating teams, ownership, and a timeline around those rules, we could turn ongoing standards into actionable initiatives with clear goals and accountability.

	

	
	
Introducing Campaigns
&#60;img width="146" height="146" width_o="146" height_o="146" data-src="https://freight.cargo.site/t/original/i/c15472152357442991091753a2244133f6e7031e9586f1146c0097d74290b145/scorecards-badge.png" data-mid="253070897" border="0" data-scale="8" src="https://freight.cargo.site/w/146/i/c15472152357442991091753a2244133f6e7031e9586f1146c0097d74290b145/scorecards-badge.png" /&#62;
This goal led us to create a new product called Campaigns. It gives teams a shared place to define an initiative, identify the teams and services involved, assign ownership, and track progress toward a deadline.

By building on the data and workflows already in Datadog, Campaigns reduces the need to coordinate work across spreadsheets and other tools. The goal was to turn an initiative into clear, actionable work that teams could understand, own, and complete together.


	


	
	Campaigns gives teams a shared place to define an initiative, align impacted teams, and track progress toward a deadline.
	

	
	Campaigns has two main user groups. Platform engineers need to create and manage campaigns. Developers need to know which of their services are included and what work they have to do.
	




	
	Platform engineerDefine &#38;amp; launch&#60;img width="736" height="780" width_o="736" height_o="780" data-src="https://freight.cargo.site/t/original/i/5a89c192eeeffc4ca52f73308b9db2b490800f53f233153873dcaf37bf86e371/campaign-owner.png" data-mid="253070898" border="0" data-scale="90" src="https://freight.cargo.site/w/736/i/5a89c192eeeffc4ca52f73308b9db2b490800f53f233153873dcaf37bf86e371/campaign-owner.png" /&#62;
	DeveloperUnderstand &#38;amp; act&#60;img width="712" height="546" width_o="712" height_o="546" data-src="https://freight.cargo.site/t/original/i/746be3903a46a66ffe94864b9c50d440a4786f79686d5c38e22b916fe619089b/developer.png" data-mid="253070899" border="0" data-scale="90" src="https://freight.cargo.site/w/712/i/746be3903a46a66ffe94864b9c50d440a4786f79686d5c38e22b916fe619089b/developer.png" /&#62;
	

	
	
Core areas
The needs of these two main user groups led us to focus on three core areas: creating, running, and managing campaigns.

The creation flow would let users define a campaign’s purpose, scope, rules, ownership, and deadline. Once a campaign was running, users needed a place to understand the initiative, take action, and track progress. They also needed a way to manage campaigns over time, including viewing active campaigns, updating their status, and archiving completed work.

	



	
	&#60;img width="3000" height="960" width_o="3000" height_o="960" data-src="https://freight.cargo.site/t/original/i/4e41fa6d1bf9b08737295668df9f40fb91c88da4f8c3b3dbbbbf46f3f2e72fc7/cores.png" data-mid="253070901" border="0"  src="https://freight.cargo.site/w/1000/i/4e41fa6d1bf9b08737295668df9f40fb91c88da4f8c3b3dbbbbf46f3f2e72fc7/cores.png" /&#62;
	



	


	
VisioningCAMPAIGN CONFIGURATION 
I started with campaign creation, which would primarily be handled by platform teams. They needed to define the campaign’s purpose, choose the relevant Scorecard rules, set ownership and a timeline, determine which teams and services were in scope, and provide clear guidance on what participating teams needed to do.

I organized the creation flow into three parts: defining the campaign and its purpose, setting ownership and a timeline, and defining the scope with a preview of the teams and services involved.
&#60;img width="746" height="1578" width_o="746" height_o="1578" data-src="https://freight.cargo.site/t/original/i/ebf9eb187905e5162a311640ccc85988dd5c7f284513fb86bea59ef587184ce8/campaign-configuration-flow.png" data-mid="253070902" border="0" data-scale="30" src="https://freight.cargo.site/w/746/i/ebf9eb187905e5162a311640ccc85988dd5c7f284513fb86bea59ef587184ce8/campaign-configuration-flow.png" /&#62;I translated this flow into an initial wireframe. The form on the left guides users through defining the campaign, while the preview on the right shows which entities and teams are in scope, along with their evaluation results.
&#60;img width="1920" height="1764" width_o="1920" height_o="1764" data-src="https://freight.cargo.site/t/original/i/d146e34399c9ba239810e2b3325ada41af7dd3f900a90355a5e5c70359966d46/campaign-creation-wireframe.png" data-mid="253070903" border="0" data-scale="70" src="https://freight.cargo.site/w/1000/i/d146e34399c9ba239810e2b3325ada41af7dd3f900a90355a5e5c70359966d46/campaign-creation-wireframe.png" /&#62;As the design evolved, I added a dedicated step for guidance and consolidated the earlier steps to keep the overall flow to three steps.
I initially explored structured action items, but each initiative required different types of guidance. We chose a Markdown editor instead, giving campaign owners the flexibility to provide instructions, images, and links without being limited to a fixed format.




	



	
	&#60;img width="2828" height="1416" width_o="2828" height_o="1416" data-src="https://freight.cargo.site/t/original/i/db8a30ce5614b845f7c74c6cef9c4c9ae74d39c940685321227b87dc7a166ee7/campaign-form-iterations.png" data-mid="253070904" border="0"  src="https://freight.cargo.site/w/1000/i/db8a30ce5614b845f7c74c6cef9c4c9ae74d39c940685321227b87dc7a166ee7/campaign-form-iterations.png" /&#62;
	

	
	I then focused on making the preview more useful. I explored different ways to show the campaign scope, participating teams, selected rules, and current evaluation results, along with contextual setup guidance.Rather than simply repeating what users entered in the form, the preview showed what those choices meant in practice. This helped owners understand the campaign’s impact and catch unexpected entities or evaluation results before launching it.


	


	
	&#60;img width="2850" height="1436" width_o="2850" height_o="1436" data-src="https://freight.cargo.site/t/original/i/9772ab641e8ddd4bac16393b2bf4d5050831983cfc6a51dbfda0b1bdd1c23a15/campaign-preview-iterations.png" data-mid="253070905" border="0"  src="https://freight.cargo.site/w/1000/i/9772ab641e8ddd4bac16393b2bf4d5050831983cfc6a51dbfda0b1bdd1c23a15/campaign-preview-iterations.png" /&#62;
	
	


	



	

CAMPAIGN DETAIL PAGE
The campaign detail page is the center of the experience. It needs to give everyone a shared view of the campaign while helping each person focus on what matters to their role.

&#60;img width="2404" height="568" width_o="2404" height_o="568" data-src="https://freight.cargo.site/t/original/i/ed7e84a51dec900dd8b368a83ba774829d3487a5f8ece82024845f6712173697/campaings-detail-needs.png" data-mid="253070907" border="0"  src="https://freight.cargo.site/w/1000/i/ed7e84a51dec900dd8b368a83ba774829d3487a5f8ece82024845f6712173697/campaings-detail-needs.png" /&#62;
Campaign owners need to see overall progress, team status, ownership, and deadlines, with ways to follow up when needed. 
Developers need to quickly find their own entities, see which rules they still needed to meet, and understand what actions to take.
&#60;img width="2466" height="1440" width_o="2466" height_o="1440" data-src="https://freight.cargo.site/t/original/i/4f6787befa537304cec8f2ed0927308a8f907f764002da7392362a2fca0cd1c2/campaings-detail-wireframe.png" data-mid="253070908" border="0"  src="https://freight.cargo.site/w/1000/i/4f6787befa537304cec8f2ed0927308a8f907f764002da7392362a2fca0cd1c2/campaings-detail-wireframe.png" /&#62;
I organized the page from a high-level summary down to more detailed information.
The header showed the campaign name, owner, timeline, description, and key actions.
Below that was an overview of the campaign’s progress, followed by individual entities where users could see how much of the required work had been completed.
This hierarchy was designed around the needs of different users. Shared campaign information came first, while the more detailed entity-level information that developers would use more often came below.As I moved into high-fidelity design, I explored different ways to organize the information. I focused on what to prioritize, how much information to show at once, and how to make important details easy to find.



	


	
	&#60;img width="4570" height="5683" width_o="4570" height_o="5683" data-src="https://freight.cargo.site/t/original/i/0b5f7a1bc8f3f7238d8641d4ad9dc38b1dab12f09f607b834028f5a2274c1690/detail-iterations-2.png" data-mid="253070912" border="0"  src="https://freight.cargo.site/w/1000/i/0b5f7a1bc8f3f7238d8641d4ad9dc38b1dab12f09f607b834028f5a2274c1690/detail-iterations-2.png" /&#62;
	

	
	
&#38;nbsp;CAMPAIGN MANAGEMENT PAGE
The management page needs to give platform engineers a place to step back and see multiple campaigns at once, track their status, timelines, and completion rates, and make changes when needed.

&#60;img width="1800" height="568" width_o="1800" height_o="568" data-src="https://freight.cargo.site/t/original/i/5ac1e7506bd6523fbf877bf50c13eacef8e86b053c3f9f1dbc2f130d12f7cb2f/campaign-manage-platform.png" data-mid="253070910" border="0" data-scale="75" src="https://freight.cargo.site/w/1000/i/5ac1e7506bd6523fbf877bf50c13eacef8e86b053c3f9f1dbc2f130d12f7cb2f/campaign-manage-platform.png" /&#62;
I created the wireframe to bring all campaigns into one view, with navigation and filters to help users focus on what was most relevant to them.&#38;nbsp;Each campaign showed key information such as its name, status, scope, timeline, and overall score.

This made it easier to review progress, spot campaigns that needed attention, and take the next step, whether that was viewing details, editing a campaign, or updating its status.
&#60;img width="2808" height="1764" width_o="2808" height_o="1764" data-src="https://freight.cargo.site/t/original/i/136fe8318fb8f867d4c011485ad8f48482e8c9989f1d3ea168fc3d42b478def5/campaings-manage-wireframe.png" data-mid="253070911" border="0" data-scale="90" src="https://freight.cargo.site/w/1000/i/136fe8318fb8f867d4c011485ad8f48482e8c9989f1d3ea168fc3d42b478def5/campaings-manage-wireframe.png" /&#62;


	


	
	As I moved into high-fidelity design, I explored several layouts, including tables, standard cards, and horizontal cards. I compared how well each option helped users scan key campaign information and compare progress across multiple campaigns.

I also considered how the layout could give Campaigns its own visual identity while clearly distinguishing it from the existing Scorecards experience.
	


	
	&#60;img width="5200" height="2974" width_o="5200" height_o="2974" data-src="https://freight.cargo.site/t/original/i/ab2c9ecda4a3299d6d50b83f0e73eddcad6926166285bad5e79e70e5f31645ee/campaign-manage-iterations.png" data-mid="253070916" border="0"  src="https://freight.cargo.site/w/1000/i/ab2c9ecda4a3299d6d50b83f0e73eddcad6926166285bad5e79e70e5f31645ee/campaign-manage-iterations.png" /&#62;
	


	
	ExecutionThe final Campaigns experience brings initiative setup, guidance, and progress tracking into one place.

Campaign owners can define the scope, assign ownership, set a timeline, select rules, and provide clear guidance for participating teams. Before launching, they can preview who and what is affected. Once the campaign is running, teams can see what they need to do, take action, and track progress toward the deadline.

By bringing ownership, progress, and action together in Datadog, Campaigns gives teams a shared view of the initiative and reduces the need to coordinate work across spreadsheets, Slack, and other tools.
	


	
	
	



	
	OutcomesIn the first three months after launch, 46 organizations created 89 campaigns, showing early adoption of the new experience.
Customer feedback also reinforced the value of bringing this work into Datadog. One customer used Campaigns to track security initiatives that had previously been managed in spreadsheets. Another expected it to save significant time compared with their existing process. A third used it to coordinate upgrades and retire outdated functionality across the organization while maintaining service maturity standards.
These early adoption signals and customer feedback suggested that Campaigns was addressing a real need for a shared way to track and coordinate cross-team initiatives.


	




	
	&#60;img width="3710" height="1784" width_o="3710" height_o="1784" data-src="https://freight.cargo.site/t/original/i/f8d4e1ea8b211195b75c33185743990cc8d78d0eea3a87190182afdcc0de4ddc/campaigns-outcomes.png" data-mid="253070921" border="0"  src="https://freight.cargo.site/w/1000/i/f8d4e1ea8b211195b75c33185743990cc8d78d0eea3a87190182afdcc0de4ddc/campaigns-outcomes.png" /&#62;
	


	
	What I learnedBuilding Campaigns also gave me a few lessons that shaped how I approach product design. Here are three that stood out.


	
	

	Progress is meaningful only  when it leads to action
Progress needs to connect to ownership, deadlines, and the work that remains.
	Different roles need different levels of information
Campaign owners need to identify teams that are blocked, while developers need clear next steps for the services they own.
	Communication is part of  coordination
Making work visible wasn’t enough.  Campaign owners also needed ways to notify teams and follow up.




	← Previous project
	
	
	All work
	
	
	
	Next project →
Related work</description>
		
	</item>
		
		
	<item>
		<title>Campaign Notifications</title>
				
		<link>https://eunmokang.com/Campaign-Notifications</link>

		<pubDate>Fri, 09 Oct 2026 03:47:18 +0000</pubDate>

		<dc:creator>Eunmo Kang</dc:creator>

		<guid isPermaLink="true">https://eunmokang.com/Campaign-Notifications</guid>

		<description>
	Campaign Notifications
	
	
	
YEAR2026PROJECT TEAM1 designer1 product manager1 engineer
	RESPONSIBILITYUser InterviewsCompetitive ResearchEnd-to-End User FlowsInformation ArchitectureWireframing &#38;amp; PrototypingEngineering HandoffQA


	
	IDP Campaigns is designed to drive organizational improvements through time-bound initiatives, such as migrations and dependency fixes, by identifying gaps and prompting teams to take action.
However, driving completion requires more than surfacing issues. Teams need clear prioritization, actionable guidance, and effective nudges to act.



	&#60;img width="4188" height="2280" width_o="4188" height_o="2280" data-src="https://freight.cargo.site/t/original/i/e570d260deefffc3bdaa5fcd4320b6b25d2cfb1f64e37fa1b8b088efa226784a/campaign-notification-intro.png" data-mid="253101942" border="0"  src="https://freight.cargo.site/w/1000/i/e570d260deefffc3bdaa5fcd4320b6b25d2cfb1f64e37fa1b8b088efa226784a/campaign-notification-intro.png" /&#62;



	
	Discovery


I looked at the campaign owner’s workflow from launch through completion. Their role didn’t end after notifying teams. They needed to monitor progress, provide guidance, and follow up on unfinished work throughout the campaign.
	



	
	&#60;img width="3246" height="102" width_o="3246" height_o="102" data-src="https://freight.cargo.site/t/original/i/39a9179990b87ef4f2f8a0fc5135b2827d903ffbf238978144e4bf19eb84a923/campaign-owner-flow.png" data-mid="253070925" border="0"  src="https://freight.cargo.site/w/1000/i/39a9179990b87ef4f2f8a0fc5135b2827d903ffbf238978144e4bf19eb84a923/campaign-owner-flow.png" /&#62;
	

	


	Mapping this journey revealed three distinct communication needs: getting teams started, guiding them along the way, and following up on unfinished work.



&#60;img width="2847" height="1031" width_o="2847" height_o="1031" data-src="https://freight.cargo.site/t/original/i/6e274bd38a23161b3477d7a8bfd53dc2b80ceb47b69d069a843306789a5708c7/campaign-purposes.png" data-mid="253070926" border="0"  src="https://freight.cargo.site/w/1000/i/6e274bd38a23161b3477d7a8bfd53dc2b80ceb47b69d069a843306789a5708c7/campaign-purposes.png" /&#62;At launch, teams need to understand the campaign’s purpose and their responsibilities. As work progresses, they need guidance and reminders. As the deadline approaches, owners need to follow up with teams that still have work remaining.

This made it clear that improving a one-time notification modal wouldn’t be enough. We needed to support communication throughout the campaign, with different types of outreach for each stage.

	



	


	Existing limitations
The existing notification experience was mainly designed to get a campaign started. What was missing was support for keeping the work moving and helping teams reach completion.

Three key limitations stood out:

1. Manual communicationNotifications were limited to a one-time, fixed message, leaving campaign owners to handle follow-ups manually.

2. Lack of visibilityThere was no central place to review notification history or past conversations, making it difficult to know which teams had been contacted and what had already been discussed.

3. Limited actionabilityNotifications shared campaign information, but didn’t make it clear what teams needed to do next.

	


	
	“Everything is automated except communication. The only manual work remaining is sending messages,  nudging teams, and following up.”SE2, Frontend Framework at Datadog
	



	
	Opportunities

Based on these findings, I saw an opportunity to move from one-off, manual notifications to automated communication throughout the campaign, while giving owners more visibility and control over their outreach.

I focused the experience on two areas:

1. Notification configuration
Owners could decide when and where to send notifications, customize the message, and automate follow-ups based on triggers.

2. Tracking and management
Owners could monitor communication activity, review team-level history, and adjust their outreach as the campaign progressed.


	


	


	&#60;img width="1207" height="498" width_o="1207" height_o="498" data-src="https://freight.cargo.site/t/original/i/3d841d4fb57f4401b103e8974da05ff45f54e799b7125bd000b1eeb00f16aee7/opportunity-automated.png" data-mid="253070943" border="0"  src="https://freight.cargo.site/w/1000/i/3d841d4fb57f4401b103e8974da05ff45f54e799b7125bd000b1eeb00f16aee7/opportunity-automated.png" /&#62;
	&#60;img width="1207" height="514" width_o="1207" height_o="514" data-src="https://freight.cargo.site/t/original/i/39e152bfe1db5dde8c716b88457858fc69def4e2e8a1d8d08c4d69f88fcba8fc/opportunity-tracking.png" data-mid="253070944" border="0"  src="https://freight.cargo.site/w/1000/i/39e152bfe1db5dde8c716b88457858fc69def4e2e8a1d8d08c4d69f88fcba8fc/opportunity-tracking.png" /&#62;
	


	
	
Workflow mapping
Before designing the screens, I mapped the end-to-end notification experience, from initial setup to ongoing management.

	



	
	&#60;img width="3426" height="1604" width_o="3426" height_o="1604" data-src="https://freight.cargo.site/t/original/i/1329bede01743d5f9214226e64e8ac5f6a0bc5b958ace389828a2df00cb99fbc/notifications-workflow.png" data-mid="253070929" border="0"  src="https://freight.cargo.site/w/1000/i/1329bede01743d5f9214226e64e8ac5f6a0bc5b958ace389828a2df00cb99fbc/notifications-workflow.png" /&#62;
	


	
	The setup flow moves from choosing the notification type and trigger to selecting destinations, creating the message, and reviewing the configuration before launch. I explored different options at each step, including one-time and recurring notifications, scheduled and condition-based triggers, team-specific destinations, and customizable messages.
The flow then continues into ongoing management. Owners can review all notifications, drill into configuration and send history, see communication activity for individual teams, and take follow-up actions such as sending another message, editing the notification, or pausing it.
This helped me think beyond notification creation and design for the full communication lifecycle of a campaign.Using the flows as a starting point, I used AI to quickly explore and compare different approaches to notification setup and management.


	




	


	Setup exploration&#38;nbsp;TEMPLATE-LED CONFIGURATION
I first explored a template-based approach to notification setup. Users would choose between a one-time or recurring notification, then select a template based on their needs. Depending on the template, notifications could be sent immediately, on a schedule, or when a specific condition was met.


	

	
	
	


	
	︎︎︎ Template-led notification configuration prototypeThis approach could simplify complex notification setups by providing common patterns to start from. However, it also introduced unnecessary complexity for simpler tasks. Users had to understand the differences between templates before getting started, and even sending a single message required an additional selection step.


	



	
	&#60;img width="930" height="498" width_o="930" height_o="498" data-src="https://freight.cargo.site/t/original/i/f302a22e28f2efa4855a217f25e715bab4f0f3b022484a41777a00c61d416978/creation1-pros.png" data-mid="253070932" border="0"  src="https://freight.cargo.site/w/930/i/f302a22e28f2efa4855a217f25e715bab4f0f3b022484a41777a00c61d416978/creation1-pros.png" /&#62;
	&#60;img width="930" height="498" width_o="930" height_o="498" data-src="https://freight.cargo.site/t/original/i/5c7330ce3c81d55e6456cc18480e01e8b9c275eefaf97147f490bd8545372465/creation1-cons.png" data-mid="253070931" border="0"  src="https://freight.cargo.site/w/930/i/5c7330ce3c81d55e6456cc18480e01e8b9c275eefaf97147f490bd8545372465/creation1-cons.png" /&#62;
	

	



	
STEP-BY-STEP CONFIGURATIONThe second approach guided users through the setup one step at a time. Instead of choosing a template, users could turn different notification types on or off, then configure each one through a guided flow.



	


	
	
	


	

	︎︎︎ Step-by-step notification configuration prototype
Breaking the setup into smaller steps reduced the number of decisions users had to make at once, making complex configurations easier to work through. The tradeoff was reduced visibility, as users couldn’t see the full setup at a glance and had to move back and forth between steps to review or change their choices.
	

	
	
	&#60;img width="930" height="514" width_o="930" height_o="514" data-src="https://freight.cargo.site/t/original/i/2fc016bd68dff68fdbc9a66e15c6650354a54e264c8d5c5ed3935ad919d4422f/creation2-pros.png" data-mid="253070933" border="0"  src="https://freight.cargo.site/w/930/i/2fc016bd68dff68fdbc9a66e15c6650354a54e264c8d5c5ed3935ad919d4422f/creation2-pros.png" /&#62;
	&#60;img width="930" height="514" width_o="930" height_o="514" data-src="https://freight.cargo.site/t/original/i/5bba36db340a679215535d97aa0e637c419e179b5553dfebd81eb5c587796668/creation2-cons.png" data-mid="253070934" border="0"  src="https://freight.cargo.site/w/930/i/5bba36db340a679215535d97aa0e637c419e179b5553dfebd81eb5c587796668/creation2-cons.png" /&#62;
	


	
	


	
	Tracking &#38;amp; management exploration
MODAL-BASED MANAGEMENT
The first approach I explored for notification tracking and management was a separate modal. The existing “Create notification” button would become “Manage notifications,” giving owners one place to view notifications, review send history and team responses, and create new notifications.


	


	
	
	



	

	︎︎︎ Modal-based notification management prototype

This kept creation and management together without adding clutter to the campaign page as the number of notifications increased. The tradeoff was reduced visibility and context. Owners had to open the modal to check notification activity, making it harder to see communication alongside campaign progress.
	


	
	&#60;img width="930" height="350" width_o="930" height_o="350" data-src="https://freight.cargo.site/t/original/i/3996b510e89bcdb13104b18229ae0199653a8a5cae47ff9a900f3da7f458c102/tracking1-pros.png" data-mid="253070935" border="0"  src="https://freight.cargo.site/w/930/i/3996b510e89bcdb13104b18229ae0199653a8a5cae47ff9a900f3da7f458c102/tracking1-pros.png" /&#62;
	&#60;img width="930" height="350" width_o="930" height_o="350" data-src="https://freight.cargo.site/t/original/i/4bef8b9613d9e72f1c4e9897bb2bfde42ad35d08c303ccb3ca29cac01b0d80aa/tracking1-cons.png" data-mid="253070936" border="0"  src="https://freight.cargo.site/w/930/i/4bef8b9613d9e72f1c4e9897bb2bfde42ad35d08c303ccb3ca29cac01b0d80aa/tracking1-cons.png" /&#62;
	

	
	

EMBEDDED MANAGEMENT
The second approach brought notification management directly into the campaign page, making the notification list visible without requiring owners to open a separate view.
Selecting a notification opened a side panel with its details and history. From there, owners could drill into team-level communication in a second panel to review messages and responses.
	


	
	
	


	
	︎︎︎ Embedded notification management prototype
This made it easier to view notification activity alongside campaign progress and keep communication in context. The tradeoff was scalability, as a growing number of notifications could make the campaign page longer and more crowded.
	



	
	&#60;img width="930" height="350" width_o="930" height_o="350" data-src="https://freight.cargo.site/t/original/i/7efc7777bd11ebad3e6f3017291f53b2c26c22a9f7f3ca936204eae98d836358/tracking2-pros.png" data-mid="253070937" border="0"  src="https://freight.cargo.site/w/930/i/7efc7777bd11ebad3e6f3017291f53b2c26c22a9f7f3ca936204eae98d836358/tracking2-pros.png" /&#62;
	&#60;img width="930" height="350" width_o="930" height_o="350" data-src="https://freight.cargo.site/t/original/i/b9804baeb5ed70c90b8daf0b84de648a4ab21e2196797d856f0403b8127b79a0/tracking2-cons.png" data-mid="253070938" border="0"  src="https://freight.cargo.site/w/930/i/b9804baeb5ed70c90b8daf0b84de648a4ab21e2196797d856f0403b8127b79a0/tracking2-cons.png" /&#62;
	


	
	ExecutionAfter reviewing the different approaches and their tradeoffs with the team, we aligned on a direction that balanced flexibility, visibility, and implementation scope.

CONFIGURATION

&#60;img width="1564" height="880" width_o="1564" height_o="880" data-src="https://freight.cargo.site/t/original/i/d282b41f07c15cf931af99e8bfa3877c2ae0ba7fa7f7f577bd4c1065419d79de/notification-configuration-mvp.png" data-mid="253070939" border="0" data-scale="94" src="https://freight.cargo.site/w/1000/i/d282b41f07c15cf931af99e8bfa3877c2ae0ba7fa7f7f577bd4c1065419d79de/notification-configuration-mvp.png" /&#62;We kept the full notification setup in a single view, allowing owners to turn each notification type on or off. They could send a one-time launch message or combine it with automated progress updates and a due-date reminder. This gave owners flexibility without requiring them to learn a template system, while making the overall configuration easier to review and edit.
For the MVP, we focused on schedule-based notifications and left condition-based triggers for future iterations. This reduced implementation scope while still supporting the core communication needs we had identified.

TRACKING &#38;amp; MANAGEMENT
&#60;img width="1564" height="880" width_o="1564" height_o="880" data-src="https://freight.cargo.site/t/original/i/9b0ad68ffc5d4165dbf4af2488ccfd234d746af9a11b1b26d9022993c4a2a39b/notification-tracking-mvp.png" data-mid="253070940" border="0" data-scale="94" src="https://freight.cargo.site/w/1000/i/9b0ad68ffc5d4165dbf4af2488ccfd234d746af9a11b1b26d9022993c4a2a39b/notification-tracking-mvp.png" /&#62;We embedded notification management directly into the campaign detail page so owners could review communication alongside campaign progress. Based on the expected number of notifications per campaign, we determined that the added content was unlikely to overwhelm the page.

Side panels provided deeper access to each notification’s configuration, send history, and team-level communication. Owners could also edit or stop upcoming notifications independently as the campaign progressed.I initially grouped notification types into one setup flow because they formed a single communication plan. The engineer favored separate configuration because each type had a different lifecycle and editing behavior. We kept setup together, but listed and edited each notification type independently, preserving a simple setup while making the scope of each edit clear.


	



	
	
	



	
	What I learned
Through this project, I learned a few lessons that changed how I think about automation, communication, and collaboration.
	
	


	
	Automation should feel  predictable
Users need to understand what will  be sent, when it will be sent, and who  will receive it.


	Design for both senders  and recipients
Campaign owners configure notifications,  but developers experience their frequency, clarity, timing, and relevance. We designed reminders to stop once a team completed the work.
	Design and engineering can be right at different layers
Different design and engineering perspectives led to a solution that better served both users and the system.
	




	← Previous project
	
	
	All work
	
	
	
	Next project →
Related work</description>
		
	</item>
		
		
	<item>
		<title>Dash 2021 Conference</title>
				
		<link>https://eunmokang.com/Dash-2021-Conference</link>

		<pubDate>Fri, 09 Oct 2026 03:47:21 +0000</pubDate>

		<dc:creator>Eunmo Kang</dc:creator>

		<guid isPermaLink="true">https://eunmokang.com/Dash-2021-Conference</guid>

		<description>Dash 2021 ConferenceDirecting: Eunmo KangDesign: Jenny KimAnimation: Lupita Djody


Dash is Datadog’s annual conference focused on building and scaling the next generation of applications, infrastructure, and technical teams. 
I developed the visual identity for its inaugural conference in 2018 and continued to evolve it each year while maintaining its core identity.

For Dash 2021, we introduced fully 3D graphics as the main visual elements, bringing a new dimension to the conference’s visual identity.



&#60;img width="2600" height="1401" width_o="2600" height_o="1401" data-src="https://freight.cargo.site/t/original/i/d5886767c5d7864fe12ea082a30c3e55774217fd36237e34870b85e6253654e3/2-dashlogo_variations.png" data-mid="253070956" border="0"  src="https://freight.cargo.site/w/1000/i/d5886767c5d7864fe12ea082a30c3e55774217fd36237e34870b85e6253654e3/2-dashlogo_variations.png" /&#62;
&#60;img width="2292" height="1234" width_o="2292" height_o="1234" data-src="https://freight.cargo.site/t/original/i/08302b2d8a298727afbd2ba8b672b38c783b25910b86a519f3557c3e21377d7e/3-typography.jpg" data-mid="253070957" border="0"  src="https://freight.cargo.site/w/1000/i/08302b2d8a298727afbd2ba8b672b38c783b25910b86a519f3557c3e21377d7e/3-typography.jpg" /&#62;
&#60;img width="2500" height="1500" width_o="2500" height_o="1500" data-src="https://freight.cargo.site/t/original/i/b4d9b93ef318adb6703c61be0a1a74b2cf9a21aa3e84eed9df6a2be29d12b449/4-color.png" data-mid="253070958" border="0"  src="https://freight.cargo.site/w/1000/i/b4d9b93ef318adb6703c61be0a1a74b2cf9a21aa3e84eed9df6a2be29d12b449/4-color.png" /&#62;
&#60;img width="2600" height="1400" width_o="2600" height_o="1400" data-src="https://freight.cargo.site/t/original/i/d558e4d90f037d719e07c04983b123a58614d7254701b44bde46b2affa88ae4e/5_hex_basic_elements.png" data-mid="253070959" border="0"  src="https://freight.cargo.site/w/1000/i/d558e4d90f037d719e07c04983b123a58614d7254701b44bde46b2affa88ae4e/5_hex_basic_elements.png" /&#62;

&#60;img width="2600" height="1400" width_o="2600" height_o="1400" data-src="https://freight.cargo.site/t/original/i/642889ad3187afa9aa666001ffafb0cfa9a5b57e4f52c74e7033acc2ff34f43f/6_hex_blue.png" data-mid="253070960" border="0"  src="https://freight.cargo.site/w/1000/i/642889ad3187afa9aa666001ffafb0cfa9a5b57e4f52c74e7033acc2ff34f43f/6_hex_blue.png" /&#62;
&#60;img width="2600" height="1400" width_o="2600" height_o="1400" data-src="https://freight.cargo.site/t/original/i/656a557c85ffdcb0f634cdc5e0b69f0c9ab537314a563f1c12a73316396e2355/7_multicolor-1.png" data-mid="253070961" border="0"  src="https://freight.cargo.site/w/1000/i/656a557c85ffdcb0f634cdc5e0b69f0c9ab537314a563f1c12a73316396e2355/7_multicolor-1.png" /&#62;



&#60;img width="2600" height="1400" width_o="2600" height_o="1400" data-src="https://freight.cargo.site/t/original/i/693db576323b4b3d2b9b1b7a1f8dda7b086e72ae7c4ae8905ab7a224f803d700/9_banners.png" data-mid="253070963" border="0"  src="https://freight.cargo.site/w/1000/i/693db576323b4b3d2b9b1b7a1f8dda7b086e72ae7c4ae8905ab7a224f803d700/9_banners.png" /&#62;
&#60;img width="2600" height="1400" width_o="2600" height_o="1400" data-src="https://freight.cargo.site/t/original/i/7b45bf6e1453ee4365be5233958893a01c2372c79b4e598473d5307915bf3a45/11_mailer.png" data-mid="253070964" border="0"  src="https://freight.cargo.site/w/1000/i/7b45bf6e1453ee4365be5233958893a01c2372c79b4e598473d5307915bf3a45/11_mailer.png" /&#62;

&#60;img width="2600" height="1400" width_o="2600" height_o="1400" data-src="https://freight.cargo.site/t/original/i/086575949c79ee7bb22b8c7b19bde653e72f3404028151e7e640ca4e61f716a7/12_badges.png" data-mid="253070965" border="0"  src="https://freight.cargo.site/w/1000/i/086575949c79ee7bb22b8c7b19bde653e72f3404028151e7e640ca4e61f716a7/12_badges.png" /&#62;
&#60;img width="2600" height="1400" width_o="2600" height_o="1400" data-src="https://freight.cargo.site/t/original/i/e16372739a0629ef61dfd5c11ae9f4a1dd6d84d1163847f89c1f383f0a7491f0/13_t-shirts.png" data-mid="253070966" border="0"  src="https://freight.cargo.site/w/1000/i/e16372739a0629ef61dfd5c11ae9f4a1dd6d84d1163847f89c1f383f0a7491f0/13_t-shirts.png" /&#62;
&#60;img width="6000" height="3600" width_o="6000" height_o="3600" data-src="https://freight.cargo.site/t/original/i/4cb8d6744a722a9c6c280b30942ddd1333790b36197e5cbd79a534b4ae421800/14_totes.png" data-mid="253070967" border="0"  src="https://freight.cargo.site/w/1000/i/4cb8d6744a722a9c6c280b30942ddd1333790b36197e5cbd79a534b4ae421800/14_totes.png" /&#62;




	← Previous project
	
	
	All work
	
	
	
	Next project →
Related work</description>
		
	</item>
		
		
	<item>
		<title>Datadog Partner Marketing Visual Identit</title>
				
		<link>https://eunmokang.com/Datadog-Partner-Marketing-Visual-Identit</link>

		<pubDate>Fri, 09 Oct 2026 03:47:23 +0000</pubDate>

		<dc:creator>Eunmo Kang</dc:creator>

		<guid isPermaLink="true">https://eunmokang.com/Datadog-Partner-Marketing-Visual-Identit</guid>

		<description>Datadog Partner Marketing Visual Identity


Datadog provides a program for Datadog Partner Network (DPN) members that is designed to help partners enrich their product offerings and grow their businesses through stronger engagement with Datadog.&#38;nbsp;With the Partner Marketing team, I created DPN's visual identity system as an extension of the Datadog brand to support the company’s initiatives around partnership and growth.

&#60;img width="2800" height="1388" width_o="2800" height_o="1388" data-src="https://freight.cargo.site/t/original/i/e7e30f81ded542e2e5fa95e99aedded93cce806e9a1273dfd958158287375f38/DPN_detail_00_hero.png" data-mid="253070970" border="0"  src="https://freight.cargo.site/w/1000/i/e7e30f81ded542e2e5fa95e99aedded93cce806e9a1273dfd958158287375f38/DPN_detail_00_hero.png" /&#62;
&#60;img width="2292" height="1290" width_o="2292" height_o="1290" data-src="https://freight.cargo.site/t/original/i/9e672cce045009e6de8045510259151393fc00284cd3d7892b42e31d8c4dc432/DPN_detail_01.png" data-mid="253070971" border="0"  src="https://freight.cargo.site/w/1000/i/9e672cce045009e6de8045510259151393fc00284cd3d7892b42e31d8c4dc432/DPN_detail_01.png" /&#62;
&#60;img width="1146" height="645" width_o="1146" height_o="645" data-src="https://freight.cargo.site/t/original/i/c0cf999ca58dc26d4eeaec9e496a3ff3ab125bbb79520076576a66969b009e81/DPN_detail_03-preload.png" data-mid="253070979" border="0"  src="https://freight.cargo.site/w/1000/i/c0cf999ca58dc26d4eeaec9e496a3ff3ab125bbb79520076576a66969b009e81/DPN_detail_03-preload.png" /&#62;

&#60;img width="2292" height="1290" width_o="2292" height_o="1290" data-src="https://freight.cargo.site/t/original/i/47c53cf19764209e122f5aeb4d1f476c4c88a72063fa9f33cdda996232d5111c/DPN_detail_07.jpg" data-mid="253070978" border="0"  src="https://freight.cargo.site/w/1000/i/47c53cf19764209e122f5aeb4d1f476c4c88a72063fa9f33cdda996232d5111c/DPN_detail_07.jpg" /&#62;
&#60;img width="2292" height="1290" width_o="2292" height_o="1290" data-src="https://freight.cargo.site/t/original/i/ab9a5eb182b0efd7b4a2491d007e11a89d0773f11c7a148f12e138d32bbdb6cf/DPN_detail_08.png" data-mid="253070973" border="0"  src="https://freight.cargo.site/w/1000/i/ab9a5eb182b0efd7b4a2491d007e11a89d0773f11c7a148f12e138d32bbdb6cf/DPN_detail_08.png" /&#62;

︎︎︎ Partner tier badges with different tracks and the usage guidelines


&#60;img width="2292" height="1290" width_o="2292" height_o="1290" data-src="https://freight.cargo.site/t/original/i/9a52d836751f2cb35a876bb586644bb118c9939c35b5263c77391ad7f77c1286/DPN_detail_09.png" data-mid="253070974" border="0"  src="https://freight.cargo.site/w/1000/i/9a52d836751f2cb35a876bb586644bb118c9939c35b5263c77391ad7f77c1286/DPN_detail_09.png" /&#62;
&#60;img width="2292" height="1290" width_o="2292" height_o="1290" data-src="https://freight.cargo.site/t/original/i/a98112ab54a0339635b120601eb8ff80eec1bfce9cd686af4c0bc23f40381d06/DPN_detail_10.png" data-mid="253070975" border="0"  src="https://freight.cargo.site/w/1000/i/a98112ab54a0339635b120601eb8ff80eec1bfce9cd686af4c0bc23f40381d06/DPN_detail_10.png" /&#62;


&#60;img width="1116" height="1292" width_o="1116" height_o="1292" data-src="https://freight.cargo.site/t/original/i/7aa8499e0b547f5ddea9da2b0d133c60a539a266d8f421759719c8f8af1d6099/DPN_detail_11.png" data-mid="253070976" border="0"  src="https://freight.cargo.site/w/1000/i/7aa8499e0b547f5ddea9da2b0d133c60a539a266d8f421759719c8f8af1d6099/DPN_detail_11.png" /&#62;
&#60;img width="1116" height="1292" width_o="1116" height_o="1292" data-src="https://freight.cargo.site/t/original/i/52f8642223135b8490b65a11432760afeff3a459049d5f9b9a634dc14fe573ef/DPN_detail_12.png" data-mid="253070977" border="0"  src="https://freight.cargo.site/w/1000/i/52f8642223135b8490b65a11432760afeff3a459049d5f9b9a634dc14fe573ef/DPN_detail_12.png" /&#62;
︎︎︎ Partner Directory webpage and DPN Newsletter



	← Previous project
	
	
	All work
	
	
	
	Next project →
Related work</description>
		
	</item>
		
		
	<item>
		<title>Datadog Web UI Library</title>
				
		<link>https://eunmokang.com/Datadog-Web-UI-Library</link>

		<pubDate>Fri, 09 Oct 2026 03:47:24 +0000</pubDate>

		<dc:creator>Eunmo Kang</dc:creator>

		<guid isPermaLink="true">https://eunmokang.com/Datadog-Web-UI-Library</guid>

		<description>
	Datadog Web UI Library
	
Design: Eunmo Kang, Michael HoangWeb Coding: Won Choi


	



&#60;img width="3800" height="1853" width_o="3800" height_o="1853" data-src="https://freight.cargo.site/t/original/i/5e66a9efc686f022f8ade2cd0dfe557d156f5d329bb0418b1c518bb58c855e8a/dd-web-mockup.jpg" data-mid="253070989" border="0"  src="https://freight.cargo.site/w/1000/i/5e66a9efc686f022f8ade2cd0dfe557d156f5d329bb0418b1c518bb58c855e8a/dd-web-mockup.jpg" /&#62;
	


	Problem
When I joined Datadog, there was not a web guideline or an UI assets library. This fact allowed so many inconsistent styles throughout the Datadog web pages since there was not a specific rule for designers to follow. As the design team was growing up, a specific web UI asset library and guidelines were necessary to make web component styles consistent.
Goals



Making inconsistent visual elements consistent on the web pagesCreating a web UI asset library and guidelines for designers and developers











Solutions

Teamed up with the Websites team, I started to investigate and collected inconsistent visual elements such as types, spaces, buttons, and colors used on Datadog web pages, and cleaned up to make them consistent. 
TYPOGRAPHY
Even though there was a type hierarchy setting, some random font sizes and inconsistent spacings between type classes were existing on the web pages. We’ve replaced the random size fonts with the most similar existing type classes except on some pages that might cause bigger issues. The spacings between type classes also have been newly defined. &#38;nbsp;
	



	&#60;img width="2020" height="1738" width_o="2020" height_o="1738" data-src="https://freight.cargo.site/t/original/i/f3396ffb37f8ab30e729d59a1c4139f9fde62d72a1006612956668c40b1aa191/Spacing-Chart-Desktop.png" data-mid="253070985" border="0"  src="https://freight.cargo.site/w/1000/i/f3396ffb37f8ab30e729d59a1c4139f9fde62d72a1006612956668c40b1aa191/Spacing-Chart-Desktop.png" /&#62;
	&#60;img width="2020" height="1738" width_o="2020" height_o="1738" data-src="https://freight.cargo.site/t/original/i/40d9cc718bd46205c2e38af1ebda166ef39ec0322e6cd050fa695bb4f1797927/Spacing-Chart-Mobile.png" data-mid="253070986" border="0"  src="https://freight.cargo.site/w/1000/i/40d9cc718bd46205c2e38af1ebda166ef39ec0322e6cd050fa695bb4f1797927/Spacing-Chart-Mobile.png" /&#62;


	︎︎︎ Spaing charts for desktop and mobile devices



	
&#60;img width="3405" height="970" width_o="3405" height_o="970" data-src="https://freight.cargo.site/t/original/i/4e2271a56074477b4d5fe1e1143d52eae6eaeec65ef60d78c739f23fbe854731/Type-Settings.png" data-mid="253070980" border="0"  src="https://freight.cargo.site/w/1000/i/4e2271a56074477b4d5fe1e1143d52eae6eaeec65ef60d78c739f23fbe854731/Type-Settings.png" /&#62;
︎︎︎ Type setting examples


&#38;nbsp; &#38;nbsp; 
	









	BUTTONSThere were different sizes of the same CTA buttons existing. We’ve reduced them into two sizes, and combined different tab menus into one style. 
&#60;img width="2846" height="2646" width_o="2846" height_o="2646" data-src="https://freight.cargo.site/t/original/i/f0fbea51460e10df785ee3941ad08895406b42e9598d255534eeb814a6c516bf/Buttons.png" data-mid="253070981" border="0"  src="https://freight.cargo.site/w/1000/i/f0fbea51460e10df785ee3941ad08895406b42e9598d255534eeb814a6c516bf/Buttons.png" /&#62;︎︎︎ Button styles








	
	


	



	
	COLORS AND SPACING

First of all, there were too many different grays. We’ve reduced the number of grays to six according to their usages. For spacing, we’ve set up the basic increment for spacing as 10px, and defined spaces between elements and sections.
	


	&#60;img width="2800" height="3420" width_o="2800" height_o="3420" data-src="https://freight.cargo.site/t/original/i/78beec4de9733fb22bf5d27f264e753a8b24a77191d5a5ab4b84b986dde08f7d/Spacing-Desktop.png" data-mid="253070983" border="0"  src="https://freight.cargo.site/w/1000/i/78beec4de9733fb22bf5d27f264e753a8b24a77191d5a5ab4b84b986dde08f7d/Spacing-Desktop.png" /&#62;︎︎︎ Spacing settings


	
&#60;img width="2803" height="2342" width_o="2803" height_o="2342" data-src="https://freight.cargo.site/t/original/i/a98141d63418b56678af8fe9668fe1cb17e91fdca025b682f03c12823ff55a80/Cards.png" data-mid="253070987" border="0"  src="https://freight.cargo.site/w/1000/i/a98141d63418b56678af8fe9668fe1cb17e91fdca025b682f03c12823ff55a80/Cards.png" /&#62;︎︎︎ Card styles for desktop and mobile devices






	&#60;img width="3428" height="882" width_o="3428" height_o="882" data-src="https://freight.cargo.site/t/original/i/09ae9b064da3ca8af10a03aabf1aada4a98332c7fb522133397885f50bf3eaad/Icons.png" data-mid="253070988" border="0"  src="https://freight.cargo.site/w/1000/i/09ae9b064da3ca8af10a03aabf1aada4a98332c7fb522133397885f50bf3eaad/Icons.png" /&#62;︎︎︎ Icons



	
















	Conclusion
We’ve created the UI asset library and style guide web pages, and provided them to designers and developers as the final step.
	


	&#60;img width="3840" height="2160" width_o="3840" height_o="2160" data-src="https://freight.cargo.site/t/original/i/83500ea80d9b0356f24b8c9247c021b19f976b9e86af47ee5afc8052adef2735/style-guide-page-2.jpg" data-mid="253070992" border="0"  src="https://freight.cargo.site/w/1000/i/83500ea80d9b0356f24b8c9247c021b19f976b9e86af47ee5afc8052adef2735/style-guide-page-2.jpg" /&#62;
︎︎︎ Datadog Corpsite Style Guide



	
	Now, the most of the webpages are following the guides and rules, and it has got much easier and faster for designers and developers to create new pages and managing them as there are certain guides they can follow.
	




	← Previous project
	
	
	All work
	
	
	
	Next project →
Related work</description>
		
	</item>
		
		
	<item>
		<title>Airem Identity Design</title>
				
		<link>https://eunmokang.com/Airem-Identity-Design</link>

		<pubDate>Fri, 09 Oct 2026 03:47:25 +0000</pubDate>

		<dc:creator>Eunmo Kang</dc:creator>

		<guid isPermaLink="true">https://eunmokang.com/Airem-Identity-Design</guid>

		<description>
	Airem Identity Design
Client: AiremDesign: Eunmo Kang


	
Airem is a modern medical aesthetics practice that offers curated non-surgical and surgical treatments in an urban sanctuary setting inspired by traditional eastern and Korean beauty principles.&#38;nbsp;

Inspired by traditional Korean architecture, I designed its visual identity including a logo, color palette, and applications.



	&#60;img width="3840" height="2160" width_o="3840" height_o="2160" data-src="https://freight.cargo.site/t/original/i/cc630b012908512ac94ede723db7629d39c6a6bf25ce17b96d343c5365c9d53d/airem_identity_portfolio1.jpg" data-mid="253071002" border="0"  src="https://freight.cargo.site/w/1000/i/cc630b012908512ac94ede723db7629d39c6a6bf25ce17b96d343c5365c9d53d/airem_identity_portfolio1.jpg" /&#62;
&#60;img width="3840" height="2160" width_o="3840" height_o="2160" data-src="https://freight.cargo.site/t/original/i/5753319b2b1ae2da7cf0d121f38813748c55275cc279fa4c3ecf6b1ab88c8fa3/airem_identity_portfolio2.jpg" data-mid="253071000" border="0"  src="https://freight.cargo.site/w/1000/i/5753319b2b1ae2da7cf0d121f38813748c55275cc279fa4c3ecf6b1ab88c8fa3/airem_identity_portfolio2.jpg" /&#62;
&#60;img width="3840" height="2160" width_o="3840" height_o="2160" data-src="https://freight.cargo.site/t/original/i/a15dd2b00407275caf1ed35c7f9e12641ff03c143df1ac7872d15e73d8345382/airem_identity_portfolio3.jpg" data-mid="253071001" border="0"  src="https://freight.cargo.site/w/1000/i/a15dd2b00407275caf1ed35c7f9e12641ff03c143df1ac7872d15e73d8345382/airem_identity_portfolio3.jpg" /&#62;


Inspirations
&#60;img width="3840" height="2160" width_o="3840" height_o="2160" data-src="https://freight.cargo.site/t/original/i/a65b73ca96a68acfcc9a33d6f2ec778adbd64b7f8d448a9df73518dbbd669b96/airem_identity_portfolio5.jpg" data-mid="253070997" border="0"  src="https://freight.cargo.site/w/1000/i/a65b73ca96a68acfcc9a33d6f2ec778adbd64b7f8d448a9df73518dbbd669b96/airem_identity_portfolio5.jpg" /&#62;&#60;img width="3840" height="2160" width_o="3840" height_o="2160" data-src="https://freight.cargo.site/t/original/i/ae3778610e49792bb4174be74d5a2cd024938173178b5aeb6bf360e50e5fd323/airem_identity_portfolio4.jpg" data-mid="253070993" border="0"  src="https://freight.cargo.site/w/1000/i/ae3778610e49792bb4174be74d5a2cd024938173178b5aeb6bf360e50e5fd323/airem_identity_portfolio4.jpg" /&#62;&#60;img width="3840" height="2160" width_o="3840" height_o="2160" data-src="https://freight.cargo.site/t/original/i/1fa4b4cf19b1feaa8d54a20140100b71fb51ada894f8bddc6e090923330d34be/airem_identity_portfolio8.jpg" data-mid="253071004" border="0"  src="https://freight.cargo.site/w/1000/i/1fa4b4cf19b1feaa8d54a20140100b71fb51ada894f8bddc6e090923330d34be/airem_identity_portfolio8.jpg" /&#62;&#60;img width="3840" height="2160" width_o="3840" height_o="2160" data-src="https://freight.cargo.site/t/original/i/41ddca3f7d5d6958e9f4d20e5eeea666aed8524f48ace4d7dd53a0e8c0d16b55/airem_identity_portfolio6.jpg" data-mid="253070998" border="0"  src="https://freight.cargo.site/w/1000/i/41ddca3f7d5d6958e9f4d20e5eeea666aed8524f48ace4d7dd53a0e8c0d16b55/airem_identity_portfolio6.jpg" /&#62;
&#60;img width="3840" height="2160" width_o="3840" height_o="2160" data-src="https://freight.cargo.site/t/original/i/304a40f76d7781a782552a2c9ef65e64080dbc892b7b6e52def62937258ce473/airem_identity_portfolio9.jpg" data-mid="253070994" border="0"  src="https://freight.cargo.site/w/1000/i/304a40f76d7781a782552a2c9ef65e64080dbc892b7b6e52def62937258ce473/airem_identity_portfolio9.jpg" /&#62;&#60;img width="3840" height="2160" width_o="3840" height_o="2160" data-src="https://freight.cargo.site/t/original/i/258a2e65e1344423df3685f423a7415f71de9da283e78068e3813208f0468aac/airem_identity_portfolio11.jpg" data-mid="253070996" border="0"  src="https://freight.cargo.site/w/1000/i/258a2e65e1344423df3685f423a7415f71de9da283e78068e3813208f0468aac/airem_identity_portfolio11.jpg" /&#62;&#60;img width="3840" height="2160" width_o="3840" height_o="2160" data-src="https://freight.cargo.site/t/original/i/95b61967e255aa73782cc38e17368a0862300c9b8f3633d2b1385bc4207b450b/airem_identity_portfolio10.jpg" data-mid="253070995" border="0"  src="https://freight.cargo.site/w/1000/i/95b61967e255aa73782cc38e17368a0862300c9b8f3633d2b1385bc4207b450b/airem_identity_portfolio10.jpg" /&#62;





	← Previous project
	
	
	All work
	
	
	
	Next project →
Related work</description>
		
	</item>
		
		
	<item>
		<title>Dash 2018 Conference</title>
				
		<link>https://eunmokang.com/Dash-2018-Conference</link>

		<pubDate>Fri, 09 Oct 2026 03:47:27 +0000</pubDate>

		<dc:creator>Eunmo Kang</dc:creator>

		<guid isPermaLink="true">https://eunmokang.com/Dash-2018-Conference</guid>

		<description>Dash 2018 Conference

Direct: Eunmo Kang, Ynon LanDesign: Eunmo Kang, Michael HoangAnimation: Lupita Djody, Michael HoangMusic: Won ChoiWeb Coding: Won Choi

Dash is Datadog’s two-day conference for developers and operations professionals, held in New York City. The event brought engineers together for talks, hands-on labs, and training sessions focused on three themes: Performance, Scalability, and Teams. A hexagon, pyramid, and sphere represented the three themes.


&#60;img width="2600" height="1400" width_o="2600" height_o="1400" data-src="https://freight.cargo.site/t/original/i/77b6700cf3947a42ce474fad5e912bf90e96d62edb438d0d0df06759d62e3517/dash2018-01-animated_logo.gif" data-mid="253071011" border="0"  src="https://freight.cargo.site/w/1000/i/77b6700cf3947a42ce474fad5e912bf90e96d62edb438d0d0df06759d62e3517/dash2018-01-animated_logo.gif" /&#62;

&#60;img width="3000" height="1800" width_o="3000" height_o="1800" data-src="https://freight.cargo.site/t/original/i/c523b880ba6a78ddc97fb655a4273138a98cc12c3faaf416e2282e85e8fd4be5/dash2018-03-typograhy.jpg" data-mid="253071024" border="0"  src="https://freight.cargo.site/w/1000/i/c523b880ba6a78ddc97fb655a4273138a98cc12c3faaf416e2282e85e8fd4be5/dash2018-03-typograhy.jpg" /&#62;
&#60;img width="3000" height="1800" width_o="3000" height_o="1800" data-src="https://freight.cargo.site/t/original/i/d20485d29a958e9fba3ad808057d123ab9def21398d5237f7af32d0408b354a2/dash2018-04-photo.jpg" data-mid="253071012" border="0"  src="https://freight.cargo.site/w/1000/i/d20485d29a958e9fba3ad808057d123ab9def21398d5237f7af32d0408b354a2/dash2018-04-photo.jpg" /&#62;
&#60;img width="3000" height="1800" width_o="3000" height_o="1800" data-src="https://freight.cargo.site/t/original/i/b689171c6456e0ee87d523fcf36b9348681a2548cc41555fe495ea46598eabdc/dash2018-05-posters.jpg" data-mid="253071025" border="0"  src="https://freight.cargo.site/w/1000/i/b689171c6456e0ee87d523fcf36b9348681a2548cc41555fe495ea46598eabdc/dash2018-05-posters.jpg" /&#62;
&#60;img width="3000" height="1800" width_o="3000" height_o="1800" data-src="https://freight.cargo.site/t/original/i/3ac738a58d5d46851a49d53d049ee02113b3f9aac475e9199009162bc2737907/dash2018-06-photo.jpg" data-mid="253071013" border="0"  src="https://freight.cargo.site/w/1000/i/3ac738a58d5d46851a49d53d049ee02113b3f9aac475e9199009162bc2737907/dash2018-06-photo.jpg" /&#62;
&#60;img width="3000" height="1800" width_o="3000" height_o="1800" data-src="https://freight.cargo.site/t/original/i/2fed0b5a1447501413e3b6968a739e5d71092265fde01b2e39ab44af8904eb06/dash2018-07-photo.jpg" data-mid="253071014" border="0"  src="https://freight.cargo.site/w/1000/i/2fed0b5a1447501413e3b6968a739e5d71092265fde01b2e39ab44af8904eb06/dash2018-07-photo.jpg" /&#62;

&#60;img width="3000" height="1800" width_o="3000" height_o="1800" data-src="https://freight.cargo.site/t/original/i/b5fdb2e69099a23bd32deb02fb5422183bbe09e79cdeba7195e4db1b6e66a204/dash2018-09-brochure.jpg" data-mid="253071015" border="0"  src="https://freight.cargo.site/w/1000/i/b5fdb2e69099a23bd32deb02fb5422183bbe09e79cdeba7195e4db1b6e66a204/dash2018-09-brochure.jpg" /&#62;

&#60;img width="1486" height="1800" width_o="1486" height_o="1800" data-src="https://freight.cargo.site/t/original/i/e819359aecb6b94702a00a4888a0a7fe61ad2838837aa2dbfba12d3342840067/dash2018-10-1-signage.jpg" data-mid="253071016" border="0"  src="https://freight.cargo.site/w/1000/i/e819359aecb6b94702a00a4888a0a7fe61ad2838837aa2dbfba12d3342840067/dash2018-10-1-signage.jpg" /&#62;
&#60;img width="1486" height="1800" width_o="1486" height_o="1800" data-src="https://freight.cargo.site/t/original/i/01cc3462ae4516b2137abd6817e6fa849823915582ba1498ccdeed367183a68d/dash2018-10-2-signage.jpg" data-mid="253071017" border="0"  src="https://freight.cargo.site/w/1000/i/01cc3462ae4516b2137abd6817e6fa849823915582ba1498ccdeed367183a68d/dash2018-10-2-signage.jpg" /&#62;

&#60;img width="3000" height="1800" width_o="3000" height_o="1800" data-src="https://freight.cargo.site/t/original/i/af13c59dbd388691aa3b01fdfbbfe26cdf9451b2f8d66f499252792447b757dc/dash2018-11-signage.jpg" data-mid="253071018" border="0"  src="https://freight.cargo.site/w/1000/i/af13c59dbd388691aa3b01fdfbbfe26cdf9451b2f8d66f499252792447b757dc/dash2018-11-signage.jpg" /&#62;
&#60;img width="3000" height="1800" width_o="3000" height_o="1800" data-src="https://freight.cargo.site/t/original/i/0d6b1f6cedae7169887b2683fef852b5f8a918ba93bd8c06d9aeb53ee7626acf/dash2018-12-keynote.jpg" data-mid="253071019" border="0"  src="https://freight.cargo.site/w/1000/i/0d6b1f6cedae7169887b2683fef852b5f8a918ba93bd8c06d9aeb53ee7626acf/dash2018-12-keynote.jpg" /&#62;

&#60;img width="3000" height="1800" width_o="3000" height_o="1800" data-src="https://freight.cargo.site/t/original/i/020737485813a95dfe63bb78852cd03b4e26c65f867db55d469b1cf947288f5e/dash2018-14-namebadges.jpg" data-mid="253071026" border="0"  src="https://freight.cargo.site/w/1000/i/020737485813a95dfe63bb78852cd03b4e26c65f867db55d469b1cf947288f5e/dash2018-14-namebadges.jpg" /&#62;
&#60;img width="3000" height="1800" width_o="3000" height_o="1800" data-src="https://freight.cargo.site/t/original/i/fcb4c7148bf283e1067be7aba7ccf74886ca73ddf7c6b495dc075038343b78b9/dash2018-15-totebags.jpg" data-mid="253071020" border="0"  src="https://freight.cargo.site/w/1000/i/fcb4c7148bf283e1067be7aba7ccf74886ca73ddf7c6b495dc075038343b78b9/dash2018-15-totebags.jpg" /&#62;
&#60;img width="2600" height="1400" width_o="2600" height_o="1400" data-src="https://freight.cargo.site/t/original/i/780eb2de3480a30e9feec8b68a51c7fa888f18aa5a8e8b68f4592359f011a64d/dash2018-16-homepage.gif" data-mid="253071021" border="0"  src="https://freight.cargo.site/w/1000/i/780eb2de3480a30e9feec8b68a51c7fa888f18aa5a8e8b68f4592359f011a64d/dash2018-16-homepage.gif" /&#62;

&#60;img width="3000" height="1800" width_o="3000" height_o="1800" data-src="https://freight.cargo.site/t/original/i/467eb2038e705bdb1dadab05be8b4b478f2900e1503ab74130a6527620386138/dash2018-18-photo.jpg" data-mid="253071022" border="0"  src="https://freight.cargo.site/w/1000/i/467eb2038e705bdb1dadab05be8b4b478f2900e1503ab74130a6527620386138/dash2018-18-photo.jpg" /&#62;
&#60;img width="2600" height="1400" width_o="2600" height_o="1400" data-src="https://freight.cargo.site/t/original/i/325c5706f9d9826b31a92640a6ffcee4f4df55f45251a45002cf75a6e855166a/dash2018-19-photo.jpg" data-mid="253071023" border="0"  src="https://freight.cargo.site/w/1000/i/325c5706f9d9826b31a92640a6ffcee4f4df55f45251a45002cf75a6e855166a/dash2018-19-photo.jpg" /&#62;




	← Previous project
	
	
	All work
	
	
	
	Next project →
Related work</description>
		
	</item>
		
		
	<item>
		<title>The 5th Contently Summit</title>
				
		<link>https://eunmokang.com/The-5th-Contently-Summit</link>

		<pubDate>Fri, 09 Oct 2026 03:47:29 +0000</pubDate>

		<dc:creator>Eunmo Kang</dc:creator>

		<guid isPermaLink="true">https://eunmokang.com/The-5th-Contently-Summit</guid>

		<description>
	Contently Summit Fall 2016
Client: ContentlyPhotograph: Bill McCulloughCreative Director: Kathryn HanLead Designer: Eunmo Kang


	
Contenty had their 5th fall summit in 2016 and the theme was cinema. I have developted visual identity with the idea of screens. The collage of screens works as a pattern solely and also intervene in typography as well.



&#60;img width="2500" height="1667" width_o="2500" height_o="1667" data-src="https://freight.cargo.site/t/original/i/1fcae4f959f419f8d7bc8c8bc9d462d75923820872902e7051f874853f44523b/161013-1309-01.jpg" data-mid="253071039" border="0"  src="https://freight.cargo.site/w/1000/i/1fcae4f959f419f8d7bc8c8bc9d462d75923820872902e7051f874853f44523b/161013-1309-01.jpg" /&#62;
&#60;img width="1667" height="2500" width_o="1667" height_o="2500" data-src="https://freight.cargo.site/t/original/i/820cacefabb4c5310eb49e977f97b44bda25785be92485e8a8688c72c19f8479/161013-1140-41.jpg" data-mid="253071028" border="0"  src="https://freight.cargo.site/w/1000/i/820cacefabb4c5310eb49e977f97b44bda25785be92485e8a8688c72c19f8479/161013-1140-41.jpg" /&#62;
&#60;img width="1667" height="2500" width_o="1667" height_o="2500" data-src="https://freight.cargo.site/t/original/i/44e2e657560ca41dfa25687712ac0e44bacccf79fd422bf02eca6a3e591b7213/161013-1135-37.jpg" data-mid="253071027" border="0"  src="https://freight.cargo.site/w/1000/i/44e2e657560ca41dfa25687712ac0e44bacccf79fd422bf02eca6a3e591b7213/161013-1135-37.jpg" /&#62;
&#60;img width="1667" height="2500" width_o="1667" height_o="2500" data-src="https://freight.cargo.site/t/original/i/c63f3e393dbe501e56f1e4a9c039c4207a8e46eadaf34e2e22b178d1f2b8be2a/161013-1143-18.jpg" data-mid="253071029" border="0"  src="https://freight.cargo.site/w/1000/i/c63f3e393dbe501e56f1e4a9c039c4207a8e46eadaf34e2e22b178d1f2b8be2a/161013-1143-18.jpg" /&#62;
&#60;img width="2500" height="1667" width_o="2500" height_o="1667" data-src="https://freight.cargo.site/t/original/i/180e424821605648995cadf9737e31f774402c3dcd648a869a81f88a68b7373d/161013-1247-26.jpg" data-mid="253071030" border="0"  src="https://freight.cargo.site/w/1000/i/180e424821605648995cadf9737e31f774402c3dcd648a869a81f88a68b7373d/161013-1247-26.jpg" /&#62;
&#60;img width="2448" height="3264" width_o="2448" height_o="3264" data-src="https://freight.cargo.site/t/original/i/e9f0505c6a687e1af3f7b4c4585a8c8dbb5b403d7690f31acda3a514870d25c9/IMG_5533.JPG" data-mid="253071033" border="0"  src="https://freight.cargo.site/w/1000/i/e9f0505c6a687e1af3f7b4c4585a8c8dbb5b403d7690f31acda3a514870d25c9/IMG_5533.JPG" /&#62;
&#60;img width="1667" height="2500" width_o="1667" height_o="2500" data-src="https://freight.cargo.site/t/original/i/85ab2ecbe2d62cfa5d3c40ca8e0f93d895249b6cb46e043e8dd9bf39018ea6b4/161013-1229-40.jpg" data-mid="253071043" border="0"  src="https://freight.cargo.site/w/1000/i/85ab2ecbe2d62cfa5d3c40ca8e0f93d895249b6cb46e043e8dd9bf39018ea6b4/161013-1229-40.jpg" /&#62;
&#60;img width="4000" height="2667" width_o="4000" height_o="2667" data-src="https://freight.cargo.site/t/original/i/dcbb7f3992d146f3b64f4c58813dfe9412a31b694a3d64f3afcf6e0d5bf5dd28/NYSummit2016_brochure_01.jpg" data-mid="253071032" border="0"  src="https://freight.cargo.site/w/1000/i/dcbb7f3992d146f3b64f4c58813dfe9412a31b694a3d64f3afcf6e0d5bf5dd28/NYSummit2016_brochure_01.jpg" /&#62;
&#60;img width="4000" height="2667" width_o="4000" height_o="2667" data-src="https://freight.cargo.site/t/original/i/5849ab05a55f573efde894e39302ed0054a85a7a954f23e1e783717d0338919f/NYSummit2016_brochure_02.jpg" data-mid="253071034" border="0"  src="https://freight.cargo.site/w/1000/i/5849ab05a55f573efde894e39302ed0054a85a7a954f23e1e783717d0338919f/NYSummit2016_brochure_02.jpg" /&#62;
&#60;img width="4000" height="2667" width_o="4000" height_o="2667" data-src="https://freight.cargo.site/t/original/i/837005daaca967848a9cba39823714de53a355f05613db9e33f15ac4405fe63e/NYSummit2016_brochure_03.jpg" data-mid="253071035" border="0"  src="https://freight.cargo.site/w/1000/i/837005daaca967848a9cba39823714de53a355f05613db9e33f15ac4405fe63e/NYSummit2016_brochure_03.jpg" /&#62;
&#60;img width="4000" height="2667" width_o="4000" height_o="2667" data-src="https://freight.cargo.site/t/original/i/6052d2bd419073e2e1e06ec0f3f68096ae8db928a8fbc28f888335c4d43a9a01/NYSummit2016_brochure_04.jpg" data-mid="253071036" border="0"  src="https://freight.cargo.site/w/1000/i/6052d2bd419073e2e1e06ec0f3f68096ae8db928a8fbc28f888335c4d43a9a01/NYSummit2016_brochure_04.jpg" /&#62;
&#60;img width="4000" height="2667" width_o="4000" height_o="2667" data-src="https://freight.cargo.site/t/original/i/4afc45e1ea65cca4d12261d9ea7e558f74812317476b20ce3dbaaa1c9686f280/NYSummit2016_brochure_05.jpg" data-mid="253071037" border="0"  src="https://freight.cargo.site/w/1000/i/4afc45e1ea65cca4d12261d9ea7e558f74812317476b20ce3dbaaa1c9686f280/NYSummit2016_brochure_05.jpg" /&#62;
&#60;img width="4000" height="2667" width_o="4000" height_o="2667" data-src="https://freight.cargo.site/t/original/i/499b3c13cc2eeaa5e110d419156a67f2fd117003ff97c10d97c8ba8b495a7628/NYSummit2016_brochure_06.jpg" data-mid="253071038" border="0"  src="https://freight.cargo.site/w/1000/i/499b3c13cc2eeaa5e110d419156a67f2fd117003ff97c10d97c8ba8b495a7628/NYSummit2016_brochure_06.jpg" /&#62;
&#60;img width="4000" height="2667" width_o="4000" height_o="2667" data-src="https://freight.cargo.site/t/original/i/787be345d56875f57bd5a0540f1b0ed9df34ac102b9157425a83370d5a00e8e4/NYSummit2016_brochure_07.jpg" data-mid="253071040" border="0"  src="https://freight.cargo.site/w/1000/i/787be345d56875f57bd5a0540f1b0ed9df34ac102b9157425a83370d5a00e8e4/NYSummit2016_brochure_07.jpg" /&#62;
&#60;img width="4000" height="2667" width_o="4000" height_o="2667" data-src="https://freight.cargo.site/t/original/i/d1f0161d2abaeedaa53407daf6bb25435b2087f7ac2b013d3ec77ee70c363fb5/NYSummit2016_brochure_08.jpg" data-mid="253071041" border="0"  src="https://freight.cargo.site/w/1000/i/d1f0161d2abaeedaa53407daf6bb25435b2087f7ac2b013d3ec77ee70c363fb5/NYSummit2016_brochure_08.jpg" /&#62;
&#60;img width="2500" height="1667" width_o="2500" height_o="1667" data-src="https://freight.cargo.site/t/original/i/3727a4e57302adc86866bd68eca7af16a38fe8dd0ed4b3e5a38f1ce04283fe8f/161013-1536-43.jpg" data-mid="253071031" border="0"  src="https://freight.cargo.site/w/1000/i/3727a4e57302adc86866bd68eca7af16a38fe8dd0ed4b3e5a38f1ce04283fe8f/161013-1536-43.jpg" /&#62;




	← Previous project
	
	
	All work
	
	
	
	Next project →
Related work</description>
		
	</item>
		
		
	<item>
		<title>The Content Strategist Website</title>
				
		<link>https://eunmokang.com/The-Content-Strategist-Website</link>

		<pubDate>Fri, 09 Oct 2026 03:47:33 +0000</pubDate>

		<dc:creator>Eunmo Kang</dc:creator>

		<guid isPermaLink="true">https://eunmokang.com/The-Content-Strategist-Website</guid>

		<description>
	The Content Strategist page renewal
	
Creative Director: KathrynHanProgrammer: Ned Klezmer


	

	The Content Strategist is the publication for content marketing news and analysis from Contently. My role was to redesign the template for the landing page and the article pages.contently.com/strategist


&#60;img width="2000" height="1160" width_o="2000" height_o="1160" data-src="https://freight.cargo.site/t/original/i/74be59ddfeccd62de9bba961dd4eab72c46ead4727b15a2766900f1dda2fee89/contently_TCS-home.jpg" data-mid="253071079" border="0"  src="https://freight.cargo.site/w/1000/i/74be59ddfeccd62de9bba961dd4eab72c46ead4727b15a2766900f1dda2fee89/contently_TCS-home.jpg" /&#62;
&#60;img width="2000" height="3437" width_o="2000" height_o="3437" data-src="https://freight.cargo.site/t/original/i/d6780c584f423715669570152d9beb7a7bbe7f792b06c76a4be8b9440d17bb29/contently_TCS-article.jpg" data-mid="253071081" border="0"  src="https://freight.cargo.site/w/1000/i/d6780c584f423715669570152d9beb7a7bbe7f792b06c76a4be8b9440d17bb29/contently_TCS-article.jpg" /&#62;
&#60;img width="2000" height="1160" width_o="2000" height_o="1160" data-src="https://freight.cargo.site/t/original/i/2028a0d58361d7e6c275ff2d927e9298924e0e036fd616c6bd0f224cdf2f4232/contently_TCS-mobile.jpg" data-mid="253071083" border="0"  src="https://freight.cargo.site/w/1000/i/2028a0d58361d7e6c275ff2d927e9298924e0e036fd616c6bd0f224cdf2f4232/contently_TCS-mobile.jpg" /&#62;




	← Previous project
	
	
	All work
	
	
	
	Next project →
Related work</description>
		
	</item>
		
	</channel>
</rss>