[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-11-12-":3},{"paginated":4,"total":1073},[5,287,500,689,809,890],{"id":6,"title":7,"author":8,"body":9,"categories":272,"date":274,"description":275,"extension":276,"featuredImage":277,"mainImage":278,"meta":280,"navigation":281,"path":282,"previewImage":283,"seo":284,"stem":285,"tags":277,"__hash__":286},"blog/blog/designing-through-conversation-with-ux-firm-digital-telepathy.md","Designing Through Conversation with UX Firm Digital Telepathy","Axure",{"type":10,"value":11,"toc":259},"minimark",[12,17,34,46,50,53,63,69,72,76,82,88,94,97,101,106,111,114,119,123,128,139,144,147,151,156,161,166,169,173,178,183,186,191,195,198,203,206,210,213,219,225,231,246],[13,14,16],"h2",{"id":15},"can-we-talk","Can we talk?",[18,19,20,27,28,33],"p",{},[21,22,26],"a",{"href":23,"rel":24},"http://www.dtelepathy.com/",[25],"nofollow","Digital Telepathy"," has always done things differently. When you hire the San Diego-based design firm, you won't hear any pitches. Instead, you'll embark on a journey with a partner, one that involves a constant flow of conversation to propel the project forward. This journey is called ",[21,29,32],{"href":30,"rel":31},"http://www.dtelepathy.com/blog/philosophy/objective-based-design-creative-approach-to-solving-business-challenge",[25],"Objective-Based Design",".",[18,35,36,37,41,42,45],{},"As part of this process, Digital Telepathy creates assets designed to spark discussions with its clients. Conversations are how Digital Telepathy collaborates with clients to build products, design experiences and solve business challenges. The company's Art Director, ",[38,39,40],"strong",{},"Jessica Moon",", and Senior UX Designer, ",[38,43,44],{},"Cody Iddings",", walk us through their distinctive process and how they and others at the experience design firm use Axure to create those conversation pieces.",[13,47,49],{"id":48},"design-by-objective","Design by Objective",[18,51,52],{},"Objective-Based Design is as much a philosophy as it is a process. Start with your objectives. Research to discover points of friction and identify areas of opportunity. Create a strategy to improve the experience and accomplish the business' primary objectives. Implement your ideas. Measure and reflect on the results. Iterate. Repeat.",[18,54,55,62],{},[38,56,57],{},[21,58,61],{"href":59,"rel":60},"http://www.dtelepathy.com/blog/author/barefoot-ceo",[25],"Chuck Longanecker",", Digital Telepathy Founder, describes the thinking this way:",[64,65,66],"blockquote",{},[18,67,68],{},"The idea is to focus on your business objectives and work backwards to determine strategies that will accomplish them. Your objectives can relate to huge goals or a simple growth project. A key ingredient to this process is identifying friction. Friction hinders your customers' journey and it holds the secret to how you can design solutions to improve their experience.",[18,70,71],{},"Sprinkled throughout this journey are a variety of assets created to move the dialogue along. The following are five examples that help illustrate this process.",[13,73,75],{"id":74},"competitive-landscape-analysis","Competitive Landscape Analysis",[18,77,78,81],{},[38,79,80],{},"When:"," Research Phase",[18,83,84,87],{},[38,85,86],{},"What:"," This tool presents clients with a spectrum of possibilities when exploring themes such as visual design, UX patterns, and brand positioning. This particular piece, created by Jessica using Axure RP's show/hide interactions, shows a range of UX applications arranged by their ease of use. The green arrow indicates where the client currently sits along the spectrum, while the blue arrow shows the project target for creating a simpler, more intuitive user interface. But it could also apply to other qualities such as tone (playful or serious), color (high value or low value), design aesthetic (flat or skeuomorphic), and so on. Clicking along the spectrum allows clients to see the range of possibilities.",[18,89,90,93],{},[38,91,92],{},"Why:"," The tool invites hands-on exploration in a way that lets clients define their comfort zone by toggling on and off specific examples to focus conversation. If structured properly, the tool can generate the type of discussions that lead to better alignment between design team and client on aesthetic, as well as functional, choices.",[18,95,96],{},"\"We found what really drives great conversations with our clients is having an interactive talking piece that we can maneuver into specific strategic areas of focus,\" Jessica said. \"How do all potential competitors handle this? What about the niche tools?\"",[13,98,100],{"id":99},"content-wire","Content Wire",[18,102,103,105],{},[38,104,80],{}," Strategy Phase",[18,107,108,110],{},[38,109,86],{}," The Content Wire is usually a simple layout containing copy to represent a broad narrative. It's designed to initiate conversation about the story being told and the narrative points along the way, as well as what language is to be used on the site.",[18,112,113],{},"\"We don't see these as wires or prototypes,\" Jessica said. \"They're conversation facilitators.\"",[18,115,116,118],{},[38,117,92],{}," By having the content laid out in the wireframe, Jessica and her team are able to have a deeper conversation about the overall flow users will be going through, and then the particular pieces of content on a given page. Focusing the conversation around content can lead to a clearer understanding of the final product and how it will accomplish the objective among all team members.",[13,120,122],{"id":121},"client-portal","Client Portal",[18,124,125,127],{},[38,126,80],{}," Throughout the project",[18,129,130,132,133,138],{},[38,131,86],{}," For big projects involving a large team, Jessica and Cody create an online portal using Axure RP that lets anyone on the project access all assets and deliverables as they are created and updated. The portals contain ",[21,134,137],{"href":135,"rel":136},"https://share.axure.com/",[25],"Axure Share"," links to key assets associated the project, including research documents, prototypes, style guides and other critical content. Rather than just a directory of shared files, however, the portal feels like an elegant microsite, creating a unified, branded experience for clients.",[18,140,141,143],{},[38,142,92],{}," As the project evolves, the deliverables are refined and more assets are added, including style guides, design documents, content wires and so on. The files are continually updated to reflect the most recent design decisions, keeping everyone in the loop and facilitating collaboration with team members and stakeholders, regardless of where they are located. This keys into two important values at Digital Telepathy: client empowerment and transparency.",[18,145,146],{},"\"When our clients are able to access all of our work through a single place, it empowers them to engage with us anytime and from anywhere,\" said Cody. \"It cultivates discussion by encouraging our clients to give us feedback when they see the things we are working on in real time.\"",[13,148,150],{"id":149},"scrolling-transition","Scrolling Transition",[18,152,153,155],{},[38,154,80],{}," Strategy and Implementation Phases",[18,157,158,160],{},[38,159,86],{}," Increasingly, design conversations occur around micro-interactions, which can be difficult to explain in words. In those situations, an interactive prototype can help crystallize a concept. The prototype above shows one such interaction",[64,162,163],{},[18,164,165],{},"This prototype took two seconds to show, and we got it approved on the spot. I'm not sure we could have done that with static comps. This was a much more efficient process of communication...",[18,167,168],{},"\"It created an 'ah-ha!' moment,\" Jessica said. \"This prototype took two seconds to show, and we got it approved on the spot. I'm not sure we could have done that with static comps. This was a much more efficient process of communication, because it conveyed an experience that makes things more tangible.\"",[13,170,172],{"id":171},"the-why","The Why",[18,174,175,177],{},[38,176,80],{}," Throughout the project and beyond",[18,179,180,182],{},[38,181,86],{}," The Why explains the research, thought process, and rationale behind each major design decision in the project. It's often a keystone element in the Portal described above because it supports transparency and client empowerment. The Why becomes an especially important document when the project touches dozens, or even hundreds, of team members in far-flung offices.",[18,184,185],{},"\"It's a great contextual guide to onboard team members with the various design thinking decisions in the project,\" Jessica explained. \"This empowers anyone involved in the project to make good new decisions aligned with the design thinking set by the team.\"",[18,187,188,190],{},[38,189,92],{}," As the project gets passed along, the conversation has to continue through other stakeholders. The Why helps clients continue that conversation internally, even when Digital Telepathy is no longer involved. \"When clients hit constraints, they're able to revisit the decisions and evolve them,\" Jessica explained.",[13,192,194],{"id":193},"the-upshot","The Upshot",[18,196,197],{},"Objective-Based Design is an approach anyone can use, not just designers. As a philosophy, it can be applied to large and small projects alike. As a process, it's fueled by continuous dialogue designed to identify key objectives, generate and prioritize solutions, implement them, assess the results and refine. To support this approach, Digital Telepathy has used Axure RP to create \"conversation starters.\"",[64,199,200],{},[18,201,202],{},"The prototypes we build are used in conjunction with client meetings. We use them in those meetings to help clients make decisions.",[18,204,205],{},"\"The prototypes we build are used in conjunction with client meetings,\" Cody noted. \"We use them in those meetings to help clients make decisions. In the end, we want to use the tool that lets us quickly communicate and rapidly iterate. Axure gives us the ability to have that collaboration time, rather than having to spend it pitching.\"",[13,207,209],{"id":208},"tips-for-getting-started-with-objective-based-design","Tips for Getting Started with Objective-Based Design",[18,211,212],{},"Cody and Jessica share the following advice for those who interested in trying out Objective-Based Design:",[18,214,215,218],{},[38,216,217],{},"Create deliverables that help spark conversations focused on their impact on objectives, rather than just about their aesthetic value."," This generates more engagement and results in better feedback, and more evolved designs, Cody said.",[18,220,221,224],{},[38,222,223],{},"Organize, share and update deliverables in one central online location using platforms such as Dropbox or Axure Share."," This fosters transparency, as well as provide all team members with up-to-the-minute assets for timely conversations, said Jessica.",[18,226,227,230],{},[38,228,229],{},"Think outside of the box."," Rather than seeing wireframes and prototypes as deliverables or presentation material, use them as building blocks for conversation pieces, Jessica advised.",[18,232,233,234,239,240,245],{},"\"A designer named ",[21,235,238],{"href":236,"rel":237},"http://danielmall.com/",[25],"Daniel Mall"," recently said that ",[21,241,244],{"href":242,"rel":243},"http://www.slideshare.net/danielmall/design-deliverables-for-a-postcomp-era",[25],"all deliverables should lead to conversation",",\" said Cody. \"That statement really changed the way I work.\"",[18,247,248,249,253,254,33],{},"If you'd like to learn more about implementing Objective-Based Design, you can read this ",[21,250,252],{"href":30,"rel":251},[25],"step-by-step description"," of the process. You can also check out how Digital Telepathy applies this process throughout its ",[21,255,258],{"href":256,"rel":257},"http://www.dtelepathy.com/work/",[25],"work with clients",{"title":260,"searchDepth":261,"depth":261,"links":262},"",2,[263,264,265,266,267,268,269,270,271],{"id":15,"depth":261,"text":16},{"id":48,"depth":261,"text":49},{"id":74,"depth":261,"text":75},{"id":99,"depth":261,"text":100},{"id":121,"depth":261,"text":122},{"id":149,"depth":261,"text":150},{"id":171,"depth":261,"text":172},{"id":193,"depth":261,"text":194},{"id":208,"depth":261,"text":209},[44,26,40,273],"User Stories","2015-12-03T00:00:00.000Z","Digital Telepathy has always done things differently. When you hire the San Diego-based design firm, you won't hear any pitches. Instead, you'll embark on a journey with a partner, one that involves a constant flow of conversation to propel the project forward. This journey is called Objective-Based Design. ","md",null,{"src":279},"/images/2019/04/uipfy1umamw.jpg",{},true,"/blog/designing-through-conversation-with-ux-firm-digital-telepathy",{"src":279},{"title":7,"description":275},"blog/designing-through-conversation-with-ux-firm-digital-telepathy","nsWzlRPq9nDOFVr7e0L3j-bcOS6dnP-X9uQPttGKErQ",{"id":288,"title":289,"author":8,"body":290,"categories":488,"date":490,"description":491,"extension":276,"featuredImage":277,"mainImage":492,"meta":494,"navigation":281,"path":495,"previewImage":496,"seo":497,"stem":498,"tags":277,"__hash__":499},"blog/blog/the-axure-community-on-leveraging-notes-in-axure-rp.md","The Axure Community on Leveraging Notes in Axure RP",{"type":10,"value":291,"toc":478},[292,301,305,313,322,326,338,341,357,361,372,388,392,395,398,402,405,409,418,421,425,464,468,471],[18,293,294,295,300],{},"The Notes feature in Axure RP is an easy way to document and communicate the intent and functionality of your designs. This can be especially useful as the developers are implementing the solution or when QA is writing test scripts based on the design. However, we've found that the ability to add notes to pages and widgets has served a wider range of uses for ourselves and for customers -- from defining project goals to jotting down a quick to-do list. This article outlines several examples for how you can make use of notes in Axure RP, along with some best practices. (For a quick primer on notes, read our articles on ",[21,296,299],{"href":297,"rel":298},"https://docs.axure.com/axure-rp/reference/page-widget-notes/#docsNav",[25],"Page Notes"," and Widget Notes.)",[13,302,304],{"id":303},"define-stakeholder-groups","Define Stakeholder Groups",[18,306,307,308,312],{},"Page notes and widget notes can each be separated into multiple fields. The fields created for page notes will be available for all pages. Similarly, widget notes fields are available for all widgets. One way to organize notes is by their intended audience. For example, you can separate notes for clients, developers, business analysts, copywriters, and so on. (To learn how to do this, read our ",[21,309,311],{"href":297,"rel":310},[25],"step-by-step tutorial"," for customizing page note fields.)",[18,314,315,316,321],{},"When you generate an HTML prototype for a client, for example, you can configure it to only include notes relevant to the client. You have the same flexibility to decide which notes to include when creating ",[21,317,320],{"href":318,"rel":319},"https://docs.axure.com/axure-rp/reference/word-specification/",[25],"Word documentation",". It helps to establish what types of information each team member needs and how specific that information should be at the beginning of the project. Then, create the notes fields accordingly. Separating the notes into fields can help your team create more consistent and complete documentation.",[13,323,325],{"id":324},"establish-page-goals","Establish Page Goals",[18,327,328,331,332,337],{},[38,329,330],{},"Pete Karabetis",", the Director of User Experience at ",[21,333,336],{"href":334,"rel":335},"http://www.lmo.com/",[25],"LMO Advertising",", uses page notes to establish the purpose of the screen, define use cases that need to be satisfied, and include URLs to related documents (please note that Page Notes currently do not support active links).",[18,339,340],{},"\"This helps the content creator know what kind of copy they need. It helps developers know what elements on the page needs to be created as a variable. And it helps the visual designer think about the layout and the creative elements that need to be there to support the goals,\" Karabetis said.",[18,342,343,346,347,350,351,356],{},[38,344,345],{},"Ezra Schwartz"," and ",[38,348,349],{},"Elizabeth Srail",", in their book, ",[21,352,355],{"href":353,"rel":354},"https://www.packtpub.com/web-development/prototyping-essentials-axure",[25],"Prototyping Essentials With Axure",", Second Edition (Packt Publishing) suggest a few other types of high-level information that can be relevant in page notes. Those include page entry points, actions users can take on the page, user experience principles underlying the page design, business requirements fulfilled by the page, as well as localization and personalization notes.",[13,358,360],{"id":359},"store-project-information","Store Project Information",[18,362,363,364,371],{},"For pages that go through several versions, ",[21,365,368],{"href":366,"rel":367},"https://www.linkedin.com/in/svetlindenkov",[25],[38,369,370],{},"Svetlin Denkov"," of GN ReSound creates separate notes for each version, labeling them with version number followed by date like so: \"v01 20151001\", \"v02 20151002\". Depending on the project and team size, Svetlin also uses notes to communicate:",[373,374,375,379,382,385],"ul",{},[376,377,378],"li",{},"Target release date",[376,380,381],{},"Name of the final decision maker",[376,383,384],{},"Person to whom the task is currently assigned",[376,386,387],{},"Status (in scope or out of scope, approved or not)",[13,389,391],{"id":390},"document-functional-specifications","Document Functional Specifications",[18,393,394],{},"This was the original purpose of the Notes feature. Widget notes can be used to document specifications and provide the information necessary for developers to build the solution. Determining the right amount of documentation to put in the notes depends highly on your team and your process. In a lean environment and working closely with the development team, you might choose to keep the notes as concise as possible. If your process is more waterfall, or the solution is complex, or you are working with a remote team, too little documentation can lead to a lack of clarity and alignment.",[18,396,397],{},"\"The specifications may be used by a remote team, often overseas, and the developers will interpret your words verbatim,\" Schwartz and Srail noted in their book, \"while in an agile environment, the developers might barely read anything.\"",[13,399,401],{"id":400},"create-a-to-do-list-for-yourself-or-your-team","Create a To-Do List for Yourself or Your Team",[18,403,404],{},"You can use page notes to jot down things you need to do for that page. When you return to the file, the notes serve as a quick reminder of what needs to be done for the page. If there are multiple people contributing to the file or team project, keeping a simple task list within the page notes will let you know who is taking care of which tasks. This can be particularly helpful when someone new joins the team.",[13,406,408],{"id":407},"keep-track-of-changes","Keep Track of Changes",[18,410,411,412,417],{},"Similarly, for projects with multiple cooks, you can use page notes to keep track of who changed what. Each time you make a change to a page, type in a line about what was changed so the rest of your team knows what happened. With Team Projects, you can also add a Check In Note each time you check in your changes the project. Those are notes appear in the Team Project History (shown below) and are separate from page and widget notes. (You can learn how to access the history in our ",[21,413,416],{"href":414,"rel":415},"https://docs.axure.com/axure-rp/reference/team-projects-overview/",[25],"Team Projects tutorial",".)",[18,419,420],{},"In general, use widget notes or page notes when you want to document individual changes made to a page or widget. Use Team Project notes when you want to capture a broad summary of all the changes you've made across the entire project during a single check-in. Here's a quick recap.",[13,422,424],{"id":423},"six-ways-to-leverage-notes-in-axure-rp-pro","Six Ways to Leverage Notes in Axure RP Pro",[426,427,428,434,440,446,452,458],"ol",{},[376,429,430,433],{},[38,431,432],{},"Define Stakeholder Groups."," Organize notes by their intended audience. For example, you can separate notes for clients, developers, business analysts, copywriters, and so on. When you generate an HTML Prototype, you can configure it to only include notes relevant to the audience you want to target.",[376,435,436,439],{},[38,437,438],{},"Establish Page Goals."," Use page notes to establish such things as the purpose of the page, define use cases that need to be satisfied, URLs to related documents, page entry points, actions users can take on the page, user experience principles underlying the page design, business requirements fulfilled by the page, as well as localization and personalization notes.",[376,441,442,445],{},[38,443,444],{},"Store Project Information."," You can use notes to manage projects. Examples of project information include target release date, name of the final decision maker, person to whom the task is currently assigned, version number, project or page status.",[376,447,448,451],{},[38,449,450],{},"Document Functional Specifications."," Provide the information necessary for developers to build the solution.",[376,453,454,457],{},[38,455,456],{},"Create To-Do Lists."," Jot down things you need to do for that page. When you return to the file, the notes serve as a quick reminder of what needs to be done for the page. If there are multiple people contributing to the file or team project, keeping a simple task list within the page notes will let you know know who is taking care of which tasks.",[376,459,460,463],{},[38,461,462],{},"Keep Track of Changes."," Use the Page Notes to keep track of who changed what. Each time you make a change to a page, just add a note about what was changed so the rest of your team knows what happened.",[13,465,467],{"id":466},"notes-versus-comments","Notes Versus Comments",[18,469,470],{},"Page notes and widget notes are created and managed within Axure RP. They are typically part of the documentation of the solution or notes for the authors of the design. To gather feedback or have conversations with others, you can use Axure Share's in-browser discussion and screenshot tool.",[18,472,473,474,33],{},"We hope these examples give you a few new ideas for using notes in Axure RP. Do you have other ways to leverage notes? We'd love to hear about them, either in the comments below or via email at ",[21,475,477],{"href":476},"mailto:contactus@axure.com","contactus@axure.com",{"title":260,"searchDepth":261,"depth":261,"links":479},[480,481,482,483,484,485,486,487],{"id":303,"depth":261,"text":304},{"id":324,"depth":261,"text":325},{"id":359,"depth":261,"text":360},{"id":390,"depth":261,"text":391},{"id":400,"depth":261,"text":401},{"id":407,"depth":261,"text":408},{"id":423,"depth":261,"text":424},{"id":466,"depth":261,"text":467},[349,345,330,370,489],"Tips and Tricks","2015-12-01T00:00:00.000Z","The Notes feature in Axure RP is an easy way to document and communicate the intent and functionality of your designs. This can be especially useful as the developers are implementing the solution or when QA is writing test scripts based on the design.",{"src":493},"/images/2019/04/boabpmrkls0.jpg",{},"/blog/the-axure-community-on-leveraging-notes-in-axure-rp",{"src":493},{"title":289,"description":491},"blog/the-axure-community-on-leveraging-notes-in-axure-rp","QO-6Hgijl28IEdXm6Ua7K81EE-y30MQV3qns6A7O_Rs",{"id":501,"title":502,"author":8,"body":503,"categories":677,"date":679,"description":680,"extension":276,"featuredImage":277,"mainImage":681,"meta":682,"navigation":281,"path":683,"previewImage":684,"seo":686,"stem":687,"tags":277,"__hash__":688},"blog/blog/dani-nordin-on-transitioning-a-team-from-comps-to-interactive-prototypes.md","Dani Nordin on Transitioning a Team from Comps to Interactive Prototypes",{"type":10,"value":504,"toc":666},[505,509,523,526,530,539,544,547,550,554,557,561,564,567,571,574,578,581,584,588,591,594,598,601,604,608,611,617,623,629,632,636,639],[13,506,508],{"id":507},"introduction","Introduction",[18,510,511,512,515,516,519,520,33],{},"Change is difficult, but not changing is fatal. So goes the anthem for many a business leader looking to innovate and stay ahead of the curve. ",[38,513,514],{},"Dani Nordin",", UX Director at ",[38,517,518],{},"Pegasystems"," and author of several O'Reilly design books, shares her recent experience in introducing change at one of the world's most venerable corporate brands, the ",[38,521,522],{},"Harvard Business Review",[18,524,525],{},"Her mission: transition a design team from static mockups for large screens to interactive mobile-first prototypes with Axure. Easier said than done, it turns out. In this case study, Dani candidly outlines her missteps and successes, offering hard-won lessons and insights from her experience.",[13,527,529],{"id":528},"the-project","The Project",[18,531,532,533,538],{},"During the fall of 2014, ",[21,534,537],{"href":535,"rel":536},"https://hbr.org/",[25],"HBR.org"," launched a major responsive redesign after months of intense effort. I was hired shortly after launch to help the business \"live into\" the desire to take a more human-centered approach to its design and development process.",[64,540,541],{},[18,542,543],{},"Being able to create interactive prototypes gave developers and other stakeholders more immediate transparency into the intended behavior of our designs, while also providing a single link—through the Axure Share prototype—that could remain constant throughout the project.",[18,545,546],{},"During my first several weeks, I noticed a disconnect between the way the design team created documentation for the development team and the way the development team built things. In order to iterate designs more efficiently using their established workflow, static comps were created in Photoshop or Illustrator. Unfortunately, short timelines and an impression among the design team that stakeholders couldn't \"think in mobile\" meant that the majority of design work was focused on the larger screen experience and presented in static comps. As a result, the front-end team implementing the designs was left to interpret how the designs would adapt to smaller screens. The resulting experience was inconsistent across devices, and members across the team were frustrated by the communication breakdowns that resulted.",[18,548,549],{},"As I reviewed our current process and made recommendations for how to incorporate UX into our workflow, one of my key recommendations was to shift from static comps to interactive, adaptive Axure prototypes. The resulting work would allow us to think about how our designs would adapt to different devices and screen sizes, rather than treating \"desktop\" and \"mobile\" as distinct environments. In addition, being able to create interactive prototypes gave developers and other stakeholders more immediate transparency into the intended behavior of our designs, while also providing a single link—through the Axure Share prototype—that could remain constant throughout the project, rather than having to continually upload new versions of a static document.",[13,551,553],{"id":552},"meet-the-team","Meet the Team",[18,555,556],{},"As Senior UX Designer and resident Axure expert, I led the charge in bringing Axure into the design team. My mission included getting our two interactive designers up to speed on using use Axure, and helping the team strategize how to incorporate prototyping into our workflow without losing the momentum of projects. Our respective bosses provided support and mentoring through the journey.",[13,558,560],{"id":559},"getting-started","Getting Started",[18,562,563],{},"There were two big steps involved in bringing Axure to HBR. The first step was getting leadership in Design and Product on board with the transition. By showing the advantages of prototypes, both in clarity and in responsiveness, we were able to get sufficient buy-in to send the designers to training on how to use the tool.",[18,565,566],{},"The second big step was to show the Design team how prototypes could be used on a project. We did this for two big projects: the first was a redesign of the Webinar section of the website, which focused initially on the large-screen experience with no Adaptive Views. The second and most significant project was a redesign of My Library, a set of internal features that readers get when they create an account on the site. This was our first experience with truly adaptive prototypes, Team Projects, and attempting to bring a higher level of visual fidelity to our prototypes.",[13,568,570],{"id":569},"first-speed-bump","First Speed Bump",[18,572,573],{},"In both projects, the tech team and stakeholders saw an immediate benefit to the interactive prototypes. Iteration was fast, and didn't require uploading new screenshots; the intended behavior was easier to see in a prototype than in a static comp.",[64,575,576],{},[18,577,573],{},[18,579,580],{},"The Design team, however, was not sold on the concept. While the prototypes were intended as medium-fidelity documentation that could quickly be implemented using existing design patterns, the Design team needed to see a higher level of visual fidelity to feel confident in the design direction. As a result, they created separate, static comps to represent their intended \"final\" design and added them to the tickets for implementation.",[18,582,583],{},"This duplication of effort was particularly problematic during the redesign of My Library, where entire sections of functionality were created as a static, annotated PDF by the Design team, independent of the prototype, while the prototype showed an entirely different interaction pattern. This caused confusion and frustration in the development team, who couldn't tell what they should be referencing for what to build. It also caused some internal conflict between the Design and Product/UX teams, who struggled to determine who \"owned\" the prototyping and UX process.",[13,585,587],{"id":586},"second-third-speed-bumps","Second & Third Speed Bumps",[18,589,590],{},"As we reflected on the challenges of the My Library project, we uncovered some important frustrations among the members of the team. Designers liked working with Axure, but found the learning curve frustrating. As a result, they hesitated to think of it as a design tool, and felt that the additional static comps were needed to ensure the level of visual fidelity they were going for. This frustrated Product/UX, who felt that Axure could readily help the design team achieve their visual fidelity goals, and were concerned that continuing to duplicate efforts would derail our goal to make interactive prototyping a key part of our UX process.",[18,592,593],{},"Further complicating matters was a growing tension between the lead designer and myself. Throughout the redesign of HBR.org, the Lead Digital Designer served as the team's UX designer; my arrival at the company signaled a big change in her role, and my involvement in changing the design of the site, something that had long been under Design's control, was deeply uncomfortable. By not involving her and the other interactive designer in the process earlier, I had inadvertently made things much worse, making it seem that I didn't value the role that the Design team played in improving the website.",[13,595,597],{"id":596},"outcome","Outcome",[18,599,600],{},"After several weeks of discussion and a bit of trial and error, we've come a long way towards a primarily Axure-based workflow. As the designers' experience with Axure has grown, they've gotten more confident in creating higher-fidelity prototypes that can serve as primary design documentation for stakeholders and the tech team. For a redesign of our primary navigation, the designers did \"sketches\" of the intended design in Illustrator, and worked together to put those designs into Axure—at full visual fidelity—for testing and documentation. For our latest project, an upgrade to the video experience on the site, the designers are working together in Axure from start to finish, iterating from medium-to-high fidelity as feedback is collected. Meanwhile, I've shifted my role to one that is focused more on advising and guiding the UX, providing workflows and design research to support the Design team's decision-making.",[18,602,603],{},"As the process continues to evolve, the team is starting to incorporate a mobile-first approach earlier in the design process, and to more effectively use annotations to support the developers as they implement designs. The Design team is also actively working with the tech team to shift their expectations away from static comps towards interactive prototypes, as a way to make the process more efficient. The effort to move towards an Axure-based workflow has paid significant dividends in the improvement to overall design and interaction within the site. During the redesign of the navigation, the Design team was able to envision and get stakeholder buy-in on the complete experience, rather than asking them to imagine how a design would adapt to different screen sizes. For key interactions within My Library, we were able to demonstrate complete interactions for the tech team, helping them understand intended behavior as well as visual design.",[13,605,607],{"id":606},"lessons-learned","Lessons Learned",[18,609,610],{},"Looking back on this experience, there were three major takeaways:",[18,612,613,616],{},[38,614,615],{},"People build up expertise with a particular toolkit over time, and getting them to switch to something else is disruptive and uncomfortable."," Being empathetic to what your team members are going through, and providing support and coaching during their learning process, is essential for helping them make the transition.",[18,618,619,622],{},[38,620,621],{},"Learn and build on each other's strengths."," Some of my biggest mistakes during this process came from not taking more time to appreciate Design's role and mission in making the site better. Once we were able to understand each other better, I leaned back a bit and let them take on more of the prototyping work, while advising on interaction and user behavior.",[18,624,625,628],{},[38,626,627],{},"Remember that it's a process."," When working in an Agile environment, it's easy to get caught up in \"fast, fast, iterate, fast!\" But learning a new tool, and a new way of working, takes time, and generally involves a lot of bumps in the road. Taking time now and again to reflect on how you've progressed goes a long way towards making things stick in the long run.",[630,631],"hr",{},[13,633,635],{"id":634},"about-dani-nordin","About Dani Nordin",[18,637,638],{},"During her 10 months as Senior UX Designer at Harvard Business Review, Dani Nordin helped introduce key user-centered design practices to the organization, including usability testing, shared design principles, Axure prototyping and interaction design, and cross-functional collaboration between UX, Design and Front-End Development. Her tenure saw significant improvements to the usability and usefulness of HBR.org's account features, navigation and key interaction flows such as registration and checkout.",[18,640,641,642,647,648,653,654,659,660,665],{},"Dani is now the Director of UX in the Digital Engagement Group at Pegasystems, supporting both Pega.com and the Pega Developer Network. She is the author of several books for O'Reilly, including ",[21,643,646],{"href":644,"rel":645},"http://shop.oreilly.com/product/0636920024873.do",[25],"Drupal for Designers",", ",[21,649,652],{"href":650,"rel":651},"http://shop.oreilly.com/product/0636920020264.do",[25],"Planning and Managing Drupal Projects",", and ",[21,655,658],{"href":656,"rel":657},"http://shop.oreilly.com/product/0636920020301.do",[25],"Drupal Development Tricks for Designers",". She is also the author and presenter of two O'Reilly video series, ",[21,661,664],{"href":662,"rel":663},"http://shop.oreilly.com/product/0636920040170.do",[25],"Learning UX Fundamentals"," (2015) and Designing with Empathy (forthcoming in 2016).",{"title":260,"searchDepth":261,"depth":261,"links":667},[668,669,670,671,672,673,674,675,676],{"id":507,"depth":261,"text":508},{"id":528,"depth":261,"text":529},{"id":552,"depth":261,"text":553},{"id":559,"depth":261,"text":560},{"id":569,"depth":261,"text":570},{"id":586,"depth":261,"text":587},{"id":596,"depth":261,"text":597},{"id":606,"depth":261,"text":607},{"id":634,"depth":261,"text":635},[514,522,678,518,273],"HBR","2015-10-27T00:00:00.000Z","Change is difficult, but not changing is fatal. So goes the anthem for many a business leader looking to innovate and stay ahead of the curve. Dani Nordin, UX Director at Pegasystems and author of several O'Reilly design books, shares her recent experience in introducing change at one of the world's most venerable corporate brands, the Harvard Business Review.",{"src":277},{},"/blog/dani-nordin-on-transitioning-a-team-from-comps-to-interactive-prototypes",{"src":685},"/images/2019/04/magpyhro0aa.jpg",{"title":502,"description":680},"blog/dani-nordin-on-transitioning-a-team-from-comps-to-interactive-prototypes","6CAk2cY8NMyOUBC-XhGWblbMJrRrXD_QFwlEO-Y1puE",{"id":690,"title":691,"author":8,"body":692,"categories":798,"date":799,"description":800,"extension":276,"featuredImage":277,"mainImage":801,"meta":802,"navigation":281,"path":803,"previewImage":804,"seo":806,"stem":807,"tags":277,"__hash__":808},"blog/blog/jeff-harrison-of-evantage-on-how-to-future-proof-your-prototypes.md","Jeff Harrison of Evantage on How to Future-Proof Your Prototypes",{"type":10,"value":693,"toc":796},[694,697,700,715,718,723,726,729,732,737,740,745,748,753,756,761,764,769,772,777,780,785,788,793],[18,695,696],{},"You pour blood, sweat and tears into a prototype. You spend hours thoughtfully crafting every nuance of the experience. You present it, like a proud parent. Then your boss, or client, requests \"just one small change.\" No problem, except making that change requires you to rip apart your entire prototype.",[18,698,699],{},"What to do?",[18,701,702,703,708,709,714],{},"We talked with ",[21,704,707],{"href":705,"rel":706},"https://www.linkedin.com/in/mrjeffharrison/en",[25],"Jeff Harrison",", a user experience consultant with ",[21,710,713],{"href":711,"rel":712},"http://evantageconsulting.com/our-team/",[25],"Evantage Consulting"," and an Axure Fu Master, about this particular problem. His prescription: an ounce of prevention.",[18,716,717],{},"Okay, so this common sense advice doesn't help when you've already built your prototype and are in the throes of reworking it. Next time, however, Jeff has a few recommendations for ways to think about prototyping in a way that anticipates changes, or at least make them easier to pull off without pulling out your hair. For some sage advice, read our edited Q&A with Jeff.",[18,719,720],{},[38,721,722],{},"Q: Here's a serving of irony. You built this crazy puzzle to demonstrate that simplicity is often best. How exactly does it show that?",[18,724,725],{},"Jeff: This was actually the second version of the puzzle. I made the first version in 2009 to demonstrate how you can break a huge interaction into manageable parts. That puzzle used a giant control function that kept track of every square. Every time you clicked, it went through a lengthy calculation to figure out where the squares should move.",[18,727,728],{},"In this version, the location of the hole is known, the location of the clicked square is captured, and every tile knows where it is. When you click, every tile has to figure out for itself whether it's between the clicked tile and the hole, and if it is, it moves. That's it. Since the logic is built into each tile, it makes it easy to expand the puzzle to a 6x6 or 7x7 grid.",[18,730,731],{},"The point was cohesion -- everything the component does should be logically connected. If you do that, you can avoid making logical spaghetti. I've produced a lot of logical spaghetti in my time.",[18,733,734],{},[38,735,736],{},"Q: So Rule No. 1 in Jeff's Laws for Fireproofing Your Interactions is cohesion.",[18,738,739],{},"Jeff: I suppose. (He chuckles.) It's a matter of building interactions that can withstand stress.",[18,741,742],{},[38,743,744],{},"Q: I still have a head-pretzel from looking at how you built this puzzle. Are all your prototypes this insane?",[18,746,747],{},"Jeff: The puzzle was just for a little shock and awe. Most of my prototypes are very pedestrian and boring, actually. Many of them look plain and do only one simple thing. I'm a firm believer that if you have three different kinds of questions to answer, you should consider three simple prototypes. Unless those questions are inextricably linked, trying to come up with a single prototype that has everything in it isn't going to help you answer those questions.",[18,749,750],{},[38,751,752],{},"Q: So, Rule No. 2 is make one prototype per question for user testing.",[18,754,755],{},"Jeff: Right. When I think about a prototype, I see two reasons why you would make one. One, it can communicate a design better than words. Two, it helps you answer some kind of question.",[18,757,758],{},[38,759,760],{},"Q: In your experience, what types of prototypes work best in user testing?",[18,762,763],{},"Jeff: With user testing, you need simple prototypes that are focused on the test. Otherwise, people can get distracted and give you feedback about the wrong thing.",[18,765,766],{},[38,767,768],{},"Q: Give us an example.",[18,770,771],{},"Jeff: High-fidelity prototypes. A lot of people want their prototypes to reflect every nuance and every pixel of the product. But high-fidelity takes more work and time. If things change, it also takes more time to maintain. You also risk eliciting reactions that aren't useful. A classic example is when testing how people flow through your product. With high-fidelity prototypes, people can spend all their time talking about the color, the presentation or the breadth of functionality -- anything but the flow.",[18,773,774],{},[38,775,776],{},"Q: Okay, lay down another law for us.",[18,778,779],{},"Jeff: Sure. The more simply you can model something, the easier it will be for you to modify it. For example, avoid nesting one dynamic panel inside of another one -- if you can. Nesting dynamic panels makes your interactions more complicated, and changing one variable value can involve digging through multiple panels. Build interactions that make it easy for you, the prototyper, to change things down the road.",[18,781,782],{},[38,783,784],{},"Q: Now we have Rule No. 3: Avoid nesting dynamic panels. How about a fourth?",[18,786,787],{},"Jeff: Uncouple your interactions from your pages. Instead of using OnPageLoad to configure everything on your page, embed the logic into your components so they can configure themselves. Make self-contained masters. That way, if you cut and paste widgets, you won't break your interactions. This is a concept borrowed from object-oriented programming, but it's generalizable.",[18,789,790],{},[38,791,792],{},"Q: But object oriented UX advocates for a lot of nesting of masters within masters to create those self-contained objects. Doesn't that violate Rule No. 3?",[18,794,795],{},"Jeff: Sometimes, you will find yourself in situations where nesting is best option. I know saying this does jeopardize my status as a lawgiver, doesn't it? Maybe Rule No. 5 is that there will always be exceptions.",{"title":260,"searchDepth":261,"depth":261,"links":797},[],[489,273],"2015-07-01T00:00:00.000Z","You pour blood, sweat and tears into a prototype. You spend hours thoughtfully crafting every nuance of the experience. You present it, like a proud parent. Then your boss, or client, requests 'just one small change.' No problem, except making that change requires you to rip apart your entire prototype.",{"src":277},{},"/blog/jeff-harrison-of-evantage-on-how-to-future-proof-your-prototypes",{"src":805},"/images/2016/12/Jeff-Harrison.jpg",{"title":691,"description":800},"blog/jeff-harrison-of-evantage-on-how-to-future-proof-your-prototypes","mytT14mbqlzDLgIz_haI8yNv-PGU2j-hLm7Bgmzm3yY",{"id":810,"title":811,"author":8,"body":812,"categories":876,"date":880,"description":881,"extension":276,"featuredImage":277,"mainImage":882,"meta":883,"navigation":281,"path":884,"previewImage":885,"seo":887,"stem":888,"tags":277,"__hash__":889},"blog/blog/sap-releases-fiori-widgets-for-axure-rp.md","SAP Releases Fiori Widgets for Axure RP",{"type":10,"value":813,"toc":874},[814,835,869],[18,815,816,817,822,823,828,829,834],{},"SAP released a ",[21,818,821],{"href":819,"rel":820},"https://experience.sap.com/fiori-design/resources/downloads/",[25],"new Fiori widget library"," for Axure RP and is making the switch from PowerPoint. The change coincided with the release this month of the Fiori Design Guidelines Version 1.28. For those unfamiliar with Fiori, it is a set of user experience ",[21,824,827],{"href":825,"rel":826},"https://experience.sap.com/fiori-design/foundation/design-principles/",[25],"design principles"," developed by SAP to build business software that is simple, consistent, responsive, role-based and delightful. Kai Richter, the company’s Director of UI Concepts and Guidelines, wrote an in-depth article about SAP’s experience in using Axure. Among SAP's reasons for switching, he cited, \"First and foremost, Axure allows us to create interactive prototypes that can be used for usability testing. The scripting and animation capabilities are sufficient to create click-through mockups that can cover complex business scenarios.\" Here’s an excerpt of “lessons learned,” reprinted with his permission, from the article, which you can ",[21,830,833],{"href":831,"rel":832},"http://scn.sap.com/people/kai.richter/blog/2015/06/08/prototyping-fiori-applications",[25],"read in full on SAP’s blog",":",[64,836,837,843],{},[18,838,839],{},[840,841,842],"em",{},"As our new stencils are now being used by application designers internally, we can already report some first lessons learned:",[373,844,845,853,861],{},[376,846,847],{},[840,848,849,852],{},[38,850,851],{},"The overall quality of the mockups"," that are being shown in review sessions has dramatically increased - fidelity and attention to detail is much better than before. It is clear very early on what controls are being used and how implementation can be achieved.",[376,854,855],{},[840,856,857,860],{},[38,858,859],{},"Training efforts were limited."," Most designers were able to get started after a short introduction. The material available from the provider is also a valuable source.",[376,862,863],{},[840,864,865,868],{},[38,866,867],{},"The interactivity features are being used by the designers."," The applications become more tangible for the development teams very early in the process so that uncertainties in the interactivity can be clarified early in the process. We have created a community space where designers exchange their designs and stencils so that good solutions can be leveraged by colleagues.",[18,870,871,872,33],{},"Richter noted on his post that Axure is not as ubiquitous as Microsoft PowerPoint. \"This excludes most of the business experts who before that could easily modify or sketch prototypes using Microsoft Powerpoint,\" he said. As an alternative, his group is exploring the option of offering simplified page-level stencils for users who have PowerPoint but not Axure. Overall, Richter concluded that his group’s transition to a \"professional design tool\" has led to \"improvements in design quality.\" Do you have a story you’d like to share? We’d love to hear about it! Send an email to ",[21,873,477],{"href":476},{"title":260,"searchDepth":261,"depth":261,"links":875},[],[877,878,273,879],"Fiori","SAP","What's New","2015-06-15T00:00:00.000Z","SAP released a new Fiori widget library for Axure RP and is making the switch from PowerPoint. The change coincided with the release this month of the Fiori Design Guidelines Version 1.28.",{"src":277},{},"/blog/sap-releases-fiori-widgets-for-axure-rp",{"src":886},"/images/2017/01/Designing-SAP-Fiori-.png",{"title":811,"description":881},"blog/sap-releases-fiori-widgets-for-axure-rp","gMJUmvazv48rf3rUqzJwMqX_be31hD9Dwe_bHCbZJI4",{"id":891,"title":892,"author":8,"body":893,"categories":1062,"date":1063,"description":1064,"extension":276,"featuredImage":277,"mainImage":1065,"meta":1066,"navigation":281,"path":1067,"previewImage":1068,"seo":1070,"stem":1071,"tags":277,"__hash__":1072},"blog/blog/tips-for-organizing-awesome-axure-meetups.md","Tips for Organizing Awesome (Axure) Meetups",{"type":10,"value":894,"toc":1040},[895,898,902,911,915,920,929,933,936,939,943,947,950,954,963,967,970,974,977,981,984,987,991,1000,1004,1007,1011,1014,1018,1021,1025,1028,1032],[18,896,897],{},"Meetups are a great way to network, learn new tricks and polish your presentation skills. And if you live in Chicago, London, Los Angeles, San Diego, San Francisco or Richmond, Va., you're in luck. Those cities already have Axure Meetups you can attend. But what if you don't live in those cities? You can organize your own Axure Meetup. It takes a bit of work, but to get you going, we interviewed several top organizers to share their best tips and tricks for putting together an awesome and rewarding Meetup Group.",[13,899,901],{"id":900},"why-go-to-all-the-trouble","Why go to all the trouble?",[18,903,904,905,910],{},"Sandra Gonzales, the ",[21,906,909],{"href":907,"rel":908},"http://www.meetup.com/Axure-London-Meetup/",[25],"London Axure Meetup"," Organizer, gets this question a lot. Sandra says she has gotten job offers, invitations to speak and a reputation as a user experience design expert. But those were just the side effects. The real reason Sandra started an Axure Meetup was that she wanted to meet like-minded people, share her knowledge and learn from others.",[13,912,914],{"id":913},"how-do-i-score-a-venue","How do I score a venue?",[916,917,919],"h3",{"id":918},"start-small","Start small",[18,921,922,923,928],{},"If you're just aiming for a casual social mixer, a local cafe or bar is a good choice. If you need a quieter space, try the local library. That's where Stefani Sandow, the ",[21,924,927],{"href":925,"rel":926},"http://www.meetup.com/Axure-Users-Meetup-Chicago/",[25],"Chicago Axure Meetup"," Organizer, chose to locate her first Axure Meetup two years ago.",[916,930,932],{"id":931},"ask-your-employer-or-a-local-agency","Ask your employer or a local agency",[18,934,935],{},"When Stefani got more RSVP's than the library could accommodate, her co-organizer Adam Bitner asked his employer if they could use the company's conference rooms. The company, a digital ad agency, happily agreed. That's because many agencies see Axure Meetups as a chance to recruit designers and spread the word about their services.",[18,937,938],{},"\"Companies know they'll get skilled and qualified interaction designers at the event,\" Adam said. Approach an agency that is hiring or is new and actively looking to establish its reputation, he advised. As your Meetup grows, companies may even vie to host your events, which is the case with Sandra's London Meetup.",[13,940,942],{"id":941},"how-do-i-get-people-to-come","How do I get people to come?",[916,944,946],{"id":945},"related-meetupcom-topics","Related Meetup.com topics",[18,948,949],{},"When you set up your Meetup page, you'll be asked to select topics that are relevant to your group. This step is critical, because once you've created your group, Meetup will promote your group to members who have subscribed to those topics. It's a great chance to get a free marketing boost.",[916,951,953],{"id":952},"event-cross-promotion","Event cross-promotion",[18,955,956,957,962],{},"Beth Wegner, organizer of the ",[21,958,961],{"href":959,"rel":960},"http://www.meetup.com/Los-Angeles-Axure-Users/",[25],"Los Angeles Axure Meetup"," Group, also suggests reaching out to related Meetup groups to help cross-promote each other's events. In L.A., Beth works with LAUX, a popular user experience group. And in Chicago, Stefani and Adam have reached out to the local IXDA Chapter to help spread the word.",[916,964,966],{"id":965},"social-media","Social Media",[18,968,969],{},"Social media is also a good way to increase awareness. \"Whenever I am at a conference or workshop, there's usually a hashtag for the event. I use the hashtag and say something like, 'Speaking of prototyping, here's a shameless plug for our Axure Meetup,' with a link\" to information on the group, said Sandra. Others use social media to remind folks to come before the event and keep the conversation going after the event.",[13,971,973],{"id":972},"what-do-i-do-at-the-event","What do I do at the event?",[18,975,976],{},"Coming up with fresh, engaging topics and activities is possibly the biggest challenge for Meetup organizers. Here are some ideas:",[916,978,980],{"id":979},"reverse-engineering","Reverse Engineering",[18,982,983],{},"Stefani and Adam came up with the idea of showing a prototype on a screen and challenging people to create it. They divided people into teams, being careful to pair up people who are new to Axure with Axure Fu Masters. This overcomes one of the recurring issues that crop up -- how to engage people along a wide spectrum of proficiency.",[18,985,986],{},"\"Axure is so versatile that there could be five or more ways to skin the cat,\" said Stefani. \"People come up with different ways to build the same thing, so we get to all learn something new.\"",[916,988,990],{"id":989},"axure-puzzles","Axure Puzzles",[18,992,993,994,999],{},"To get people thinking, Sandra built a ",[21,995,998],{"href":996,"rel":997},"http://yym59z.axshare.com/london_axure_puzzle_-_1.html",[25],"puzzle"," and sent a link to the prototype via AxShare a few days before the event. The challenge was to see if people could figure out how she built it. She used the puzzle as the focal point of the event.",[916,1001,1003],{"id":1002},"real-world-problems","Real World Problems",[18,1005,1006],{},"Ask people to come with a current issue they're struggling with. The collective brain power in the room can be put to the test!",[916,1008,1010],{"id":1009},"case-studies","Case Studies",[18,1012,1013],{},"Past projects make for great case studies. Speakers can talk about how they tackled a design challenge, the roadblocks they faced and conquered along the way and the results.",[916,1015,1017],{"id":1016},"invite-guest-speakers","Invite Guest Speakers",[18,1019,1020],{},"This helps shift the onus of having to come up with new content for every event. Authors who have just published a book on a related topic are often very willing to speak. Another source of potential speakers are local colleges and universities. Researchers who have just published papers on relevant topics can sometimes be persuaded to present their paper to the group.",[916,1022,1024],{"id":1023},"gather-ideas","Gather Ideas",[18,1026,1027],{},"The best time to get new ideas for your next event is during your current event. That's when people are most focused and interested. One way to do this is by working the room and canvassing their interests. If someone comes up with a smashing idea, don't be afraid to ask them if they can present it.",[13,1029,1031],{"id":1030},"can-axure-help","Can Axure help?",[18,1033,1034,1035,1039],{},"Yep! Just get in touch with us using the form on ",[21,1036,1038],{"href":1037},"/meetup/start","this page",". We'll help you pay the Meetup.com fees and even pick up the tab for pizza. We'll also send you a care package of swag that you can hand out at your event. Be sure to contact us three to four weeks before the event to make sure we have enough time to send you the goodies. Lastly, send us your photos or videos of the event. We'd love to hear about your experience!",{"title":260,"searchDepth":261,"depth":261,"links":1041},[1042,1043,1048,1053,1061],{"id":900,"depth":261,"text":901},{"id":913,"depth":261,"text":914,"children":1044},[1045,1047],{"id":918,"depth":1046,"text":919},3,{"id":931,"depth":1046,"text":932},{"id":941,"depth":261,"text":942,"children":1049},[1050,1051,1052],{"id":945,"depth":1046,"text":946},{"id":952,"depth":1046,"text":953},{"id":965,"depth":1046,"text":966},{"id":972,"depth":261,"text":973,"children":1054},[1055,1056,1057,1058,1059,1060],{"id":979,"depth":1046,"text":980},{"id":989,"depth":1046,"text":990},{"id":1002,"depth":1046,"text":1003},{"id":1009,"depth":1046,"text":1010},{"id":1016,"depth":1046,"text":1017},{"id":1023,"depth":1046,"text":1024},{"id":1030,"depth":261,"text":1031},[489,273],"2015-01-28T00:00:00.000Z","You can organize your own Axure Meetup. It takes a bit of work, but to get you going, we interviewed several top organizers to share their best tips and tricks for putting together an awesome and rewarding Meetup Group.",{"src":277},{},"/blog/tips-for-organizing-awesome-axure-meetups",{"src":1069},"/images/2019/05/lr5cyw3aqno.jpg",{"title":892,"description":1064},"blog/tips-for-organizing-awesome-axure-meetups","0K89AXfXc2K0W13cD4PTyqkntofK8bmTHA9xCEZvWxo",126]