Gregory Kneller
Ai Solution Architect @Jirbis Gmbh
Signup · Get unlimited contacts
WORK HISTORY
Ai Solution Architect @Jirbis Gmbh
Stuttgart, DE
AI readiness & feasibility assessments• AI-supported workflow and decision system design• Responsible AI, governance, and risk boundaries• Human-in-the-loop architectures• Executive decision support (Go / No-Go)• Governed CI/CD and deployment architectures (Harness, Protocolware)
EDUCATION
Kolmogorov School #18
Physics, Mathematics
Moscow Aviation Institute (National Research University)
Master of Engineering (MEng), Applied Math, System Programming
SKILLS
ABOUT GREGORY KNELLER
Most Jira instances are not broken.They are just no longer understandable.Over time, Jira accumulates- duplicated projects- inconsistent workflows- complex permission schemes- growing administrative overheadAt some point, it becomes difficult to maintain, hard to understand, and disconnected from the business processes it is supposed to support.This is not a tooling problem.It is an architecture problem.Most organizations try to fix this by adding more automation or introducing new workflows.That usually makes the system even harder to control — and increases the risk of breaking it further.I help organizations understand what is actually happening inside their Jira.Instead of working through the interface, I treat Jira configuration as a dataset and analyze it using a structured, question-driven approach.This makes it possible to- measure how complex the system has become- identify structural problems- detect duplication and fragmentation- define a clear and safe cleanup strategyWith 15+ years of experience in Jira architecture, workflow design, and Jira Service Management, I have worked with systems ranging from small teams to enterprise environments with thousands of users.My focus is not just cleanup, but clarity.Once the architecture becomes understandable and stable, organizations can safely introduce automation and AI-assisted workflows — with Jira acting as a reliable orchestration layer instead of a source of operational friction.If your Jira is becoming difficult to maintain or no longer reflects how your organization actually works, it is usually a sign of accumulated configuration debt.I turn that into a system you can understand, control, and evolve.If this sounds familiar, we can take a closer look at your Jira.
This profile is compiled from publicly available professional sources. Unifers is not affiliated with or endorsed by LinkedIn. Request removal of this profile.