I design, automate and run Jira, Confluence, JSM and Asana, from 25-person teams to instances with more than 25,000 users. My specialty is automated access management with Entra ID, Okta and Active Directory, and I build custom Forge apps when nothing off the shelf fits.
Teams I've equipped on Jira, Confluence, JSM and Asana
Every new joiner, mover and leaver waits on an admin. Nobody knows who still needs a licence.
Schemes, custom fields and workflows multiplied team by team until reporting stopped making sense.
Deadlines, approvals and hand-offs live in files and email threads, chased one reminder at a time.
Engineering lives in Jira, business teams love Asana. I make both work, and I automate everything people do by hand twice.
Access requests go through a self-service portal, get approved by the right owner and are provisioned through your identity provider in Jira, Confluence, JSM and Asana. Leavers lose access the same way.
Approvals, hand-offs, reminders and reporting that run on their own, whatever your market. Built with Jira Automation, JMWE, Asana rules and REST APIs.
More on the blogWhen the Marketplace has nothing that fits, I build it: custom Forge apps for Jira and Confluence, from new JQL functions to dedicated features.
Schemes, workflows, fields and permissions that scale, service portals with forms and SLAs, change management with CAB, and Assets as a CMDB.
Teams of 10 to 250 moved from spreadsheets to Asana: portfolios, templates, retro-planning across countries, licence governance and the change management that makes it stick.
Agile Release Trains modelled in Jira, capacity planning in Plans, release reporting leadership can read, and Rovo and Atlassian Intelligence rolled out with guides teams actually use.
ServiceNow to JSM, regional workspaces into one Asana organisation, legacy schemes into a clean model. Planned, rehearsed and communicated so teams don't lose a day.
A selection of recent missions with engineering, IT, security and business teams. Client names stay confidential.
Separate country instances brought together into a single Asana organisation, with more than 400 people moved across.
Read the case study Agile at scale · SAFeChange management for three Agile Release Trains moving from portfolio management to agile teams in Jira.
Read the case study Planning · PortfolioCapacity scenarios and the roadmap moved out of spreadsheets into a live Advanced Roadmaps (Plans) view.
Read the case study IT service managementA risk-scoring model and CAB governance designed in Jira Service Management, documented end to end in Confluence.
Read the case study eCommerce · Release managementAn automation framework for eCommerce delivery teams: release tracking, dashboards and automated release emails.
Read the case study Marketing · Multi-countryDigital transformation for marketing teams following retro-planning across several countries.
Read the case studyYou work with me directly. The person who scopes the work is the person who builds it.
Configuration, automation rules, documentation and Forge apps live in your tenant, not in a black box.
If people do it by hand twice, I look for a rule, a script or an app that does it for them.
Every delivery ships with Confluence documentation, user guides and a communication plan.
Atlassian Certified Professional in Jira Administration (ACP-120) and Managing Jira Projects (ACP-620).
Start with a fixed-scope project, then keep me on for a set number of days per month. [Adjust to your offer]
I'm an independent Atlassian and Asana consultant based near Paris, and the founder of HANI Consulting. My work runs from 25-person teams to instances with more than 25,000 users, and I have set up over 400 Software, Business and ITSM projects.
Today I lead the Atlassian platform for the Europe & Middle East organisation of a global retailer, across Jira, Confluence, JSM and Asana. I care about platforms people actually adopt: a clear model behind every project, automation that removes repetitive work, documentation teams can follow, and Forge apps when nothing off the shelf fits.
“Merging our Asana instances meant moving more than 400 people without stopping the work. Joseph mapped every team and project, planned the switch in waves, and made sure everyone knew what would change for them. We now have one Asana and, for the first time, one view of our work.”
“Moving three trains and more than 600 people from portfolio management to agile teams is a people project before it's a Jira project. Joseph handled both: a clear model in Jira and a change plan teams actually followed, train by train.”
“Our capacity planning lived in an Excel file nobody fully trusted. Joseph moved it, and our roadmap, into a live view in Jira Plans. Planning sessions now start from real data instead of last week's spreadsheet.”
“Each platform released on its own rhythm, and stakeholders kept asking what had shipped and when. Joseph built one release framework in Jira: tracking across platforms, live dashboards and release emails that go out automatically. Nobody compiles a release report by hand any more.”
“Joseph redesigned our change process in Jira Service Management, from risk scoring to CAB approvals, and documented it so clearly that new team members learn it from the Confluence pages alone.”
A practical way to decide which tool fits your team, and when the right answer is using both, well.
The difference between Jira automation that holds up in production and automation that pages you at 2 a.m. — five JMWE patterns worth standardising on.
A Jira admin's Monday, before and after Rovo. What Atlassian's AI layer actually is — search, chat, agents — and the real cost of waiting to learn it.
Yes, that is often where I start. An audit of schemes, fields, filters, automations and licences becomes a clean-up plan ranked by risk and effort, so you see quick wins early.
Microsoft Entra ID, Okta and on-premise Active Directory. Access is driven by groups synced from your identity provider, so joiners, movers and leavers are handled without manual steps.
No. Engineering often lives in Jira and business teams in Asana. I help decide which work belongs where and how access and licences are governed on both sides.
Yes. I develop Forge apps on demand, from custom JQL functions to dedicated features for your processes, and they run inside your own Atlassian cloud.
Either a fixed-scope project, such as a migration, a JSM portal or a licence audit, or an ongoing platform-lead role. [Your day rate / minimum engagement]
Tell me what slows your teams down. You'll get an honest read on what to fix first, and what can run on its own.
A few sentences on your team, your tools and what you'd like to improve. I reply within two working days.