Updated HP
This commit is contained in:
Aron August Hohmann
parent
89db801c46
commit
fdc26c9b92
2 changed files with 42 additions and 41 deletions
|
|
@ -7,34 +7,34 @@
|
|||
"footer_terms": "AGB",
|
||||
"footer_imprint": "Impressum",
|
||||
|
||||
"hero_title": "Digital Platform & Process Lead",
|
||||
"hero_subtitle": "Mit möglichst wenig das Meiste erreichen.",
|
||||
"hero_title": "Business Analyst & Solution Designer",
|
||||
"hero_subtitle": "Vom fachlichen Problem zur tragfähigen Lösung.",
|
||||
"hero_location": "Wien, Österreich",
|
||||
|
||||
"what_i_do_heading": "Was ich mache",
|
||||
"what_i_do_1_title": "Business- & System-Alignment",
|
||||
"what_i_do_1_body": "Ich übersetze fachliche Anforderungen in skalierbare Systeme und Prozesse und schaffe so die Verbindung zwischen Stakeholdern und technischen Teams.",
|
||||
"what_i_do_2_title": "Plattform- & Prozessdesign",
|
||||
"what_i_do_2_body": "Ich gestalte Workflows, Verantwortungsmodelle und Dokumentationsstrukturen, die Fehler reduzieren und mit dem Team skalieren.",
|
||||
"what_i_do_3_title": "Stakeholder-Koordination",
|
||||
"what_i_do_3_body": "Ich fungiere als Schnittstelle zwischen Fachbereichen, IT und externen Partnern, um stabile Datenflüsse und eine reibungslose Umsetzung sicherzustellen.",
|
||||
"what_i_do_4_title": "End-to-End Plattforminitiativen",
|
||||
"what_i_do_4_body": "Von der Idee bis zum Rollout — ich übernehme die Verantwortung für den gesamten Lebenszyklus von Plattformprojekten, inklusive Strategie, Umsetzung und Adoption.",
|
||||
"what_i_do_1_title": "Anforderungsanalyse & Solution Design",
|
||||
"what_i_do_1_body": "Ich erhebe und strukturiere fachliche und technische Anforderungen gemeinsam mit Stakeholdern und übersetze sie in tragfähige Lösungsarchitekturen – von der Problemdefinition bis zum High-Level-Design.",
|
||||
"what_i_do_2_title": "Business- & System-Alignment",
|
||||
"what_i_do_2_body": "Ich schaffe die Verbindung zwischen Fachbereichen und technischen Teams: Systemintegration, Datenflüsse und Architekturentscheidungen immer mit Blick auf den Business-Kontext.",
|
||||
"what_i_do_3_title": "Stakeholder-Koordination & Governance",
|
||||
"what_i_do_3_body": "Ich fungiere als Schnittstelle zwischen IT, Fachabteilungen und externen Partnern – mit klaren Dokumentationsstrukturen, Qualitätsstandards und abgestimmten Verantwortungsmodellen.",
|
||||
"what_i_do_4_title": "End-to-End Projektverantwortung",
|
||||
"what_i_do_4_body": "Von der Konzeption bis zum Rollout übernehme ich die Gesamtverantwortung für Plattform- und Integrationsprojekte – inklusive Strategie, Steuerung und nachhaltiger Adoption.",
|
||||
|
||||
"work_heading": "Ausgewählte Projekte",
|
||||
"work_1_title": "Internes PIM-System",
|
||||
"work_1_problem": "Die nativen Möglichkeiten von Magento sowie fragmentierte Prozesse zwischen Marketing, Einkauf, Produktentwicklung, Finance und Webteam führten zu Engpässen und inkonsistenten Datenstrukturen, die sich nur schwer skalieren ließen.",
|
||||
"work_1_approach": "Initiierung und Leitung der Entwicklung eines internen PIM-Systems von der Konzeption bis zum Rollout, inklusive technischer Ausrichtung, Architekturentscheidungen und Implementierungsstrategie.",
|
||||
"work_1_problem": "Fragmentierte Produktdatenprozesse zwischen Marketing, Einkauf, Produktentwicklung, Finance und Webteam führten zu Engpässen und inkonsistenten Datenstrukturen, die sich nur schwer skalieren ließen.",
|
||||
"work_1_approach": "Erhebung und Strukturierung der fachlichen Anforderungen, Design des Datenmodells (Entity-Schema, Attributstrukturen, Beziehungen) sowie Spezifikation der Datenflüsse aus heterogenen Quellen. Steuerung der Umsetzung von der Konzeption bis zum Rollout.",
|
||||
"work_1_outcome": "Optimierung der abteilungsübergreifenden Produktdatenprozesse durch ein maßgeschneidertes internes Tool – bei rund 80–90 % geringeren Kosten im Vergleich zu vergleichbaren SaaS-Lösungen.",
|
||||
|
||||
"work_2_title": "Migration der Bewertungsplattform",
|
||||
"work_2_problem": "Das Unternehmen musste seine Bewertungsinfrastruktur von Reviews.io auf Trusted Shops migrieren, was die Abstimmung mehrerer Stakeholder aus Marketing, IT und Recht erforderte.",
|
||||
"work_2_approach": "Übernahme der End-to-End-Verantwortung für die Migration – inklusive Koordination der beteiligten Teams, Steuerung des Rollout-Zeitplans sowie Sicherstellung der Daten- und Prozesskontinuität.",
|
||||
"work_2_problem": "Das Unternehmen musste seine Bewertungsinfrastruktur von Reviews.io auf Trusted Shops migrieren – mit mehreren betroffenen Stakeholdern aus Marketing, IT und Customer Support sowie harter Anforderung an Datenkontinuität.",
|
||||
"work_2_approach": "End-to-End Projektverantwortung: Anforderungsaufnahme, Koordination aller beteiligten Teams, Steuerung des Rollout-Zeitplans sowie Sicherstellung der Daten- und Prozesskontinuität während des gesamten Übergangs.",
|
||||
"work_2_outcome": "Erfolgreiche Umstellung der Plattform ohne Unterbrechung der kundenrelevanten Bewertungsprozesse.",
|
||||
|
||||
"work_3_title": "Workflow- & Prozessstandardisierung",
|
||||
"work_3_problem": "Produkt- und Content-Workflows waren uneinheitlich und stark manuell geprägt, was zu Engpässen und einer hohen Fehlerquote führte.",
|
||||
"work_3_approach": "Einführung von Task-Tracking, Dokumentationssystemen und eines TMS für Landingpage-Übersetzungen. Aufbau einer zentralen Wissensbasis für QA, Uploads und Workflows.",
|
||||
"work_3_problem": "Produkt- und Content-Workflows waren uneinheitlich und stark manuell geprägt, was zu Engpässen, hoher Fehlerquote und mangelnder Skalierbarkeit führte.",
|
||||
"work_3_approach": "Anforderungsanalyse, Einführung von Task-Tracking und Dokumentationssystemen sowie eines TMS für Landingpage-Übersetzungen. Aufbau einer zentralen Wissensbasis für QA, Uploads und Workflows.",
|
||||
"work_3_outcome": "Bis zu 90 % Effizienzsteigerung in Produktprozessen, ca. 60 % schnellere Übersetzungszyklen und rund 5 Stunden weniger organisatorischer Aufwand pro Woche.",
|
||||
|
||||
"work_label_problem": "Problem",
|
||||
|
|
@ -45,7 +45,7 @@
|
|||
"how_i_work_body": "Ich starte immer vom fachlichen Problem, nicht von der Lösung. Jedes System, jeder Prozess und jedes Tool muss sich gegenüber der Alternative rechtfertigen – nämlich nichts zu tun oder weniger zu tun. Ich priorisiere nach Impact, halte Lösungen so einfach wie möglich und stelle sicher, dass Veränderungen durch Dokumentation, klare Übergabemodelle und abgestimmte Stakeholder nachhaltig wirken.",
|
||||
|
||||
"languages_heading": "Sprachen",
|
||||
"languages_list": "Deutsch & Ungarisch — Muttersprache<br>Englisch — C2<br>Italienisch & Japanisch — A2",
|
||||
"languages_list": "Deutsch & Ungarisch — Native<br>Englisch — C2",
|
||||
|
||||
"contact_cta_heading": "Kontakt aufnehmen",
|
||||
"contact_cta_body": "Interesse an einer Zusammenarbeit?",
|
||||
|
|
|
|||
|
|
@ -1,39 +1,40 @@
|
|||
{
|
||||
"$schema": "https://inlang.com/schema/inlang-message-format",
|
||||
"back": "Back",
|
||||
"nav_about": "About me",
|
||||
"nav_contact": "Contact",
|
||||
"footer_privacy": "Privacy Policy",
|
||||
"footer_terms": "Terms of Service",
|
||||
"footer_imprint": "Legal Notice",
|
||||
"hero_title": "Digital Platform & Process Lead",
|
||||
"hero_subtitle": "Doing the most with the least.",
|
||||
"$schema": "https://inlang.com/schema/inlang-message-format",
|
||||
"back": "Back",
|
||||
"nav_about": "About me",
|
||||
"nav_contact": "Contact",
|
||||
"footer_privacy": "Privacy Policy",
|
||||
"footer_terms": "Terms of Service",
|
||||
"footer_imprint": "Legal Notice",
|
||||
|
||||
"hero_title": "Business Analyst & Solution Designer",
|
||||
"hero_subtitle": "From business problem to lasting solution.",
|
||||
"hero_location": "Vienna, Austria",
|
||||
|
||||
"what_i_do_heading": "What I Do",
|
||||
"what_i_do_1_title": "Business & Systems Alignment",
|
||||
"what_i_do_1_body": "Translating business requirements into scalable systems and processes — bridging the gap between stakeholders and technical teams.",
|
||||
"what_i_do_2_title": "Platform & Process Design",
|
||||
"what_i_do_2_body": "Designing workflows, ownership models, and documentation structures that reduce errors and scale with the team.",
|
||||
"what_i_do_3_title": "Stakeholder Coordination",
|
||||
"what_i_do_3_body": "Acting as the interface between business units, IT, and external partners to keep data flows stable and initiatives on track.",
|
||||
"what_i_do_4_title": "Platform Initiatives End-to-End",
|
||||
"what_i_do_4_body": "From concept to deployment — owning the full lifecycle of platform projects including strategy, rollout, and adoption.",
|
||||
"what_i_do_1_title": "Requirements Analysis & Solution Design",
|
||||
"what_i_do_1_body": "I gather and structure business and technical requirements together with stakeholders, translating them into viable solution architectures — from problem definition through to high-level design.",
|
||||
"what_i_do_2_title": "Business & Systems Alignment",
|
||||
"what_i_do_2_body": "I bridge the gap between business units and technical teams: system integration, data flows, and architecture decisions always grounded in business context.",
|
||||
"what_i_do_3_title": "Stakeholder Coordination & Governance",
|
||||
"what_i_do_3_body": "I act as the interface between IT, business departments, and external partners — with clear documentation structures, quality standards, and aligned ownership models.",
|
||||
"what_i_do_4_title": "End-to-End Project Ownership",
|
||||
"what_i_do_4_body": "From concept to deployment — I take full responsibility for platform and integration projects, including strategy, coordination, and lasting adoption.",
|
||||
|
||||
"work_heading": "Selected Work",
|
||||
"work_1_title": "Internal PIM System",
|
||||
"work_1_problem": "Magento's native capabilities and the fragmented workflows connecting marketing, procurement, product development, finance, and the website team created bottlenecks and data inconsistencies that were difficult to scale.",
|
||||
"work_1_approach": "Initiated and led the development of an internal PIM system from concept to deployment, owning technical direction, architecture decisions, and rollout strategy.",
|
||||
"work_1_problem": "Fragmented product data workflows across marketing, procurement, product development, finance, and the website team created bottlenecks and data inconsistencies that were difficult to scale.",
|
||||
"work_1_approach": "Gathered and structured business requirements, designed the data model (entity schema, attribute structures, relationships), and specified data flows from heterogeneous sources. Managed delivery from concept to rollout.",
|
||||
"work_1_outcome": "Streamlined cross-departmental product data workflows with a purpose-built internal tool — delivered at ~80–90% lower cost than comparable SaaS solutions.",
|
||||
|
||||
"work_2_title": "Review Platform Migration",
|
||||
"work_2_problem": "The company needed to migrate its customer review infrastructure from Reviews.io to Trusted Shops, involving multiple stakeholders across marketing, IT, and Customer Support.",
|
||||
"work_2_approach": "Took end-to-end responsibility for the migration — coordinating cross-functional teams, managing the rollout timeline, and ensuring continuity of review data and processes.",
|
||||
"work_2_problem": "The company needed to migrate its customer review infrastructure from Reviews.io to Trusted Shops — involving multiple stakeholders across marketing, IT, and Customer Support, with a hard requirement on data continuity.",
|
||||
"work_2_approach": "End-to-end project ownership: requirements gathering, coordination of all involved teams, rollout timeline management, and ensuring continuity of review data and processes throughout the transition.",
|
||||
"work_2_outcome": "Successful platform transition with no disruption to customer-facing review flows.",
|
||||
|
||||
"work_3_title": "Workflow & Process Standardisation",
|
||||
"work_3_problem": "Product and content workflows were inconsistent and manual, creating bottlenecks and high error rates across the team.",
|
||||
"work_3_approach": "Introduced task tracking, documentation systems, and a TMS for landing page translations. Built a central knowledge base covering QA, uploads, and workflows.",
|
||||
"work_3_problem": "Product and content workflows were inconsistent and manual, creating bottlenecks, high error rates, and limited scalability across the team.",
|
||||
"work_3_approach": "Requirements analysis, introduction of task tracking and documentation systems, and a TMS for landing page translations. Built a central knowledge base covering QA, uploads, and workflows.",
|
||||
"work_3_outcome": "Up to 90% efficiency gains in product workflows. ~60% reduction in translation turnaround time. ~5 hours saved per week in organisational overhead.",
|
||||
|
||||
"work_label_problem": "Problem",
|
||||
|
|
@ -44,7 +45,7 @@
|
|||
"how_i_work_body": "I start from the business problem, not the solution. Every system, process, or tool I introduce has to justify itself against the alternative of doing nothing — or doing less. I prioritise by impact, keep things as simple as the situation allows, and make sure changes actually stick through documentation, handover models, and stakeholder alignment.",
|
||||
|
||||
"languages_heading": "Languages",
|
||||
"languages_list": "German & Hungarian — Native<br>English — C2<br>Italian & Japanese — A2",
|
||||
"languages_list": "German & Hungarian — Native<br>English — C2",
|
||||
|
||||
"contact_cta_heading": "Get in touch",
|
||||
"contact_cta_body": "Interested in working together?",
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue