Kornelia Skóra

Why this persona fits the audience

BI developer for a 12-person logistics company in Warsaw; documents warehouse tables for one analyst and one backend contractor, keeps schema notes in spreadsheets, and draws the database structure before monthly report cycles.

• Age: 30
• Location: Warsaw, Poland
• Occupation: BI Developer
• Income: 18,000 PLN/month
• Education: Master's in Economics and Analytics
• Company size: 12 employees
• Years in role: 4

“Data is only useful if you can trace exactly how it got there, no matter how small the step.”

Kornelia Skóra is a thirty-year-old BI Developer based in Warsaw, balancing a Master's degree in Economics and Analytics with four years of practical experience in the logistics sector. Currently employed by a twelve-person SME, she operates as the silent backbone of their data infrastructure. Unlike larger corporations where roles are siloed, Kornelia wears multiple hats: she is the documenter, the modeler, and the quality assurance officer for their data pipeline. Her workflow is distinctively analog-digital hybrid; while she writes complex SQL queries, her architectural planning remains trapped in Excel spreadsheets and hand-drawn diagrams. This choice stems from a pragmatic view that her team finds specialized modeling tools too rigid or expensive for their current scale. Every month, Kornelia faces the 'reporting cycle' pressure. She meticulously maps warehouse tables, ensuring that the backend contractor and the internal analyst speak the same language regarding data types and relationships. Her recent decision to maintain these manual notes was driven by a fear that automated tools might introduce hidden dependencies that could break their legacy reporting system. She values accuracy above speed, often spending extra hours verifying a single foreign key constraint to prevent a cascade of errors in the final monthly P&L statement. Financially, she earns a solid 18,000 PLN monthly, allowing her to live comfortably in Mokotów while saving aggressively. She views her income as a tool for security rather than status. Professionally, she is skeptical of 'silver bullet' solutions, preferring incremental improvements that offer tangible ROI. Her personality reflects a high conscientiousness; she is the person who color-codes her filing cabinet and double-checks the locks. While she enjoys the logical satisfaction of solving complex data puzzles, she feels a growing frustration with the manual nature of her documentation work. She dreams of a future where her data models are self-documenting, freeing her to focus on higher-level analytics rather than drawing lines between tables.

Background & daily life

A day in their life

Kornelia wakes at 6:30 AM, avoiding the rush hour by starting early. After a quick jog and a simple breakfast, she arrives at the office by 8:00 AM. Her morning is spent reviewing overnight logs for data anomalies, a ritual she never skips. Between 9:30 and 11:00, she meets with the backend contractor to discuss upcoming warehouse schema changes, sketching out the new relationships on a whiteboard. The bulk of her afternoon is dedicated to updating her master spreadsheet of table definitions, cross-referencing them with the actual database to ensure accuracy. She avoids meetings after 3:00 PM to focus on deep work. Before leaving, she runs a final query to verify the previous day's monthly report numbers. She returns home around 6:00 PM, cooking dinner and spending the evening unwinding with a puzzle game or reading a book on logistics history.

Lifestyle

Kornelia lives in a modest but well-organized apartment in Mokotów, where order is paramount. Her evenings are reserved for running along the Vistula River or solving complex logic puzzles like Sudoku and chess problems, which she finds relaxing after a day of data wrangling. She manages her finances strictly, prioritizing savings for a potential mortgage over luxury travel. Socially, she maintains a tight circle of three close friends from university, preferring deep conversations at quiet cafes over large gatherings. Health is a steady routine rather than a hobby; she cooks nutritious meals at home and avoids alcohol on weekdays. Her disposable income goes toward high-quality coffee beans and occasional visits to the National Museum in Warsaw.

Work life

At her small logistics firm, Kornelia is the de facto data architect despite not having that title. Her primary daily task involves mapping warehouse table structures before the monthly reporting cycle begins. She relies heavily on Excel spreadsheets to document schemas because her colleagues find dedicated modeling software too abstract. She collaborates closely with a single backend contractor who needs precise schema definitions and an internal analyst who builds dashboards in Power BI. The pressure peaks every month-end when reports must be flawless. She spends hours manually drawing ER diagrams to ensure everyone understands the relationships between inventory and shipping tables, often working late to fix discrepancies found by the analyst.

Relationships

Kornelia is deeply connected to her family in Krakow, visiting monthly for dinner, though her mother worries she works too hard. At work, she has a symbiotic relationship with her manager, who trusts her implicitly with data decisions but rarely challenges her methods. Her partner, an architect, respects her need for quiet and often helps her visualize structural concepts. She influences junior analysts through patient mentorship rather than authority, earning their respect for her calm demeanor. Her professional network is small but highly reliable, consisting mostly of former classmates and a few peers from local data meetups.

How they decide

Cautious and research-heavy, Kornelia requires concrete evidence of utility before adopting any new method. She prefers peer validation and documented case studies over marketing claims. If a solution promises efficiency, she will demand a proof-of-concept using her own messy data before committing time to learning it. She values stability and low risk, often sticking with known workflows until a friction point becomes unbearable. Her decisions are rarely impulsive; she weighs long-term maintenance costs against immediate gains.

How they sound

Her speech is measured, clear, and devoid of filler words. She speaks Polish with a slight urban Warsaw cadence but uses English technical terms precisely when discussing code. She avoids hyperbole and emotional language, preferring factual descriptors like 'inconsistent' or 'inefficient.' In meetings, she listens intently before speaking, often pausing to formulate the most accurate response. She does not use slang and rarely jokes in professional settings, maintaining a tone of professional seriousness.