What we believeabout Jira for product teams.
Lottusa is an Atlassian consulting firm for SaMD, hardware and SaaS product teams in the US, the UK and Europe, founded by Ewa Kasiak. These six beliefs decide what we set up, what we leave out, and how we work with you.
Jira
Confluence
Jira Service Management
Jira Product Discovery
RovoA Jira setup is a long series of small decisions. Who makes them, and on what basis, is what separates a tool your team trusts from one it works around. Here is the basis for ours.
- Fewer fields. More meaning.
Most Jira sites grow by accident: a status for one audit, a field for one customer, a workflow copied from another team. Each made sense once; together they hide the work. We start from the questions your team has to answer, and set up only what answers one.
In practiceEvery status, field and rule gets a one-line reason in a Confluence decision log. If nobody can write the reason, it doesn’t go in.
- Your quality lead signs, not us.
We’re not a regulatory consultancy, and we’ll never call your setup “compliant”. That judgment belongs to your quality or regulatory lead. Our job is to make their evidence easy to produce and easy to show.
In practiceWe configure Jira and Confluence around the procedures your quality lead wrote, and document the configuration so your team can validate it.
- One method, every time.
Consulting goes wrong when nobody knows what happens next. Every engagement runs on the Product Ops Flywheel: Teardown, Blueprint, Implement, Enhance and Thrive. Each stage ends with something you can see.
In practiceThe Teardown is free, and ends with recommendations across product, people, processes and tools: the gap list and a suggested way forward.
- The person you meet leads the work.
You won’t be sold by one person and handed to another. Ewa leads every engagement, and brings in the Atlassian experts your flow needs, for Jira Service Management, Jira Product Discovery or Rovo, when it needs them.
In practiceYour review call is with Ewa, the person who will lead your project.
- Cloud only, on purpose.
Atlassian Cloud is where Jira Product Discovery, Rovo and the newest automation live, and it changes every month. We’d rather know Cloud deeply than half-know three platforms.
In practiceNo Server or Data Center work. Every setup is planned for how Cloud keeps changing, with a quarterly health review in the Thrive stage.
- We build what we keep needing.
When we set up the same thing for the third time, it’s a sign Jira is missing something. So we build it as an app, and every team can use it, not only our clients.
In practiceGatecast for Jira puts hardware milestones, builds and parts on one timeline. It grew out of a setup hardware teams kept needing.
Ewa Kasiak, founder
Ewa has designed and implemented Jira, Jira Service Management and Confluence since 2015, building on more than 20 years of software delivery and product development. As an Agile transformation coach, she ran Scrum, Kanban and SAFe delivery for multi-team product organizations at Lufthansa Systems and Hapag-Lloyd, and she has led Atlassian work for Deutsche Börse Group and Johnson & Johnson. She models the whole development lifecycle in Jira, from discovery and requirements to testing and release. She co-created two Atlassian Marketplace apps and is an Atlassian Community Champion and co-organizer of ACE Gdańsk, Poland.
Book a review call with Ewa →Where we work
Remote-first, in hours that overlap with US and European time zones.
- United States
- United Kingdom
- Ireland
- Germany
- Netherlands
- Switzerland
- Austria
What clients say
“Most importantly, she understands the human element—which is critical when implementing operational systems that teams actually need to adopt and use.”
Stop rebuilding the truth before every review.
Bring the Jira you have, or the question you’re tired of answering by hand. In 45 minutes with Ewa, you’ll see where your flow breaks and what to fix first.
Book a review callFree · 45 minutes · on Google Meet