The Domino V11 Jams Are Here
It’s hard to believe that it’s only been a year since we held our first Domino “jam.” In Warsaw, on December 5, 2017, we launched a series of workshop sessions asking for input from the Domino community, so that we could learn from you and work toward building a better product. We didn’t know then that those jams would also start a movement and reinvigorate a community that was instrumental in helping us deliver Domino V10 last month.
Well, it’s that time again. Today we announce the Domino V11 Jams, a round-the-world series of face-to-face workshops and virtual events to build and co-create an even better future Domino — with you. This time around we are starting from a very different place. We have a baseline of input from you to build upon for the next installment of the Domino roadmap to make sure it continues to be the premium rapid application-development platform. We have valued deeply your feedback in the beta forums, listened to you at the user group events and the CWP Factory Tour, and reviewed the ideas you poured into the Domino ideals portal. Thank you for all your input so far!
So why have a jam at all? Actually, it’s a bit like a jigsaw puzzle. And we believe the best way to solve it is with you, together, using design thinking — a proven way to come to better solutions, faster.
For this round of workshops, we first start with our mission for the platform. Over the next three years, our mission is for Domino to remain the premium rapid application-development platform, of which mail is an important application.
Second, we use the workshops to help validate initiatives that represent use cases that we want to improve in V11. We want to make sure to prioritize initiatives that help delight the business user, the developer, and the administrator who use the product every day. These are all important strides in the journey to deliver on our mission for Domino.
Third, in the workshops we want to specifically focus on the usage scenarios for a give role. Leveraging a design-thinking framework, we will explore outcome-based scenarios and requirements that directly relate to what matters to the business, i.e., making Domino faster, cheaper, or easier to use. We’re going to focus on 3-5 of the most important scenarios for the business user, administrator, and developer.
Lastly, we always strive to improve how we build Domino with you. That’s why each workshop has a Domino V10 retrospective built in. This is your opportunity to provide us with feedback on our last journey together. What went well? What could we improve? Let your voice be heard!
Ultimately, it’s going to be a lot of fun. If you joined us last year then you know that this is true. If you’re new to the Domino jams, find an event in a city near you and we hope to see you there!
Workshops are by invitation only and spaces are limited. Find your jam contact person here.
Disclaimer: IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.