Anna Ślusarczyk
GFT Polska, Lead Business Analyst
Kraków, Poland
Actions
I’m an experienced Lead Consultant and Core Banking Solution Expert with a strong focus on core banking systems. Throughout my career, I’ve worked with production systems and ERP solutions, developing a deep understanding of both business and technical perspectives.
I’m passionate about connecting people, processes, and technology to create meaningful change. I believe that empathy and curiosity are among the most important skills an analyst can have — they help me truly understand user needs, build trust, and ask the right questions.
Area of Expertise
Topics
Great Experiences Die in Architecture
To understand their customers, organisations can expend a lot of time, energy and money. This is to define business needs and design appropriate architecture. During this process the original vision for the customer can be lost. What happens to make this so? Tangible, human needs become lost in corporate abstraction. The need becomes a journey. This is reconciled with business rules and translated into requirements and product decisions. In turn, these change into systems and constraints. All along this process the information in the language of customer needs, the contexts and assumptions are lost.
In this proposed session, we will see how a problem is seen through three perspectives. The sample case is that of granting access. From the customer, the request is simply wanting to share access to resource: “I´d like my partner to access this”. But this simplicity collides with the business logic of roles, consent and liability. In systems terms, access means identity, permissions and synchronisation. The session draws from connected IoT products and banking. We look at what three logics show, hide and how the differences turn into misunderstandings when teams model reality in conflicting ways.
We will present an approach that explains how to keep customer experiences, business logic and systems thinking aligned across the internal borders of organisations. We do this without adding more documentation.
Using a short exercise, participants can see the speed at which one view can quickly be re-interpreted and how early sharing of perspectives lead to better organisational and architectural decisions.
You’ll gain a) a way to see where intent gets lost between customer, business and system, b) a simple template to trace a customer need all the way to architecture decisions and c) questions to check you’re still solving the original problem
This approach can help ensure that by the time we talk about architecture, we should still be solving the problem we started with.
Tags:
# Interactive Talk | #Communicating Architecture | #Culture Clashes | #The Learning Organisation | #Participative Decision-Making
Who Will Build the Next Senior? Experience, Systems Thinking and Business Analysis in the Age of AI
Generative AI is transforming the way Business Analysts work. Requirements, backlogs, workshop summaries, and documentation can now be produced in minutes. As operational work becomes increasingly automated, it raises a different and more fundamental question:
How do we build the next generation of senior Business Analysts?
For years, seniority has been developed through experience gained across projects, products, and business domains. It is this experience that shapes business understanding, systems thinking, professional judgement, and the ability to recognize consequences beyond the boundaries of a single product or team.
If AI changes the way analysts gain experience, does it also change the path to seniority?
This interactive session invites the audience to explore that question together. Through real project stories, practical examples, and live discussion, we'll challenge some of the assumptions we make about seniority today. We'll discuss whether AI changes the value of experienced analysts, what competencies will matter most in the future, and how we can continue developing professionals who understand not only requirements, but the systems, decisions, and consequences behind them.
Because perhaps the biggest question isn't whether AI will replace Business Analysts.
It's whether we know how to build the next senior.
No Users, No Use: How We Designed a Failure
The project team was aligned. Requirements were approved. The solution was ready for testing. And then—it all fell apart. This is a true story of a project where the complete absence of end-user involvement led to a dramatic clash between what stakeholders thought the process looked like and what actually happened on the ground. Testing revealed a complete mismatch: the designed solution didn’t fit the real process, because no one had ever validated it with those who actually do the work. The project never made it to production. Instead, we had to start over—remapping the process, involving actual users, and uncovering their real needs. This talk is about a costly mistake—and how to avoid it by putting real users at the heart of business analysis.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top