JMP's first wall-topsy: Help us test the interactive wall process for DiscoveryThis week at Discovery, we are planning to do the same interactive wall scenario where customers share how they are using the various capabilities within the Analytic Workflow. Never a group to leave good enough alone, we asked ourselves this year, how could we overengineer this?
The answer is, of course, building a cloud application that lets us automate the data collection process, add responses to a database and then build refreshing JMP Live reports to keep the resulting data visualizations and analyses up-to-date during the event.
We are excited to release this new, fun example of an end-to-end analytic workflow to the world!
And what started as a fun activity to bring people closer together during the event with the first interactive wall in 2018 (String Wall), has continued to be improved each and every year, making this activity more interesting, finding new ways to incorporate JMP and JMP Live functionality.

As you will learn in the plenary on Tuesday, we have built a process to digitize the data from the wall via a web form. That data then pushes to a database, pulled and analyzed in JMP, then published to JMP Live reports to share with the world.
Huge thanks to Dan Valente (@Daniel_Valente), Russ Wolfinger (@russ_wolfinger), Kristen Slappey (@kristen-slappey), and Caleb King (@calking) for building out this structure and creating an awesome set of initial visualizations!
To better prepare, we are asking for internal help in testing the process and ensuring the workflow works as expected.
What we are asking from internal folks before the event:
Have an idea for how to visualize this data? Feel free to pull down the data from this JMP Live report and republish to this same space.
Thank you for your help to ensure this activity is as engaging as possible.
We need your help to build a workflow for Discovery!
JMP NewsProduct ManagementRe: JMP's first wall-topsy: Help us test the Interactive wall process for DiscoverySuper excited about this!! Can't wait to see the different ways people may come up with to visualize the data!
Re: JMP's first wall-topsy: Help us test the Interactive wall process for DiscoveryGreat idea. Maybe @martindemel your Munich weather data example could be uploaded? #actionitemformylovelysystemengineer 
Re: JMP's first wall-topsy: Help us test the Interactive wall process for DiscoveryI found the 0-10 scale confusing for answering "how frequently" I do something. Ultimately, I interpreted it as percents (0%, 10%,...,100%). I would have expected Likert scale type options "never, sometimes, often, all the time". Or maybe the 0-10 is supposed to be Likert, in which case explaining that at the top "0=never, 5=half the time, 10=all the time" might be helpful?
Re: JMP's first wall-topsy: Help us test the Interactive wall process for DiscoveryThe actual form is only filled out by JMP Staff corresponding to the stickers that the respondents put on the physical wall. Each sticker represents 4 hours. So the form corresponds to the number of stickers, which is the atomic unit of the data collection device in this case @eclaassen.
Re: JMP's first wall-topsy: Help us test the Interactive wall process for DiscoveryThanks for the explanation, @Daniel_Valente. Good luck to the data transfer-ers on keeping the data clean. 
Re: JMP's first wall-topsy: Help us test the Interactive wall process for DiscoveryThanks! Always open to other ideas for the future too. We've thought about using a camera to capture images of the responses and then send those images to the database as well to use some computer vision techniques to automate the data capture even more. Maybe next time!
Re: JMP's first wall-topsy: Help us test the Interactive wall process for Discovery@eclaassen btw, one of the current reports runs Fit Mixed to handle the repeated measures, then does two-way Hierarchical Clustering on the Industry*Category LSMeans.
Re: JMP's first wall-topsy: Help us test the interactive wall process for DiscoveryWe still have some time to add some additional reports, so if you have any good ideas, just send the JSL to me and I'll get it published.