[{"data":1,"prerenderedAt":1271},["ShallowReactive",2],{"work":3},[4,188,363,465,630,829,946,1057],{"id":5,"title":6,"body":7,"company":170,"date":171,"description":172,"draft":173,"extension":174,"featured":175,"industry":176,"meta":177,"navigation":175,"order":178,"path":179,"role":180,"seo":181,"skills":182,"stem":186,"thumbnail":120,"__hash__":187},"work\u002Fwork\u002Fvenafi-cybersecurity.md","CyberSecurity — How 'Who' Edged the Feature",{"type":8,"value":9,"toc":162},"minimark",[10,15,23,31,34,38,41,44,48,51,54,57,60,64,87,92,95,98,108,115,124,127,130,138,142,145,159],[11,12,14],"h2",{"id":13},"cybersecurityhow-who-edged-thefeature","CyberSecurity — How “Who” Edged the Feature",[16,17,18],"p",{},[19,20],"img",{"alt":21,"src":22},"","\u002Fimages\u002Fwork\u002Fvenafi-cybersecurity\u002F01.png",[16,24,25,26,30],{},"At the start of most design projects, defining ",[27,28,29],"strong",{},"who"," the user is seems obvious — but you’d be surprised.",[16,32,33],{},"In 2020, I joined Venafi to design the CodeSigning Protect product, with the excitement to design for another industry. While it had already launched to five customers and demonstrated market fit, there were gaps to address. One of those was the “Auditing Feature” — a documented requirement waiting to be designed.",[11,35,37],{"id":36},"the-beginning","The Beginning",[16,39,40],{},"I studied the document, had a few briefs with the PM and the Product\u002FTech Lead (a founding member who jokingly called himself the “product janitor”).",[16,42,43],{},"The ask was clear: enable auditors to discover the root cause of incidents — such as detecting if a signing key had been abused to sign malware. At the high level, we will need to provide contextual entry points and enable an efficient analytical flow when there is an outside trigger.",[11,45,47],{"id":46},"dug-in-and-zoomedout","Dug In and Zoomed Out",[16,49,50],{},"I kicked off research during our (virtual) annual conference in 2020 — thanks to COVID, it was remote, but perfect for connecting (plus, screen-sharing and recording). I hopped into relevant “room chat” discussions and invited attendees to become early influencers for the newest product offering. That approach led to five enterprise customers, agreeing to interview. Our CodeSign customers were big enterprise companies and consultancy with high security needs, so I was very happy with the number of customers I was able to recruit.",[16,52,53],{},"The method was “Expert Interviews,” leading with open questions to understand their current practices, contexts, and motivations. Triggered by our conversations, we ended up zooming out beyond the feature.",[16,55,56],{},"Surprisingly, none had a defined code-signing audit process — even though they were pioneers in the space. In fact, their code-signing maturity was closer to infancy. I probed deeper into comparable auditing workflows in other cybersecurity practices, repeatedly asking “why” to uncover valuable insights.",[16,58,59],{},"Here’s the crux: Auditors — whether internal or external — are rarely using the product directly. Their reviews happen only annually, quarterly, or at best monthly. Instead of using the UI, they either sit with an administrator to navigate the system or simply request exported data.",[11,61,63],{"id":62},"edge-inagain","Edge In Again",[16,65,66,67,70,71,74,75,78,79,82,83,86],{},"Clearly, auditing and incident diagnosis matter. But could we get more ROI by shifting the design focus? I proposed expanding the workflow to emphasize ",[27,68,69],{},"prevention",", not just ",[27,72,73],{},"diagnosis",". The full flow would include diagnostic tools, but ",[27,76,77],{},"daily health checks"," became the ",[27,80,81],{},"priority"," — same data, but now oriented toward **admins ",[27,84,85],{},"(the active product user)"," **for proactive use, rather than auditors (reactive use).",[16,88,89],{},[19,90],{"alt":21,"src":91},"\u002Fimages\u002Fwork\u002Fvenafi-cybersecurity\u002F02.png",[16,93,94],{},"Beyond the key findings, other insights — derived from the answers to the “whys” (why he\u002Fshe pay special attentions and took certain actions to keep their systems healthy) — helped position the feature as truly value-driven.",[16,96,97],{},"I advanced from low-fidelity to mid-fidelity mockups for both preventive and diagnostic scenarios. We honed in on a dashboard that offers admins:",[99,100,101,105],"ul",{},[102,103,104],"li",{},"A real-time operational health summary",[102,106,107],{},"One-click access to diagnostic workflows",[16,109,110,111,114],{},"Not surprisingly, engineering proceeded with the ",[27,112,113],{},"preventative dashboard first",", delivering value to customers earlier — accelerating impact through preventative care.",[16,116,117,121],{},[19,118],{"alt":119,"src":120},"Homepage\u002FDashboard (not latest version)","\u002Fimages\u002Fwork\u002Fvenafi-cybersecurity\u002F03.png",[122,123,119],"em",{},[16,125,126],{},"The new homepage, which provides admins both a quick “health” summary based on real-time operational data and also quick entry point into any diagnostic workflow.",[16,128,129],{},"Through either a wizard to navigate the ambiguity or jump right in when the indicator is clear, you will be able to investigate each signing activity under a microscope here:",[16,131,132,136],{},[19,133],{"alt":134,"src":135},"Signing Activity, under MicroScope","\u002Fimages\u002Fwork\u002Fvenafi-cybersecurity\u002F04.png",[122,137,134],{},[11,139,141],{"id":140},"reflection-finalthoughts","Reflection \u002F Final Thoughts",[16,143,144],{},"If we had focused the design exclusively on auditors, the final experience might have been far less efficient for admins — the true daily users.",[16,146,147,148,151,152,155,156,158],{},"Of all the design questions — Who, What, How, Why — ",[27,149,150],{},"“Who”"," is the one we ",[27,153,154],{},"least often"," challenge. But as this case shows, re-examining ",[27,157,29],{}," the primary user is can completely shift your direction.",[16,160,161],{},"The health-check dashboard was very well received — not just in immediate user testing but also through positive feedback months later from customer-facing teams.",{"title":21,"searchDepth":163,"depth":163,"links":164},2,[165,166,167,168,169],{"id":13,"depth":163,"text":14},{"id":36,"depth":163,"text":37},{"id":46,"depth":163,"text":47},{"id":62,"depth":163,"text":63},{"id":140,"depth":163,"text":141},"Venafi","2025-08-20","Pivoted an auditing feature into a real-time admin health dashboard by reframing who the actual user was.",false,"md",true,"Cybersecurity",{},1,"\u002Fwork\u002Fvenafi-cybersecurity","Senior Product Designer",{"title":6,"description":172},[183,184,185],"Product Strategy","User Research","UX Design","work\u002Fvenafi-cybersecurity","2n0uyc38j8T0yoe_DYcYdm4MyeLmWg4m5Mb8H3BRURQ",{"id":189,"title":190,"body":191,"company":352,"date":353,"description":354,"draft":173,"extension":174,"featured":175,"industry":355,"meta":356,"navigation":175,"order":163,"path":357,"role":180,"seo":358,"skills":359,"stem":361,"thumbnail":344,"__hash__":362},"work\u002Fwork\u002Ften-x-buyer-profile.md","Design a bridge to trust and action",{"type":8,"value":192,"toc":345},[193,197,200,203,211,215,218,221,226,229,237,241,244,252,255,259,262,265,271,285,291,299,304,308,311,332,340],[11,194,196],{"id":195},"design-a-bridge-to-trust-andaction","Design a bridge to trust and action",[16,198,199],{},"The world of Commercial Real Estate (CRE) transactions is a high-stakes game, with multi-million dollar deals hinging on a delicate balance of trust, expertise, and negotiation. Traditionally, these transactions have been conducted locally, where parties can rely on personal relationships and local insights to navigate the market.",[16,201,202],{},"However, an increasing number of CRE transactions are now taking place online, with billions of dollars in assets changing hands through digital platforms. At the forefront of this shift is Ten-X, an online auction platform that has revolutionized the way CRE transactions are conducted. With over 20 billion in assets sold to date (end of 2019), Ten-X has emerged as a major player in the world of online CRE transactions, offering a streamlined and efficient way for buyers and sellers to connect and close deals.",[16,204,205,209],{},[19,206],{"alt":207,"src":208},"Decision Making with Unstructured Information","\u002Fimages\u002Fwork\u002Ften-x-buyer-profile\u002F01.png",[122,210,207],{},[11,212,214],{"id":213},"the-project-background","The Project Background",[16,216,217],{},"Ten-X brought in buyers from all over the world for US properties, opened up the opportunity for both buyer and seller. At the same time, shaking up the solid triangle relationship of buyer, seller and broker. In most cases, seller broker and seller have no pre-existing information about the potential buyers. Among the hundreds of leads brought in by the platform, who should the seller\u002Fbroker move forward with?",[16,219,220],{},"Being the biggest platform for online CRE transaction, we are aware of the gap we need to bridge to get a bigger share of the cake — not to compete with another online platform, but to win the 90% of CRE transaction that still happen in the local comfort zone.",[16,222,223],{},[19,224],{"alt":21,"src":225},"\u002Fimages\u002Fwork\u002Ften-x-buyer-profile\u002F02.png",[16,227,228],{},"In the existing product, buyer information had been organically added into the “leads” table”, as a row expansion, which started out useful and soon grew unusable as the information grows and context changes.",[16,230,231,235],{},[19,232],{"alt":233,"src":234},"Buyer Info Panel before the Project","\u002Fimages\u002Fwork\u002Ften-x-buyer-profile\u002F03.jpeg",[122,236,233],{},[11,238,240],{"id":239},"early-exploration","Early Exploration",[16,242,243],{},"The project started with the direction of solving the usability issue of existing layout, so the early exploration focused more on presenting the information we have available in a more organized way.",[16,245,246,250],{},[19,247],{"alt":248,"src":249},"An Early Exploration","\u002Fimages\u002Fwork\u002Ften-x-buyer-profile\u002F04.png",[122,251,248],{},[16,253,254],{},"After this version was presented, the product team realized it is not the way to bridge the gap. My manager called me in to ask if I want to take a stab at it. Owning the operation side of product at that time, I was very happy to switch gears and do something for seller brokers (I will simply refer them as broker to make it easier).",[11,256,258],{"id":257},"zoom-out-and-zoomin","Zoom out and Zoom in",[16,260,261],{},"After another round of discussion, I agreed with the head of product that the goal is to create a “resume” that fully presents the buyer. As a broker, ‘I’ should have a good grasp of ‘Who this buyer is’ after looking through the resume and should feel comfortable and confident to take an action, ranging from a initial phone call to deal negotiation.",[16,263,264],{},"As we proceed to create Buyer Profile v.2, I have led the effort to discover, define and design to create this “resume” beyond “resume”. We've all had the experience of buying a gift for someone we know. Sometimes, we “Know” he\u002Fshe likes it because we “know” he\u002Fshe. Hopefully our buyer “resume” can create this kind of comfort in broker’s decision making.",[16,266,267,268],{},"A one and half day **workshop **was conducted with a group of ten who had either worked as broker or was in a position that works directly with broker daily. The goal is to ",[27,269,270],{},"meet the broker where he\u002Fshe is.",[16,272,273,274,277,278,281,282],{},"Day 1: we spent the whole day to find out a. “",[27,275,276],{},"where he\u002Fshe could be","” — the phases of a full deal lifecycle; and b. ",[27,279,280],{},"“where the place is like”- the needs\u002Fproblems of each phase",". Nothing specific to buyer info in day 1. Focus was on ",[27,283,284],{},"“where can we meet he\u002Fshe”.",[16,286,287,288],{},"Day 2: we spend large half day on cards sorting the information we have about buyer, specifically, sorting the card for each of the 6 phases we identify during day 1. Focus was on ",[27,289,290],{},"“How should we meet he\u002Fshe with the buyer information at different places\u002Fphases”.",[16,292,293,297],{},[19,294],{"alt":295,"src":296},"workshop","\u002Fimages\u002Fwork\u002Ften-x-buyer-profile\u002F05.png",[122,298,295],{},[16,300,301],{},[19,302],{"alt":21,"src":303},"\u002Fimages\u002Fwork\u002Ften-x-buyer-profile\u002F06.png",[11,305,307],{"id":306},"design","Design",[16,309,310],{},"The discovery set a very solid foundation for us as a product-design team to make quick agreement and move. Here is a few key decisions",[312,313,314,317,320,323,326,329],"ol",{},[102,315,316],{},"Phases to focus on: we quickly identified that we can make the biggest impact on phase 3 (marketing phase) and phase 4 (offer select or live auction).",[102,318,319],{},"Page Layout: it became an easy decision once we know where and how we are going to meet the broker with buyer information. Two examples of the “meets” are conversation start point on mobile to a serious offer negotiation support.",[102,321,322],{},"Lay the information into the structure, with more focus on what content and how the content flow. As the reading flow for each context being defined, the content was also polished (e.g. add local time for friendly calling; use illustration for property unsold and relisted property, etc)",[102,324,325],{},"Details consistency and visual details. (e.g. how to best present bidding habit and profile matching rank.)",[102,327,328],{},"Same time with 4, we consult legal and related department to finalized the availability of information to broker with the consideration of privacy and platform benefit, etc.",[102,330,331],{},"Phase the entire project into a development plan with engineering.",[16,333,334,338],{},[19,335],{"alt":336,"src":337},"Layout","\u002Fimages\u002Fwork\u002Ften-x-buyer-profile\u002F07.png",[122,339,336],{},[16,341,342],{},[19,343],{"alt":21,"src":344},"\u002Fimages\u002Fwork\u002Ften-x-buyer-profile\u002F08.png",{"title":21,"searchDepth":163,"depth":163,"links":346},[347,348,349,350,351],{"id":195,"depth":163,"text":196},{"id":213,"depth":163,"text":214},{"id":239,"depth":163,"text":240},{"id":257,"depth":163,"text":258},{"id":306,"depth":163,"text":307},"Ten-X CRE","2023-06-26","Redesigned buyer profiles for a $20B+ commercial real estate auction platform, building broker confidence across deal phases.","Marketplace Operation",{},"\u002Fwork\u002Ften-x-buyer-profile",{"title":190,"description":354},[360,185,183],"Workshop Facilitation","work\u002Ften-x-buyer-profile","FqmhPCSeASGiY4NM-AUINDy_ZKrc7jIOHCPNUtH1G-4",{"id":364,"title":365,"body":366,"company":450,"date":451,"description":452,"draft":173,"extension":174,"featured":175,"industry":453,"meta":454,"navigation":175,"order":455,"path":456,"role":457,"seo":458,"skills":459,"stem":463,"thumbnail":372,"__hash__":464},"work\u002Fwork\u002Fapttus-design-system.md","Infrastructure components of a Design System — a looking glass view",{"type":8,"value":367,"toc":444},[368,373,377,380,383,387,390,393,396,400,403,411,414,417,420,423,427,430],[16,369,370],{},[19,371],{"alt":21,"src":372},"\u002Fimages\u002Fwork\u002Fapttus-design-system\u002F01.png",[11,374,376],{"id":375},"infrastructure-components-of-a-design-systema-looking-glassview","Infrastructure components of a Design System — a looking glass view",[16,378,379],{},"Design systems have gained attention over years as a way to enable scalable, consistent, and efficient design solutions. It always consists of a set of atom level elements. Infrastructure level? Not always there. To enable highly complex and connected business processes, it is equally or even more important to create infrastructure level of structure at design system level.",[16,381,382],{},"Over the past few years, I’ve been a contributor to or user of four different design systems, at different stage of maturity. Nova Design System, was the one we used and recreated at Apttus (Conga). I was the designer and owner of the infrastructure components for Nova 2.0. (Each product\u002Fvisual designer on our team designed and owned different perspective of the design system.)",[11,384,386],{"id":385},"the-context","The Context",[16,388,389],{},"The existing design system — Nova 1.0 — was no longer enough for the growing needs. This was reflected in the products experience starting to growing apart, among the three 3 product pillars and close to 10 products. Nova 1.0 was also too under-documented to be used consistently. It was a good timing and necessity to rethink about it.",[16,391,392],{},"This article is not going to talk about all the details of how the whole team setup the entire design system, but to spend time talking about the considerations for designing the “infrastructure” components for a specific set of use cases.",[16,394,395],{},"Though the atomic components and visual perspectives are incredible important to any design system, they are relatively easy to borrow. The “whys” of atoms and visuals are based on relatively universal factors such as ergonomics, cognitive ergonomics and visual trend (set branding aside for now). On the other hand, infrastructure components are much harder to borrow, because the “whys” are very hard to understand from the transient layout images.",[11,397,399],{"id":398},"the-use-case-considerations","The Use Case Considerations",[16,401,402],{},"The design process for infrastructure of each design system is likely to be different, depends on how much you know about the potential use cases. Based on the knowledge matrix, we can consider the use cases (existing and potential\u002Fpossible) into four groups, as I charted below.",[16,404,405,409],{},[19,406],{"alt":407,"src":408},"Use Case\u002F Knowledge Matrix","\u002Fimages\u002Fwork\u002Fapttus-design-system\u002F02.png",[122,410,407],{},[16,412,413],{},"A In our case, We have a solid set of use cases in zone A. The products are already in use for years with roughly a hundred of customers, including many high profile names. It is a pretty good situation to redefine the structure. This set of use cases are the foundation for defining the high level components including layout, container (main, panel, pop-up, etc), navigation, etc.",[16,415,416],{},"BIn this context, aware but not “understand” means it is in practice but not fully justified. e.g. There were a billing method that were only used by one customer. It is a viable and important use case when we design for that specific feature, but I would say it is in Zone B when design infrastructure level of design system. We won’t be able to optimize for this zone, but be aware of a few. They are important cases to use to be sure the infrastructure level design is not blocking the flow.",[16,418,419],{},"C Again, in this context, it means not aware of certain use case in customer practice, but we may consider it a potential from product\u002Fdesign perspective. e.g. An AI based billing assistant.",[16,421,422],{},"D we don’t know what we don’t know. At atom level, it is usually not destructive to add new item in the design system for new use cases. At infrastructure level, it could be, so it is more essential to go a little further based on B and C, even though some may not be immediate need. One other thing we can do here is more on mindset — always be open-minded, willing to hear.",[11,424,426],{"id":425},"some-morethoughts","Some More Thoughts",[16,428,429],{},"It was a project I worked on 5 years ago, so here is a looking glass view to add.",[312,431,432,435,438,441],{},[102,433,434],{},"Design System is not just for designers. More importantly, it should be considered as a shared understanding of the whole product-design-engineering team. As a result, documentation is very important. Make sure this “shared understanding” is in a shared accessible space.",[102,436,437],{},"Documentation is not just a list of visual elements, it needs to include applicable context, basic design rationale (intention), applied example and possible interactive “playground”. Documentation is as important as the design itself.",[102,439,440],{},"At infrastructure level, we’ve defined layout, container (main, panel, pop-up, etc), navigation. When look back, I would add “language” — the way you talk via the UI. The interaction is not only via navigation but also personable and respectful language communication.",[102,442,443],{},"Last but not least, probably more importantly, Design System should be an enabler, not a restrictor.",{"title":21,"searchDepth":163,"depth":163,"links":445},[446,447,448,449],{"id":375,"depth":163,"text":376},{"id":385,"depth":163,"text":386},{"id":398,"depth":163,"text":399},{"id":425,"depth":163,"text":426},"Apttus \u002F Conga","2023-07-04","Built the infrastructure layer of Nova 2.0 — layouts, containers, and navigation for a multi-product design system.","Design System",{},3,"\u002Fwork\u002Fapttus-design-system","Senior UX Designer",{"title":365,"description":452},[460,461,462],"Design Systems","Information Architecture","Documentation","work\u002Fapttus-design-system","dWj2oZVezmes5WVoLSOqpT1-2rlHlmDzLYTnHY9F-a8",{"id":466,"title":467,"body":468,"company":618,"date":619,"description":620,"draft":173,"extension":174,"featured":175,"industry":621,"meta":622,"navigation":175,"order":623,"path":624,"role":625,"seo":626,"skills":627,"stem":628,"thumbnail":557,"__hash__":629},"work\u002Fwork\u002Fapttus-billing.md","Design for billing, the structured and unstructured use cases",{"type":8,"value":469,"toc":605},[470,474,476,479,482,486,489,496,499,506,509,514,518,525,530,533,547,553,558,562,565,569,572,575,578,585,590,593,596,599],[11,471,473],{"id":472},"design-for-billing-the-structured-and-unstructured-usecases","Design for billing, the structured and unstructured use cases",[11,475,386],{"id":385},[16,477,478],{},"Apttus was positioned as a Quote-to-Cash Company with 3 product pillars, Quoting, Contracting and Finance. While I was there, owning the UX for the finance pillar (including order management, billing and revenue recognition), 70-80% of my time was spent on billing.",[16,480,481],{},"The main initiative of Billing was to design the billing product for Apttus cloud. At the time, the billing product of Apttus had over 500 existing customers in 18 industry verticals, for the Salesforce version. The goal was not only to bring the new cloud solution to feature parity with the Salesforce version, but also bring the UX to next level, free from the limitations of the Salesforce UI.",[11,483,485],{"id":484},"the-billing-usecases","The Billing Use Cases",[16,487,488],{},"There were a big list of use cases, a large portion of which were presented in the format of “wizard”, due to the high volume and highly repetitive nature of billing activities. The setups are highly structured to handle the “automatable” and leave human for the “tough cases”. Example features are set up for invoice run, usage run, billing plan, billing term, etc.",[16,490,491,492,495],{},"An one phrase principle for designing this category would be, as the title of the renown UX classics, “",[27,493,494],{},"Don’t Make Me Think","”.",[16,497,498],{},"The rest, I’d like to call them unstructured use cases, e.g. landing page, object page, forecast, analytical page, etc. A good example is the “Prescriptive Billing” account page, which provided layers of information for initiating\u002Fmaking informed actions. In this case, there is a prescribed action, however we still put the control and transparency to the user’s hand.",[16,500,501,502,505],{},"An one phrase principle for designing this category would be “",[27,503,504],{},"Got Me Thinking","” , providing conversation start points, thought stream stimuli or potential actions.",[16,507,508],{},"There are many ways to approach a design problem, While working on this big overhaul I started to really think the way to discuss in this writing — is it structured or unstructured. Below is a quick chart of the approach, to be followed by two specific billing use cases.",[16,510,511],{},[19,512],{"alt":21,"src":513},"\u002Fimages\u002Fwork\u002Fapttus-billing\u002F01.png",[11,515,517],{"id":516},"design-for-the-structured","Design for the Structured",[16,519,520,521,524],{},"The Apttus Billing on Salesforce UI was relatively mature with a big customer base. It provided a great reference point for ",[27,522,523],{},"WHAT"," to be designed. At the same time, luckily, we were not constrained to the **HOW **(user will experience it).",[526,527,529],"h3",{"id":528},"to-understand","To Understand",[16,531,532],{},"The design decisions are supported by four main pillars.",[99,534,535,538,541,544],{},[102,536,537],{},"Study existing product (Salesforce) — systematically understand what’s there and how well they are used",[102,539,540],{},"Finance and billing focused training — systematically understand the operational context",[102,542,543],{},"Competitive products — fractured information, hard to understand underlying logic but great thought stimuli",[102,545,546],{},"Don’t forget the Human, on going user research with internal\u002Fexternal billing team through out the process — understand the underlying logic, the tips and trick and the real pain",[548,549,550],"blockquote",{},[16,551,552],{},"Side notes on research with internal team. It was considered as less ideal to start with, but turned out to be a fortune to have. I recruited two of our own billing specialists (AR and AP) to participant throughout the design process. We had multiple sessions of interviews and I was able to look deep and broad into their working context. I was able to looking into things like their secrete excel formula, real purchase orders\u002Finvoices and chat over the “difficult accounts”. With external users, the conversation is hard to go as deep and the artifacts are almost impossible to collect (sensitive data).",[16,554,555],{},[19,556],{"alt":21,"src":557},"\u002Fimages\u002Fwork\u002Fapttus-billing\u002F02.png",[526,559,561],{"id":560},"to-design","To Design",[16,563,564],{},"Taking the invoice run setup as an example. There is two layers of designing, after a thorough understanding of the needs. 1) decide on the interaction paradigm, wizard in this case, and structure (key decision making steps or “independent” logic blocks); 2) input needs and interaction\u002Fcommunication strategy.",[11,566,568],{"id":567},"design-for-the-unstructured","Design for the unStructured",[16,570,571],{},"“Don’t make me think” set the premise of what a good software (or interaction) should behave and widely accepted. It is the touchstone for a cognitive walkthrough before you even dare to take users’ time for testing.",[16,573,574],{},"However, after years of design for operation and get into supporting complex business decision making. I wondered: is design really meant to keep users from thinking and wondering and pondering, or is design even capable to do that. Maze-solving is fun. Business operations has a large “streamlinable” part and also opportunities to experience a multi-in multi-out maze with unique decision makings and “tokens” to collect along the way before finding the exit.",[526,576,529],{"id":577},"to-understand-1",[16,579,580,581,584],{},"The keys to understand for an informed “maze” navigation are 1) where should we leave an exit open, 2) where to shine a light when needed. In another word, we need to understand 1) the potential decisions that the user may reach within this ",[27,582,583],{},"context"," and 2) what are the information that can lead to or support the decision at the specific context and timing.",[16,586,587],{},[19,588],{"alt":21,"src":589},"\u002Fimages\u002Fwork\u002Fapttus-billing\u002F03.png",[526,591,561],{"id":592},"to-design-1",[16,594,595],{},"To design for this category, I believe the best way is to",[16,597,598],{},"First, design the layout depends on the decisions that the visual communication\u002F design may lead to, based on impact-driven ranking of the decisions. \nFollow that, lay the information out into the layout blocks by the first step. Key information or “prescription” (if available) first, then fit in the supporting information with goal to further ground the potential decision building user confidence in the potential decision.",[16,600,601,602],{},"In practice, I feel design for the unstructured user case requires deeper understanding of the underlying logic of user’s “think”, “feel” and “gain”, while design for structured use cases focus more on the understanding of “say”, “do” and “pain” in a classic ",[27,603,604],{},"Empathy Map.",{"title":21,"searchDepth":163,"depth":163,"links":606},[607,608,609,610,614],{"id":472,"depth":163,"text":473},{"id":385,"depth":163,"text":386},{"id":484,"depth":163,"text":485},{"id":516,"depth":163,"text":517,"children":611},[612,613],{"id":528,"depth":455,"text":529},{"id":560,"depth":455,"text":561},{"id":567,"depth":163,"text":568,"children":615},[616,617],{"id":577,"depth":455,"text":529},{"id":592,"depth":455,"text":561},"Apttus","2023-08-21","Defined the UX framework for billing — when to minimize cognitive load vs. when to maximize decision support.","Finance",{},4,"\u002Fwork\u002Fapttus-billing","UX Design Lead, Finance Pillar",{"title":467,"description":620},[185,184,183],"work\u002Fapttus-billing","rm7z8q9vR7ONZlGcTdEHkNlDPiFj66SV2u7emw09trM",{"id":631,"title":632,"body":633,"company":815,"date":816,"description":817,"draft":173,"extension":174,"featured":173,"industry":818,"meta":819,"navigation":175,"order":820,"path":821,"role":822,"seo":823,"skills":824,"stem":827,"thumbnail":646,"__hash__":828},"work\u002Fwork\u002Fsap-employee-dashboard.md","Bridge — SAP Employee Dashboard",{"type":8,"value":634,"toc":800},[635,639,642,647,650,653,657,661,664,667,671,674,677,681,684,688,692,695,698,709,726,734,742,746,750,755,760,765,770,775,780,785,789,792,795],[11,636,638],{"id":637},"bridgesap-employee-dashboard","Bridge — SAP Employee Dashboard",[16,640,641],{},"Bridge is the SAP Employee Dashboard to connect the dots of our workday for both work and life.",[16,643,644],{},[19,645],{"alt":21,"src":646},"\u002Fimages\u002Fwork\u002Fsap-employee-dashboard\u002F01.png",[16,648,649],{},"Employee could see the comprehensive view of everything that touch the workday — life and work, from the morning commute, lunch of the day all the way to project progress and development status.",[16,651,652],{},"Bridge is an internal tools, however it is one of the projects that brought me the most satisfaction. The satisfactions was not from the big brand names of customers, but from the dozens of “thank you” emails that were pouring into our team email during our first month of launch. Proud to be in the team and led the UX design.",[11,654,656],{"id":655},"how-itstarted","HOW IT STARTED?",[526,658,660],{"id":659},"the-pain","THE PAIN",[16,662,663],{},"We have over 80 web tools internally to support the product development and daily work. The overall using experience of daily tools are fragmented, disconnected. Some of the tools become such a chore that employees started to avoid them which brought in compliance and productivity issues.",[16,665,666],{},"Bridge was initiated to bridge the gaps, to provide a single access point to most (if not all) of employee’s daily tools (web applications).",[526,668,670],{"id":669},"find-the-most-impactful","FIND THE MOST IMPACTFUL",[16,672,673],{},"Among the pains of using internal tools, there is one chore that touches every single employee on a weekly basis. It is to log in our working hours in to CAT2, the standard SAPGUI system. The system is so non-intuitive that as new hires we all have received a several pages long instructions to use it. It is so hard to use that employee often delay the entries weeks to months until they were “forced” to make it up to date.",[16,675,676],{},"Bridge beautifully solved the time entry problem through interactive web interface, which greatly contribute to its quick adoption globally.",[526,678,680],{"id":679},"everyone-is-theowner","EVERYONE IS THE OWNER",[16,682,683],{},"Bridge is build on SAP internal GitHub, not only code all discussion from design to technical was happening in GitHub. Some of our early adopters quickly took their ownership of the new tool and contributed to our discussion and even development.",[11,685,687],{"id":686},"what-idid","WHAT I DID?",[526,689,691],{"id":690},"the-context-andprocess","THE CONTEXT AND PROCESS",[16,693,694],{},"I was brought in the project after the first version was delivered (as the screenshot below), which aimed to address the three values mentioned. I love the tool, at the same time saw lots of opportunities to rethink the user experience.",[16,696,697],{},"This project lived entirely in GitHub, from product\u002Fdesign discussion to implementation and bug fixing, to provide full transparency to any colleague interested to contribute globally. As a result, the design process (or more of design delivery process) is handled a little uniquely. Here is what happened:",[312,699,700,706],{},[102,701,702,703],{},"I sketched out the user journey and then had a cognitive walk through of the product. The goals was to identify** touch points** and ",[27,704,705],{},"design opportunities.",[102,707,708],{},"I created an GitHub issues — re-Design Topics and Goals, and had a conference call with the product owner and dev team to get their buy-in. The topics listed were:",[99,710,711,714,717,720,723],{},[102,712,713],{},"Extendability as the product grow — how to organize the dashboard and the tile library.",[102,715,716],{},"Usability of overgrown search based tiles — consolidate search needs",[102,718,719],{},"Usability of weather based app background—redesign visual for weather",[102,721,722],{},"Be more inviting to contributors and collaborators",[102,724,725],{},"Visual cleanup",[312,727,728,731],{"start":455},[102,729,730],{},"I start to post design details via Slack and via creating separated issues for each topic we agreed on, as design progressing.",[102,732,733],{},"Design get implemented quickly as they are signed-off by stakeholders via GitHub issues.",[16,735,736,740],{},[19,737],{"alt":738,"src":739},"Bridge before redesign","\u002Fimages\u002Fwork\u002Fsap-employee-dashboard\u002F02.png",[122,741,738],{},[11,743,745],{"id":744},"the-newdesign","THE NEW DESIGN",[526,747,749],{"id":748},"think-beyond-bridging-internaltools","THINK BEYOND BRIDGING INTERNAL TOOLS",[16,751,752],{},[27,753,754],{},"Spotlight like search function",[16,756,757],{},[19,758],{"alt":21,"src":759},"\u002Fimages\u002Fwork\u002Fsap-employee-dashboard\u002F03.png",[16,761,762],{},[27,763,764],{},"Needs met, elegantly",[16,766,767],{},[19,768],{"alt":21,"src":769},"\u002Fimages\u002Fwork\u002Fsap-employee-dashboard\u002F04.png",[16,771,772],{},[27,773,774],{},"Easy customization — WYSIWYG",[16,776,777],{},[19,778],{"alt":21,"src":779},"\u002Fimages\u002Fwork\u002Fsap-employee-dashboard\u002F05.png",[16,781,782],{},[27,783,784],{},"The list goes on …",[11,786,788],{"id":787},"poster-for-10000-unique-usersmonth","POSTER FOR 10,000 unique users\u002Fmonth",[16,790,791],{},"Bridge touches the user pain points and received quick adoption. At April 2015, we hits 10,000 unique users\u002Fmonth. I designed the poster below, to celebrate our success and more importantly to spread the words using the power of number.",[16,793,794],{},"The message behind the poster: inspire curiosity, build trust through solid number and call for action.",[16,796,797],{},[19,798],{"alt":21,"src":799},"\u002Fimages\u002Fwork\u002Fsap-employee-dashboard\u002F06.png",{"title":21,"searchDepth":163,"depth":163,"links":801},[802,803,808,811,814],{"id":637,"depth":163,"text":638},{"id":655,"depth":163,"text":656,"children":804},[805,806,807],{"id":659,"depth":455,"text":660},{"id":669,"depth":455,"text":670},{"id":679,"depth":455,"text":680},{"id":686,"depth":163,"text":687,"children":809},[810],{"id":690,"depth":455,"text":691},{"id":744,"depth":163,"text":745,"children":812},[813],{"id":748,"depth":455,"text":749},{"id":787,"depth":163,"text":788},"SAP","2016-11-23","Designed Bridge — a unified launchpad reclaiming lost productivity from fragmented internal workflows at SAP.","Employee Productivity",{},5,"\u002Fwork\u002Fsap-employee-dashboard","UX Specialist",{"title":632,"description":817},[825,185,826],"Service Design","Employee Experience","work\u002Fsap-employee-dashboard","15KLVUPMGdSMlwipwESJuOaMQ8v6_zFkcFwWepNxuho",{"id":830,"title":831,"body":832,"company":815,"date":933,"description":934,"draft":173,"extension":174,"featured":173,"industry":935,"meta":936,"navigation":175,"order":937,"path":938,"role":822,"seo":939,"skills":940,"stem":944,"thumbnail":894,"__hash__":945},"work\u002Fwork\u002Fsap-iot-simulator.md","IoT Simulator — refocus on action",{"type":8,"value":833,"toc":928},[834,838,841,844,847,851,854,859,862,867,872,877,882,886,889,897,900,908,911,914,922,925],[11,835,837],{"id":836},"iot-simulatorrefocus-onaction","IoT Simulator — refocus on action",[16,839,840],{},"“a problem well-stated is half-solved.” -Charles Kettering",[16,842,843],{},"IoT Simulator is a tool for simulating data message of IoT sensors. It creates a virtual IoT environment for developers to test their code when it is not feasible to develop with a real sensor network. IoT Simulator also enables QA, P&R specialist and Presales to generate sensors messages for test or demo purpose.",[16,845,846],{},"The team has worked on IoT Simulator for three months, a design was delivered to the engineering team. However, there is something wrong with it that make it hard to understand how to use. My task was to rethink the user experience.",[11,848,850],{"id":849},"state-theproblem","STATE THE PROBLEM",[16,852,853],{},"30 pages of product requirements and a dozen screenshots of previous design is what I have to get started. The three key tasks for the application is create “simulation”, configure “execution” and execute “execution”. The previous design has all the information onscreen and has screens for all the tasks, however screens didn’t flow. It takes me a while to sort out the relationship among the screens.",[548,855,856],{},[16,857,858],{},"How to make the tasks flow?",[16,860,861],{},"Can I spin the question\u002Fproblem from different angle? The questions could be:",[548,863,864],{},[16,865,866],{},"Why does our user groups need to perform the tasks?",[548,868,869],{},[16,870,871],{},"What are the relationship among the tasks?",[548,873,874],{},[16,875,876],{},"Are users already familiar with the concept and terms?",[548,878,879],{},[16,880,881],{},"Does the information on screen well support actions?",[11,883,885],{"id":884},"the-re-shape-opportunity","THE RE-SHAPE OPPORTUNITY",[16,887,888],{},"Went through the questions and then look at the previous screens been delivered. The problem gets clearer — Actions were put in a secondary position while information is surfaced as primary.",[16,890,891,895],{},[19,892],{"alt":893,"src":894},"Previous Design","\u002Fimages\u002Fwork\u002Fsap-iot-simulator\u002F01.png",[122,896,893],{},[16,898,899],{},"While we worked on so many apps that are focus on data analytics in SAP, this one is not. It is for taking actions, with information to support — only the right amount of information at the right time. Redesign was smooth once the problem is well-stated. The stages of the tasks became very clear to me and mapped to my years of experience in designing for printing.",[16,901,902,906],{},[19,903],{"alt":904,"src":905},"Understand the concept through a printing analogy","\u002Fimages\u002Fwork\u002Fsap-iot-simulator\u002F02.png",[122,907,904],{},[16,909,910],{},"The opportunity for reshaping the experience start to unfold. Actions was put to the center of the new user experience, specifically I refocused the design to deliver clearer call to action; enable quick action based on history; provide sufficient and efficient information to support action and provide distinguishable visual for different stages of the action flow.",[16,912,913],{},"The key screens are simplified to three: one for enabling quick actions; one for creating simulations and configure executions and the last one for execute and monitor executions.",[16,915,916,920],{},[19,917],{"alt":918,"src":919},"Three Key Screen of Redesign","\u002Fimages\u002Fwork\u002Fsap-iot-simulator\u002F03.png",[122,921,918],{},[16,923,924],{},"The full redesign also include consideration for access right and relationship of different user groups, etc.",[16,926,927],{},"Contact me if you would like to know more.",{"title":21,"searchDepth":163,"depth":163,"links":929},[930,931,932],{"id":836,"depth":163,"text":837},{"id":849,"depth":163,"text":850},{"id":884,"depth":163,"text":885},"2016-11-17","Refocused an IoT simulator from data display to actionable decision-making for manufacturing operators.","Action Driven Data",{},6,"\u002Fwork\u002Fsap-iot-simulator",{"title":831,"description":934},[941,942,943],"Interaction Design","Prototyping","IoT","work\u002Fsap-iot-simulator","bX74Xna3gXPUtuIJrR0S3iH7hsw0SjGSZgidRuUgU9Y",{"id":947,"title":948,"body":949,"company":1043,"date":1044,"description":1045,"draft":173,"extension":174,"featured":173,"industry":1046,"meta":1047,"navigation":175,"order":1048,"path":1049,"role":822,"seo":1050,"skills":1051,"stem":1055,"thumbnail":974,"__hash__":1056},"work\u002Fwork\u002Fmanufacturing-dashboard.md","Operational Efficiency Dashboard for Manufacturing",{"type":8,"value":950,"toc":1036},[951,954,957,961,964,967,970,975,980,984,987,998,1001,1006,1010,1013,1016,1019,1024,1028,1031],[11,952,948],{"id":953},"operational-efficiency-dashboard-for-manufacturing",[16,955,956],{},"The application is aiming to support Perfect Order Fulfillment in manufacturing, in co-innovation with a leading manufacturer of construction engines.",[11,958,960],{"id":959},"the-problem","THE PROBLEM",[16,962,963],{},"The construction engine giant was still running on papers — lots of papers. A two days workshop and dozens of technical documents — Excel sheets and PowerPoints, were given to help us understand the problem space and find the right target. A daily communication with customer was also kept throughout the project.",[16,965,966],{},"The final goal for this customer was Perfect Order Fulfillment. The Supply Chain Council describes perfect order fulfillment as a discrete measurement defined as the percentage of orders delivered to the right place, with the right product, at the right time, in the right condition, in the right package, in the right quantity, with the right documentation, to the right customer, with the correct invoice.",[16,968,969],{},"Within the phase we worked on, scope was limited to optimize the manufacturing operation.",[16,971,972],{},[19,973],{"alt":21,"src":974},"\u002Fimages\u002Fwork\u002Fmanufacturing-dashboard\u002F01.png",[16,976,977],{},[19,978],{"alt":21,"src":979},"\u002Fimages\u002Fwork\u002Fmanufacturing-dashboard\u002F02.png",[11,981,983],{"id":982},"the-solution","THE SOLUTION",[16,985,986],{},"A Operational Efficiency Dashboard was designed and developed, targeting making the manufacturing process efficient and effective, including components for",[99,988,989,992,995],{},[102,990,991],{},"monitoring SCOR KPI;",[102,993,994],{},"tracking orders throughout the manufacturing line;",[102,996,997],{},"supporting flexible and efficient order scheduling.",[16,999,1000],{},"Working in close collaboration with Customer operation team, we delivered the solution that led to a big sales deal and long-term collaboration.",[16,1002,1003],{},[19,1004],{"alt":21,"src":1005},"\u002Fimages\u002Fwork\u002Fmanufacturing-dashboard\u002F03.png",[11,1007,1009],{"id":1008},"explore-the-interactions","EXPLORE THE INTERACTIONS",[16,1011,1012],{},"There are many interesting challenges in the interaction design part due to the large amount of KPI involve in the manufacturing process.",[16,1014,1015],{},"One example in designing the interaction is factory map configuration. Because it is a solution that is going to be carry out in several manufacturing plants globally, it is not practical and sustainable to pre-ship factory maps. The key configuration is to map spaces on a x by y matrix to the factory stations, sections, cost centers, etc.",[16,1017,1018],{},"The UI developer was told by PM to explore using drag-n-drop — drag from a long list of names to a dense matrix that reflect factory layout. However, through a quick Cognitive Walkthrough, I was sure it is not the right pattern to use. Because the visual scanning between the assigning list and the matrix and the map reference (be it a real map on paper) will interrupt the continuity of the flow, user will need to refocus onto the right spot of space every time then move their eye away and back. The solution I proposed which quickly approved by both engineering and PO is click-n-assign, through a in-place pop-up combo box. It not only significantly reduce users' cognitive load by letting them continue moving along the space\u002Fmap, but also reduce the development efforts.",[16,1020,1021],{},[19,1022],{"alt":21,"src":1023},"\u002Fimages\u002Fwork\u002Fmanufacturing-dashboard\u002F04.png",[11,1025,1027],{"id":1026},"my-design-playground","MY DESIGN PLAYGROUND",[16,1029,1030],{},"The design delivered above is based on SAP Fiori framework. I also had some fun to play with a concept freely, which focused on a view we scoped out for the business delivery — daily view.",[16,1032,1033],{},[19,1034],{"alt":21,"src":1035},"\u002Fimages\u002Fwork\u002Fmanufacturing-dashboard\u002F05.png",{"title":21,"searchDepth":163,"depth":163,"links":1037},[1038,1039,1040,1041,1042],{"id":953,"depth":163,"text":948},{"id":959,"depth":163,"text":960},{"id":982,"depth":163,"text":983},{"id":1008,"depth":163,"text":1009},{"id":1026,"depth":163,"text":1027},"SAP \u002F Caterpillar","2016-11-28","Co-innovated with Caterpillar to design operational efficiency dashboards for manufacturing workflows.","Operational Efficiency",{},7,"\u002Fwork\u002Fmanufacturing-dashboard",{"title":948,"description":1045},[1052,1053,1054],"Dashboard Design","Customer Co-innovation","Data Visualization","work\u002Fmanufacturing-dashboard","lFkMEZAokEztVnGCOaN3flkR-lJlnGwRAm4F2DNIGOc",{"id":1058,"title":1059,"body":1060,"company":815,"date":1259,"description":1260,"draft":173,"extension":174,"featured":173,"industry":1261,"meta":1262,"navigation":175,"order":1263,"path":1264,"role":822,"seo":1265,"skills":1266,"stem":1269,"thumbnail":1082,"__hash__":1270},"work\u002Fwork\u002Fsapbot.md","SAPbot — help you stay focused",{"type":8,"value":1061,"toc":1251},[1062,1066,1069,1071,1074,1077,1085,1089,1094,1099,1104,1109,1114,1119,1123,1126,1152,1156,1159,1162,1165,1168,1181],[11,1063,1065],{"id":1064},"sapbothelp-you-stayfocused","SAPbot — help you stay focused",[16,1067,1068],{},"SAPbot is chatbot reinvented from Github Hubot, to “run errands” and keep you focused.",[526,1070,386],{"id":385},[16,1072,1073],{},"Working on simplifying the overall tool landscape (over 80 tools) as a long-term task and designing for one of the tools call PFDB at the same time. I found out that integration is a major challenge for a smooth user journey of working day with multiple tools. The large set of tools live in silo while need to work together.",[16,1075,1076],{},"SAPbot was born from the insights I distilled along the way.",[16,1078,1079,1083],{},[19,1080],{"alt":1081,"src":1082},"Internal tools organized into the development process","\u002Fimages\u002Fwork\u002Fsapbot\u002F01.png",[122,1084,1081],{},[526,1086,1088],{"id":1087},"opportunities-and-limitations","Opportunities and Limitations",[548,1090,1091],{},[16,1092,1093],{},"Large number of internal apps are disconnected",[548,1095,1096],{},[16,1097,1098],{},"Internal apps need to work together throughout the development life-cycle",[548,1100,1101],{},[16,1102,1103],{},"Hopping among different tools to look for a value is a pain",[548,1105,1106],{},[16,1107,1108],{},"Some tasks users perform in secondary tools are simple and could potentially be automated",[548,1110,1111],{},[16,1112,1113],{},"All apps are web based — potential connect point",[548,1115,1116],{},[16,1117,1118],{},"We have limited development resources",[526,1120,1122],{"id":1121},"sapbot","SAPbot",[16,1124,1125],{},"is not a smart bot, reinvented from GitHub Hubot that",[99,1127,1128,1131,1134,1137,1140,1143,1146,1149],{},[102,1129,1130],{},"can be easily developed on Github (Enterprise version)",[102,1132,1133],{},"is a set of chat bots live as an chrome extension, so user can interact with it without leaving their current working context (current web app)",[102,1135,1136],{},"helps user to access information or accomplish simple task of the 3rd web app\u002Fservice without needing to launch the app itself",[102,1138,1139],{},"is developed on GitHub Enterprise, so the owning team of each app will be able to create and iterate their own bot",[102,1141,1142],{},"streamline workflow",[102,1144,1145],{},"provide transparency into multiple system status",[102,1147,1148],{},"can grow organically by the internal GitHub community",[102,1150,1151],{},"is a SAP tryout of ChatOPS *",[526,1153,1155],{"id":1154},"interaction","Interaction",[16,1157,1158],{},"Because SAPbot is not a smart bot but only respond to specific comments, we need to design the language that user can easily remember.",[16,1160,1161],{},"A fair and important product assumption I made is: user knows the name of the tool he\u002Fshe is going to interact with. Also, with the intention to make the maintain of bot sustainable, each tool is designed to have its own designated bot, so the owning team of that web tool can take over the bot ownership at their will.",[16,1163,1164],{},"The dialog design is based on the way we designate a bot to each tool:",[16,1166,1167],{},"Basic command format recommended (Tools owner will be able to define their own command based on their specific needs and task):",[548,1169,1170],{},[16,1171,1172,1173],{},"@botname what is ",[1174,1175,1176,1177],"fieldlable",{}," for ",[1178,1179,1180],"an",{"identifiable":21,"object":21},": for fetching a value from another web tool (to connect the tools that has cross reference)",[548,1182,1183],{},[16,1184,1185,1186],{},"@botname ",[1187,1188,1189,1190],"task",{}," ",[1191,1192,1193,1194,1203,1207,1210,1218,1226,1229,1234,1238,1241,1244,1248],"object",{},": for automate a task for an object (e.g. for devops. object is optional)",[548,1195,1196],{},[16,1197,1198,1199],{},"@botname how to ",[1200,1201,1202],"term",{},": for informational bot (e.g. Playbook example below)",[526,1204,1206],{"id":1205},"sustain-andgrowth","Sustain and Growth",[16,1208,1209],{},"Our team is not able to design and maintain every single chatbot. We need to spread the words out and encourage the community to flesh it out. The public web pages are created with this in mind. We also feature SAPbot in the developer events we were designing at the time.",[16,1211,1212,1216],{},[19,1213],{"alt":1214,"src":1215},"SAPbot Homepage —introduce our Chatbot and invite the community","\u002Fimages\u002Fwork\u002Fsapbot\u002F02.png",[122,1217,1214],{},[16,1219,1220,1224],{},[19,1221],{"alt":1222,"src":1223},"SAPbot — About me","\u002Fimages\u002Fwork\u002Fsapbot\u002F03.png",[122,1225,1222],{},[16,1227,1228],{},"*ChatOps, I like to quote the definition from Atlassian:",[548,1230,1231],{},[16,1232,1233],{},"ChatOps is a collaboration model that connects people, tools, process, and automation into a transparent workflow. This flow connects the work needed, the work happening, and the work done in a persistent location staffed by the people, bots, and related tools.",[526,1235,1237],{"id":1236},"my-role","My Role",[16,1239,1240],{},"I initiated the project, wrote the product vision, designed the workflow and interaction, convinced our architect to work on it providing both product design and initial technical research (possible library to use).",[16,1242,1243],{},"I was not assigned to design a chatbot. I was assigned to simplify and streamline the development process; I was assigned to improve the usability of an isolated feature management application called PFDB; I was assigned to think about how to onboard developers to SAP GitHub Enterprise. These separate but connected topics surfaced the opportunity.",[526,1245,1247],{"id":1246},"the-status","The Status",[16,1249,1250],{},"SAPbot was developed and featured as one of the topic in our global developer event -Toolathon. One of the implementation of SAPbot won first place of the first Toolathon event. However, due to technical issue with single sign-on, the project stopped several months after launching.",{"title":21,"searchDepth":163,"depth":163,"links":1252},[1253],{"id":1064,"depth":163,"text":1065,"children":1254},[1255,1256,1257,1258],{"id":385,"depth":455,"text":386},{"id":1087,"depth":455,"text":1088},{"id":1121,"depth":455,"text":1122},{"id":1154,"depth":455,"text":1155},"2017-02-27","Designed SAPbot — a conversational AI assistant helping employees stay focused by surfacing relevant tasks and information.","Chatbot",{},8,"\u002Fwork\u002Fsapbot",{"title":1059,"description":1260},[1267,1268,185],"Conversational UI","AI Assistant","work\u002Fsapbot","ROidMBlJQpqOkD8ey__PH4e17Kw5SWkJyJRh-JmfKic",1776257913544]